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

# Set up a Star printer

> How to enter a Tillcast printer URL in a Star printer's CloudPRNT settings, and what has been checked on a real printer.

These steps were written from tests on a Star mC-Print3 with firmware 5.2 against the production service. What has been checked on a device, and what has not, is listed at the end of the page. Menu names in the printer's web page differ a little between firmware versions, so look for the words in bold.

## Before you start

* A [printer URL](/concepts/printer-url) for this printer. It is shown once, when you add the printer in the dashboard or through the API. See the [Quickstart](/quickstart).
* A computer on the same network as the printer. The network must allow outgoing HTTPS (port 443) and DNS. No VPN, port forwarding or local server is needed.
* A printer that supports CloudPRNT and speaks StarPRNT. See [Supported printers](/printers/supported-printers). On mC-Print models use firmware 3.2 or newer.
* The printer added by its paper width, or added as a Star. Added by its paper width, it reads `star` until it first connects, and then takes its width from what it reports: see [Add a printer by its paper width](/printers/profiles#add-a-printer-by-its-paper-width). Added as a Star by name, a narrower printer needs the [profile](/printers/profiles) of its paper. For a 58 mm printer that is `star-starprnt-utf8-58mm`.

## Steps to set up the printer

1. **Find the printer's IP address.** Print the printer's self-test page. On the mC-Print3, switch the printer on while holding the FEED button. For another model, see its manual. The page also shows the firmware version.
2. **Open the printer's web page.** Enter `http://<printer-ip>/` in a browser on the same network, and log in.
3. **Change the web admin password** if it is still the factory default. The printer's web page shows the URL, and the URL is the printer's only credential. Anyone who can log in there can read it.
4. **Open the CloudPRNT settings.**
5. **Set the fields.**
   * **CloudPRNT:** enable it, in HTTP mode.
   * **Server URL:** paste the whole printer URL. It is one field. Do not add a trailing slash or spaces. Never `localhost`: that would be the printer itself.
   * **HTTP authentication, user name and password:** leave both empty. The secret in the URL is the credential.
   * **Polling time:** 5 seconds, which is the default.
   * **Encryption Level:** `HIGH + MEDIUM`, which is the printer's default, or `MEDIUM`. Against the production service both took the same time. If the printer sits behind a tunnel or a proxy, use `MEDIUM`.
   * **MQTT settings:** leave them off.
6. **Save, then restart the printer.** Settings apply only after the restart (**Save & Restart**, or a power cycle).
7. **Wait for the first connection.** A printer that connects for the first time prints a welcome receipt. See [First connection](/printers/first-connection).

Check the printer's date and time too. The printer needs the right time to validate the HTTPS certificate.

Then send a [test print](/printers/first-connection#test-print) from the dashboard, or a job with the API.

## What has been checked on a device

Checked on a Star mC-Print3 with firmware 5.2 against the production service on 2026-10-12:

* **Certificate.** The printer accepts Tillcast's wildcard certificate at both Encryption Levels.
* **Empty username and password.** The printer form accepts them, the printer polls with the URL, and the secret arrives intact.
* **One request per poll.** There is no extra authentication round trip.
* **Speed.** A job was confirmed 5 to 6 seconds after it was queued on average, at either Encryption Level, with a 5 second poll interval.

One more result comes from a test tunnel and not from the production service. Through the tunnel, `HIGH + MEDIUM` made every download and every confirmation wait about 15 seconds, and `MEDIUM` took under 3 seconds. Behind a tunnel or a proxy, use `MEDIUM`.

## Not checked yet

* **Recovery after a refusal.** How a printer behaves while Tillcast refuses it, and how fast it reconnects afterwards, has not been measured. It matters for a [suspension](/concepts/suspension) and for an [allowed device](/concepts/printer-url#allow-only-one-device-optional).
* **Paper out and cover open.** The status codes are known (`410 Out of paper`, `420 Cover open`), but what the printer does with a waiting job while it has such a condition has not been tested.
* **The limits of the form.** The maximum length of the URL field, trailing spaces and upper case in the URL.
* **The report of its paper.** Whether a Star answers the question about its print area when it first connects, and what an mC-Print3 reports, has not been checked on a device.
* **How the new documents look on paper.** The ReceiptLine stream has been delivered on production. The full test page was printed on an mC-Print3 on 16 October 2026 and every section came out; ordinary receipts are not checked on paper yet. See [Supported printers](/printers/supported-printers).

If your printer does not connect, see [Troubleshooting](/printers/troubleshooting).