Aug 24, 2026IMPROVEDAVAILABLEROUTERGATEWAYAPI
Router publishes its canonical machine-readable contract
The hosted Router now serves the Gateway-owned OpenAPI 3.1 document at /openapi.json and returns typed JSON for unknown routes and unsupported methods.
- GET https://router.patchboard.online/openapi.json is public and returns the exact normative relayapi OpenAPI mirror embedded from the public Gateway repository.
- Unknown paths return route_not_found with HTTP 404. Known paths called with the wrong method return method_not_allowed with HTTP 405 and an Allow header.
- Every public Router response advertises the default edge quota through RateLimit-Policy. Application-generated 429 responses also include Retry-After and the normalized error envelope.
- The contract documents the stable /v1 compatibility policy, RFC 9745 deprecation signal, migration link, and minimum 90-day Sunset notice.
Action: No request migration is required. Agents and code generators should discover the Router contract from patchboard.online/openapi.json or router.patchboard.online/openapi.json instead of guessing routes.
Aug 24, 2026ADDEDAVAILABLEGATEWAYLIVEKITPIPECAT
Gateway is the open customer-side voice runtime
Patchboard Gateway provides one local streaming protocol across voice providers, native LiveKit and Pipecat integrations, and local BYOK credential custody.
- Gateway runs in the customer workload and can call voice providers directly while keeping BYOK credentials inside the Gateway process.
- The public image ships native LiveKit and Pipecat integrations for streaming STT and TTS, interruption handling, usage, and timing events.
- Gateway can combine provider-direct voice legs with Patchboard-managed routes. The hosted Router remains a separate Patchboard-operated data plane at router.patchboard.online.
- The public relayapi package in the Gateway repository is the canonical HTTP, SSE, and WebSocket wire contract for hosted Router traffic.
Action: Choose Gateway for provider-direct or local-BYOK workloads. Choose Router for the hosted managed data plane; the two surfaces are complementary, not interchangeable.