Patchboard developer resources
Patchboard Router, Gateway, Agents API, OpenAPI, framework guides, MCP, CLI, and machine-readable discovery resources in one place.
Router, Gateway and Agents API are three different jobs
Router is Patchboard’s hosted STT, LLM, and TTS data plane at router.patchboard.online. Gateway is the open customer-side runtime in the PatchboardAI/gateway repository; it keeps BYOK credentials in your process and integrates natively with LiveKit and Pipecat. The separate hosted Agents API at api.patchboard.online owns agents, sessions, phone numbers, and calls. They solve different jobs and do not share an OpenAI-compatible facade.
A typed contract, not a hostname swap
Every Router request sends Authorization: Bearer $PATCHBOARD_API_KEY. Every POST also sends an Idempotency-Key. Use GET /v1/models to discover currently routable models and their capabilities. Use routing: { mode: "auto", objective: "balanced" } for managed selection, or provide an explicit provider and model. Router is a native contract, not a hostname replacement for an OpenAI SDK.
A read-only MCP server, no auth required
The public Patchboard Docs MCP server is a read-only Streamable HTTP endpoint at patchboard.online/.well-known/mcp. It requires no authentication: initialize the connection, list resources, read patchboard://docs/index, and then open the matching documentation resource rather than guessing a page or tool name. Account data and write tools remain on the protected operational MCP endpoint at mcp.patchboard.online/mcp, using OAuth or a Patchboard bearer key.
First-party packages on npm
Use npx @patchboard/mcp-calls init for the disclosed agent-call setup flow, or npx @patchboard/mcp as a local stdio bridge when an MCP client cannot connect to Streamable HTTP directly.
claude mcp add --transport http patchboard https://mcp.patchboard.online/mcp