Concepts

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: the REST API, the MCP server, and the tracker.

The object model is small. Once you understand these three concepts, the rest of the docs is just the API surface around them.

A contact is a person tracked across all connected sources. Every contact has:

• A unified profile — properties merged from CRM, enrichment providers, and form submissions.
• An event timeline — chronological cross-system activity (page views, opens, replies, syncs).
• Notes — free-form internal annotations.
• Conversations — Gmail threads and Intercom chats (when those sources are connected).
• An association with one company.

→ Contacts API

A company is the primary B2B unit. Individual contacts roll up to company-level intelligence. Companies are identified by domain and have properties like industry, employee_count, and lifecyclestage. When you query a company, Pathbound returns its associated contacts (up to 25).

→ Companies API

An event is a tracked interaction across any connected source — a page view, button click, form submission, video play, email open. Events are linked to a contact (when the visitor is identified) and provide the behavioral signal layer of the unified profile.

The tracker is the most common source of events, but events can come from email opens, CRM webhooks, video providers (Wistia), and custom track() calls.

→ Events API

Tracker  ───▶  Events  ───┐
                          │
Connected sources  ───▶  Contact  ───▶  Company
(CRM, email, etc.)        │
                          ▼
                  Unified customer profile
                  (read by your code, your
                   AI agents, or Claude.ai
                   over MCP)

A typical loop:

1. The tracker captures behavioral events on your site.
2. A form submission (public form endpoint) identifies the visitor — events are now linked to a contact.
3. CRM, enrichment, and email sources merge into the contact’s unified profile.
4. Your code (or an AI agent connected over MCP) reads the profile and timeline to make a decision.