Introduction

Pathbound is the customer-context layer for AI agents and humans. It connects data from your CRM, website analytics, email, LinkedIn, 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, actions, agents, events, segments, and identities.
• MCP server — Same data, tool-shaped, for Claude.ai and other Model Context Protocol clients.
• Tracker — A 4 KB JavaScript snippet that captures behavioral events on your website and links them to contacts.

These docs cover all three.

Where to start

If you want to…	Go to
Make your first API call	Quickstart
Understand the object model	Concepts
Authenticate	Authentication
Browse REST endpoints	API Reference → Contacts
Connect Pathbound to Claude.ai	MCP → Overview
Capture website behavior	Tracker → Install

Base URL

All API v1 endpoints are served under:

https://api.pathbound.ai/v1

The MCP server lives at https://mcp.pathbound.ai. The tracker is served from https://tracker.pathbound.ai/tracker.js.

Error format

All REST error responses follow a consistent shape:

{
  "status": "error",
  "error": "A human-readable message",
  "details": [],
  "timestamp": "2026-04-29T12:00:00.000Z"
}

Validation errors (400) include a details array with per-field messages.

Rate limits

• REST API: 100 requests per 15-minute window per API key (global). Heavy bursts may also hit per-endpoint limits — these are returned as 429 Too Many Requests.
• Public form submission: 30/min/IP globally, 100/min per tenant.
• Tracker /track and /recover-visitor: per-domain and per-IP rate limits, tuned for normal browser traffic.

Webhooks

Pathbound can deliver events to your own URLs. Webhooks are configured in the dashboard, not via the API. See API Reference → Webhooks for payload format and signature verification.

Status

Live status: status.pathbound.ai.