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

# Roadmap

> What is live in Tillcast today, what is in development and not available, what is planned and what is only an idea. No dates.

> **A plan, not a promise**
>
> Order and scope can change. There are no dates. Only the part called "Live" exists. Whatever is under "In development", "Planned" or "Ideas, not decided" is not available: do not write code that depends on it.

## Live

* **The API.** `https://api.tillcast.com/v1`, with restricted API keys and scopes, organizations, customers, locations, printers, jobs, the test print, idempotency, pagination and a version header. The [API reference](/api-reference) is built from the contract of the service.
* **Receipt documents.** A job carries `document`, an array of blocks (text, tables, rules, codes and images), or `receiptline`, text in ReceiptLine for documents written for other ReceiptLine tools. Send exactly one of the two. Tillcast renders the document for the printer's profile. See [Create a print job](/create-a-print-job) and [Receipt documents](/concepts/documents).
* **Two printer technologies.** Star CloudPRNT and Epson Server Direct Print, with nine profiles for 80 mm and 58 mm paper. See [Supported printers](/printers/supported-printers).
* **The printer URL**, with an optional allowed device, and the suspension of a customer and the pause of a location.
* **Your own domain for printer URLs**, as an extra on request. Tillcast sets the domain up for your organization, and the price is agreed individually. See [Printer URL](/concepts/printer-url#own-domain-for-printer-urls).
* **The dashboard** at [dashboard.tillcast.com](https://dashboard.tillcast.com). Sign-up is open, with an e-mail address and a password. People create organizations, invite members, create API keys, and create customers, locations and printers, edit and delete printers, and print a test page. They read the lists of customers, locations, printers and jobs.
* **The status page** at [status.tillcast.com](https://status.tillcast.com).
* **SDKs for TypeScript and Python**, as pre-1.0 versions: `npm install @tillcast/sdk` and `pip install tillcast`. They are generated from the API contract, and method names can still change before 1.0, so pin the version. Blocks need version 0.2.0 or later. See [SDKs](/getting-started/sdks).
* **A receipt preview for your own pages.** The npm packages `@tillcast/preview` (a React component and a function for any page) and `@tillcast/html-render` (the renderer) draw a receipt as HTML in the browser or in Node, so nothing is sent to Tillcast to draw it. They are `0.x`: pin the version. See [Preview a receipt in your app](/preview-a-receipt).
* **An MCP server for the API.** `https://api.tillcast.com/mcp`: 28 tools for customers, locations, printers and jobs and a preview that prints nothing, used with an API key as a bearer token, so the key's scopes decide what an assistant can do. It works with the clients that can send a header, and sign-in with OAuth is not available (see Planned). A key prints on real paper. See [Connect an AI assistant (MCP)](/connect-an-ai-assistant). The docs also have a search server for agents, which cannot call the API: see [Build with an agent](/build-with-an-agent).
* **This documentation.** It has an `llms.txt` index, a Markdown version of every page (add `.md`) and a search server for agents that answers from these docs only. See [Build with an agent](/build-with-an-agent).

## Being finished

* **Paper checks.** The new receipt output has been delivered on production to a Star mC-Print3 and an Epson TM-m30III-H. How it looks on paper is being checked, and so are the points listed in [Set up a Star printer](/printers/star-setup#not-checked-yet).

## In development

These are being built. None of them is available, and none has a date. Do not write code that depends on them.

* **A template language and stored templates.** A language for receipts with places for your data, kept in Tillcast and used from a job. Today a job has no `template` and no `data` field, and a request that sends one is refused. Build the document in your code, with a loop over your own data.
* **Sign-in with Google.** For the dashboard. Today sign-in is an e-mail address and a password.

## Planned

* **Webhooks, the events API and a CSV export.** See [Webhooks and events](/events/webhooks).
* **An editor for your own pages.** An editor with a preview for blocks and templates is planned. It runs in your page, so nothing is sent to Tillcast to edit.
* **OAuth sign-in for the MCP server.** So that an assistant that offers only OAuth sign-in, such as ChatGPT, can connect without an API key. Today the MCP server takes a key.
* **OAuth connections and connectors for Make, Zapier and n8n.** Today any tool that can send an HTTP request can create a print job with an API key.
* **An installable skill for coding agents.**
* **Usage statistics and the audit log** as endpoints and screens, and billing with invoices. Neither is built, and no invoice is issued yet.
* **More in the dashboard:** screens to change, pause or delete customers and locations, and to move a printer. These are done with the API today.
* **Star Line printers**, for example the TSP650II, TSP700II and TSP800II with a network interface. The renderer can make their commands, and no connection carries them to a printer yet.
* **Push to printers** (CloudPRNT over MQTT), so that a job prints without waiting for a poll. Only newer printer models support it. Polling stays as the fallback.
* **Tillcast Bridge**, a small device for network printers that cannot fetch jobs from a server by themselves. You plug it in at the venue and connect it to the venue's network. It connects out to Tillcast and passes each job to a receipt printer on the same local network, so nothing has to be opened to the internet. For now it is for printers on the network (LAN or Wi-Fi) only: printers on USB, a serial port or Bluetooth only are not supported. Tillcast Bridge will be sold as a device. It is not available yet, and it has no date and no price. Which printer models it supports will be listed in [Supported printers](/printers/supported-printers) only after they have printed through it on a real device.

## Ideas, not decided

* **Other kinds of document, a cash drawer option and an image converter.** Documents other than blocks and ReceiptLine were left out on purpose for now.