Skip to main content

Documentation Index

Fetch the complete documentation index at: https://docs.pickupbell.com/llms.txt

Use this file to discover all available pages before exploring further.

​
What you can build

PickupBell is the AI receptionist layer for home-services contractors. Over the API you can:
  • Read — pull calls, transcripts, leads, bookings, and insights for reporting, CRM sync, or your own UI.
  • Write — add FAQs, update agent personality, move leads through a pipeline, schedule appointments.
  • Listen — subscribe to webhooks for emergency transfers, new leads, booked appointments.
  • Agentic — point Claude, ChatGPT, or Cursor at our MCP server and let AI do everything on behalf of the user.

​
Two front doors, one service layer

         ┌──────────────────────────────────────────┐
         │  service layer  (enforces permissions    │
         │                  + PII scrubbing)        │
         └──────────────────────────────────────────┘
                   ▲                     ▲
                   │                     │
            ┌──────┴──────┐       ┌──────┴──────┐
            │ REST        │       │ MCP server  │
            │ /api/v1/*   │       │ /api/mcp    │
            └─────────────┘       └─────────────┘
Both front doors authenticate with the same Bearer token and go through the same service functions — scopes and PII scrubbing apply uniformly:
  • REST with Bearer token — phones masked, transcripts/recordings only with explicit scopes, billing hidden entirely.
  • MCP tools/call — same scrubbing as REST.

​
Base URL

https://api.pickupbell.com
MCP is at /api/mcp.

​
Next

Quickstart

Make your first authenticated request in under five minutes.

Authentication

How API tokens work — creation, scopes, rotation, revocation.

MCP server

Plug PickupBell into Claude Desktop / ChatGPT / Cursor.

Webhooks

Receive real-time events when calls end, leads are captured, or bookings post.