Interactive reference
The live, try-it-now API reference
90 v1 routes and the 70-tool MCP endpoint, rendered from the real OpenAPI spec — request builders, generated code samples in curl/JS/Python/Go, and (for the v1 routes) requests that actually run using your own signed-in session.
- Generated from the same route table the narrative docs are built from
- Code samples in curl, JavaScript, Python and Go
- 78 of the 90 v1 routes run on your browser session; the bearer field drives /api/mcp
Nothing here is a sandbox — a request you send runs on your own workspace, and none of it outranks the approval queue
Before you send one
The bearer field below is not how most of this API authenticates.
The generated spec declares one formal security scheme, so Scalar draws one bearer-token box and offers it against every operation in the document. 78 of the 90 v1 routes never read an Authorization header at all.
Which credential drives which request
- The v1 routes run on your session. Sign in to FounderReply in this browser first; the request builder sends a same-origin fetch and your session cookie rides along on its own. Signed out, those 78 routes return 401 whatever you paste into the bearer box.
- The bearer field is for /api/mcp. An fr_live_ key authenticates the MCP endpoint and /api/v1/voice/mcpdial/numbers, /api/v1/voice/mcpdial/numbers/{id}, /api/v1/voice/mcpdial/numbers/available, /api/v1/voice/mcpdial/numbers/requirements, /api/v1/voice/mcpdial/verification/status, /api/v1/voice/mcpdial/verification/profile, /api/v1/voice/mcpdial/verification/addresses, /api/v1/voice/mcpdial/verification/addresses/{id}, /api/v1/voice/mcpdial/verification/documents, /api/v1/voice/mcpdial/verification/documents/{id}, /api/v1/brain and /api/v1/brain/proposals. On the other 78 the header is not rejected — it is never looked at, so pasting a key there will not authenticate the request.
The live document · 90 v1 routes · 70 MCP tools
/api/v1/openapi.jsonLoading the interactive reference…
What you are actually firing
Real requests, your own workspace, through the same gate.
The builders above are not a demo against fixture data. They are the endpoints the FounderReply app itself calls, reached the way the app reaches them — which is also why nothing you send from this page can do more than you could do signed in.
The call is real
Send from this page and the browser makes a same-origin request with your session on it. There is no sandbox tenant and no seeded data — you are reading and writing your own workspace, under the same membership checks every route runs.
A write still passes the controller
A v1 or MCP call that would publish goes through the same dial and the same approval queue the dashboard uses. Neither surface can route around that controller, so a request fired from this page is exactly as safe as the same one fired from the app — and no safer.
The document cannot drift
Every path, method and tag below is generated from lib/v1-routes.ts — the same table /developers/api prints in prose — plus the 70-tool MCP registry. Change a route and all three surfaces change in the same commit.
Send a real one
Stop reading about it. Fire the request.
Sign in and the 78 session routes above run against your own workspace. Mint a key and the MCP endpoint runs from anywhere else.
Free to start · Approval on by default · No card required