Built to be run by software.
Thezi is designed to be operated by software as well as by people. Every state change is an API operation with a stable contract and a typed error code, and there is nothing a person can do in the dashboard that the API cannot. Your staff mint their own keys, from your own dashboard, scoped to your venue alone.
Nothing lives only in the screens
Everything a person can do here, an assistant can do too, because they call the same thing. Most booking systems bolted an API on afterwards. Here it is the only way in.
You can tell who did what
Every change records whether a person or a machine made it, proved by the key that was used rather than claimed, and you mint those keys yourself, from your own dashboard. When an assistant starts taking your bookings, that stops being academic.
Money always waits for you
Refunds, deposits and charges are never automatic. Software can prepare them and will chase you about them. A person commits them.
Model Context Protocol.
MCP is how an assistant is handed a set of tools rather than a set of URLs. Thezi was built for it from the first migration: the API is the contract an MCP server sits on, not something wrapped around one afterwards. Until that server ships, an assistant works over plain HTTPS with the same venue key and reaches exactly the same things.
Your key names your venue
An assistant never tells us which restaurant it is acting for. The key it was given says so, and the API refuses anything else, so a tool taking a venue as an argument would be either ignored or a lie. There isn’t one.
An assistant can find us on its own
thezi.app/llms.txt is the same courtesy to an assistant that robots.txt is to a crawler: what this is, where the contract lives, and the two rules that matter most — money waits for a person, and a retry has to replay rather than book the same table twice.
The server is deliberately later
An MCP surface has to change every time the API does, and we would rather keep improving the API while it is young than freeze it early to hold a tool list still. The shape is already settled: its own worker, holding no key of its own, passing yours through untouched.