Skip to navigation
Build with AI

Machine-readable docs

Every surface an agent or script can read, and what each one contains.

Everything on this site is available in a form a program can read. The machine-readable copies are generated from the same sources as the pages you are reading, so they do not drift.

Surfaces

SurfaceWhereWhat it contains
Site index/llms.txtEvery page with its description and a link to its Markdown. Also available per section, for example /api-reference/llms.txt.
Page as MarkdownAdd .md to any page URLThe page content, including API reference pages with their schemas and examples. Sending Accept: text/markdown works too.
Risk Intelligence contracthttps://api.toden.co/api/openapi.jsonOpenAPI 3.1 for /api/v1.
Identity verification contracthttps://api.toden.co/api/openapi/verification.jsonOpenAPI 3.1 for /api/kyc and /api/identity.
Webhook catalogueGET /api/v1/webhooks/catalogueThe current event types, read from the running service with a secret key.
Documentation MCP server/_mcp/server on this siteA tool an agent can call to search these docs. It does not call the Toden API and takes no API key. See MCP server.
Agent skillsAgent skillsOne brief per product.

Every page also has Copy page and View as Markdown actions at the top.

Reading order for an agent

  1. Fetch /llms.txt and pick the guides for the product in hand.
  2. Fetch the OpenAPI contract for the API family, and resolve the schemas it references.
  3. Read the endpoint’s reference page as Markdown for its error codes and examples.
  4. Read Requests, retries and idempotency and Verify signatures before writing any retry or webhook code.

What the contracts guarantee

  • Every documented operation exists in the released API. The build fails if a documented endpoint is not mounted.
  • A removed endpoint, removed field or newly required field on /api/v1 fails the build until it is reviewed as a breaking change.
  • The identity verification contract documents the server-to-server and SDK-entry endpoints. Routes that only the SDKs use internally during capture are deliberately left out and can change.

When the docs and the API disagree

Treat the API’s actual response as the truth, tell us at hello@toden.co, and do not guess a field that is not in the contract.