What every API gets
Every Interface, machine register and path an API serves from its one Definition, on its own host.
Every API on the platform serves all of the following from its one Definition, on its own host, with no code of its own.
Interfaces
| Interface | At | What it is |
|---|---|---|
| API | each operation path | REST over HTTP: one GET per operation, answering JSON with a cost header and a request id. |
| MCP | / | Streamable HTTP with three tools for every API, never one tool per operation. |
| Docs | / | An index and one page per operation, Markdown first, with the HTML rendered from it. |
| SDK | / | One-file TypeScript and Python clients, generated from the Definition and served by the API. |
| App | / | One Key and its calls, in HTML, Markdown and JSON. |
Machine registers
MCP tools
| Tool | Input | Answers |
|---|---|---|
search | {query} | The operations whose words match, each with its docs page. |
fetch | {id} | The answer of a REST path as text, or the docs page of an operation as Markdown. |
do | {verb, | Runs one operation; its structured content is exactly the REST body. |
Reserved paths
| Path | Serves |
|---|---|
/ | The root JSON: the API name, its operations and its other registers. |
/mcp | The MCP server. |
/docs | The docs, in HTML or Markdown. |
/openapi.json | The OpenAPI 3.1 document. |
/llms.txt | The llms.txt file. |
/pricing | The pricing document. |
/.well-known | The agents.json card. |
/sdk | The generated SDK files. |
/batch | The Batch route. |
/dashboard | The Dashboard. |
On every response
| Header | Carries |
|---|---|
X-Cost | The price of the call, the upstream cost of serving it, and the currency. |
X-Request-Id | The id a caller quotes when asking about a call. |