Introduction to Pathbound
Pathbound is the customer-context layer for AI agents and humans. It connects data from your CRM, website analytics, email, and other tools into a single profile per contact and company — then exposes that context through three surfaces:
- REST API — Programmatic access to contacts, companies, deals, events and conversations, and to the actions your connected tools can take: tagging, segments, automations, enrichment and sending email.
- MCP server — Same data and actions, tool-shaped, for Claude.ai and other Model Context Protocol clients.
- Events — A 5 KB JavaScript snippet that captures behavioral events on your website and links them to contacts.
These docs cover all three.
Reading these docs from an AI agent
Section titled “Reading these docs from an AI agent”Every page is also published as machine-readable markdown so an assistant can ground its answers in the current product knowledge:
https://pathbound.ai/llms.txt— curated index of every page (titles, descriptions, links).https://pathbound.ai/llms-full.txt— the full docs concatenated into one bundle for one-shot ingestion.https://pathbound.ai/docs/<page>.md— the raw markdown for any single page.
For step-by-step setup with Claude Projects, ChatGPT, or your own agent, see Use with AI tools.
Where to start
Section titled “Where to start”| If you want to… | Go to |
|---|---|
| Make your first API call | Quickstart |
| Understand the object model | Concepts |
| Authenticate | Authentication |
| See everything the REST API covers | API Reference → Overview |
| Browse REST endpoints | API Reference → Contacts |
| Push changes to your own systems | API Reference → Streaming |
| Connect Pathbound to Claude.ai | MCP → Overview |
| Capture website behavior | Events → Install |
| Use these docs from Claude, ChatGPT, or your agent | Use with AI tools |
Base URL
Section titled “Base URL”All API v1 endpoints are served under:
https://api.pathbound.ai/v1The MCP server lives at https://mcp.pathbound.ai/mcp. The events snippet is served from https://events.pathbound.ai/snippet.js.
Error format
Section titled “Error format”All REST error responses follow a consistent shape:
{ "status": "error", "error": "A human-readable message", "code": "a_stable_word", "details": [], "timestamp": "2026-10-12T12:00:00.000Z"}Validation errors (400) include a details array with per-field messages. code is present when the error has one. The statuses and what each means are listed under Errors.
Rate limits
Section titled “Rate limits”- REST API: limited per workspace and per IP address, well above what an integration needs in normal use. A request over a limit is answered with
429 Too Many Requestsand aRetry-Afterheader. See Rate limits. - Public form submission: 30/min/IP globally, 100/min per workspace.
- Event ingestion
/trackand/recover-visitor: per-domain and per-IP rate limits, tuned for normal browser traffic.
Streaming
Section titled “Streaming”Pathbound can push events and record changes to your own URLs as they happen, or act on them: add a tag, change a Resend segment, email everyone who submits a form. A stream that posts to a URL is set up in the dashboard; automations can also be created over the API. See API Reference → Streaming for the payload format, signature verification and the endpoints.
Status
Section titled “Status”Live status: status.pathbound.ai.