> Tillcast is live: the API at https://api.tillcast.com/v1 and the dashboard at https://dashboard.tillcast.com. A key prints on real printers, so do not call the API unless asked. A job carries its receipt as "document", an array of blocks (the recommended way), or as "receiptline", ReceiptLine text, exactly one of the two: read https://docs.tillcast.com/create-a-print-job.md and https://docs.tillcast.com/concepts/documents.md before you write a job body. Do not code against what does not exist yet: webhooks, a template language, stored templates (a job has no template field), OAuth connections and connectors for Make, Zapier and n8n, and OAuth sign-in for the MCP server. SDKs for TypeScript (@tillcast/sdk, version 0.2.0 or later for blocks) and Python (tillcast) exist as pre-1.0 versions. To show a receipt in a web page without printing, there are the npm packages @tillcast/preview and @tillcast/html-render (0.x, no API key, no call to Tillcast to draw): read https://docs.tillcast.com/preview-a-receipt.md. The docs are the source of truth: check the index https://docs.tillcast.com/llms.txt and https://docs.tillcast.com/roadmap.md before you code against anything. For clean Markdown of any page, append .md to the page URL. The Tillcast MCP server is live at https://api.tillcast.com/mcp and takes an API key as a bearer token (setup: https://docs.tillcast.com/connect-an-ai-assistant.md). It acts on the live account and its tools print on real paper, so do not connect to it or call its tools unless the owner asked you to. The MCP server at https://docs.tillcast.com/_mcp/server is a different one: it only searches these docs and cannot call the Tillcast API.

## For agents: what exists and what does not

* **Roadmap.** The roadmap has a new part, "In development", for what is being built and is not available: a template language and stored templates, an MCP server for the API, and sign-in with Google. OAuth connections and connectors for Make, Zapier and n8n are listed as planned. Nothing in "In development" or "Planned" can be used, and none has a date. See the [roadmap](/roadmap).
* **Build with an agent.** The `AGENTS.md` snippet says that stored templates, a `template` or `data` field on a job, OAuth connectors, the API's own MCP server, webhooks and test mode do not exist and must not be coded against, and that the docs are the source of truth: check [llms.txt](https://docs.tillcast.com/llms.txt) before you code against a field. There is a new prompt that checks an integration against the docs. See [Build with an agent](/build-with-an-agent).
* **Welcome.** The first page names the call, the key and its scope, and the two ways to write the receipt (`document` as blocks, or `receiptline`).
* **Examples.** Every example that sends a different request has an idempotency key of its own, so two examples run one after the other do not meet `422 idempotency_key_reused`.
* **SDKs.** The TypeScript `err.requestId` reads the header `x-request-id`, which the API does not send, so it is `undefined`. Read `err.body.error.request_id`. See [SDKs](/getting-started/sdks).
* **Update 2026-10-25.** Tillcast has no test mode.