> 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.

## SDK READMEs and the job guide

* **A page for creating a job.** [Create a print job](/create-a-print-job) is the page to start from once you have an API key and a printer. It has the smallest request in cURL, TypeScript and Python, what each field means, the `201` answer, what happens next and how to read the job, retrying with an `Idempotency-Key` with a replay shown, the usual refusals including `422 document_invalid` and its `param`, receipts to copy as blocks and as ReceiptLine text, and the test print. The welcome page and the quickstart lead to it, and it is third in the navigation.
* **READMEs of the SDKs.** From version 0.2.1, the README of `@tillcast/sdk` and of `tillcast` leads with creating a print job: how to install the package, where to get an API key, the client with `token`, a receipt as blocks and as ReceiptLine text, the idempotency key, reading the job back with `jobs.get`, and how to read a refused document. The README of version 0.2.0 shows only the creation of a customer. See [SDKs](/getting-started/sdks).