AI features
The dashboard's AI assistant, the AI studio for dish photos, listings and clips, background removal and the MCP server: what each does, what it needs and who pays for it.
For the Full Stack package
What the AI features do
| Feature | Where | What it does | What it needs |
|---|---|---|---|
| AI assistant | Staff dashboard, its own page | Answers questions about orders, dishes, kitchens and sales, draws sales charts, and proposes changes such as a dish's availability or a kitchen's hours. A change runs only after you confirm the difference it shows, and only within the signed-in account's permissions. | A Google AI (Gemini) key |
| AI studio | Staff dashboard, its own page | Restyles a dish photo with a background, a lighting and a prompt, keeping the food, the portion and the plate exactly as photographed, and compares it with the original. | A Gemini key |
| The studio in the dish form | Staff dashboard, the dish form | Assistant writes the dish's name, description and ingredients from its photos and edits photos on request. Animate turns a photo into a short clip of a few seconds. | A Gemini key for the Assistant; a Higgsfield key and secret for generated photos and clips |
| Background removal | AI studio and the dish form | The "Remove background" button cuts a dish out of its photo; the studio's assistant can do it too. | A free model file on your server; no key |
| MCP server | The API, POST /api/mcp | Lets a coding agent or any MCP client use the assistant's tools. | A key you choose, MCP_API_KEY |
- Every feature reports itself off until what it needs is set, and the rest of the restaurant works without them.
- Each call to Google or Higgsfield is billed to the key it runs on, at that provider's prices. Background removal runs on your own server and costs nothing per image.
- Keys live only in the API's
.env. Nothing secret is ever put in a frontend. - Nothing the studio makes is published by itself: a result goes on the dish only when staff add it and save the dish.
- Kitchen accounts have no access to the studio, and the assistant never shows them money.
Without keys
- The assistant's page says "No AI model is connected".
- The AI studio says "Image generation is not connected", and the dish form's studio says "Listing writer not connected" or "AI studio not connected". The dish form itself works and saves as usual.
- Without the model file, the "Remove background" button does not appear.
- Without
MCP_API_KEY,POST /api/mcprefuses every request.
Keys and models
Included with your purchase. Sign in to read, or open it in your download.
Which variable turns on each feature, and the models each one uses by default.
How the assistant works
Included with your purchase. Sign in to read, or open it in your download.
The assistant's tools, how its changes are proposed and confirmed, and where its conversations are kept.
How the AI studio works
Included with your purchase. Sign in to read, or open it in your download.
The studio's modes, looks and generation lifecycle, and where its results are stored.
Background removal
Included with your purchase. Sign in to read, or open it in your download.
Installing the background-removal model and its limits.
The MCP server
Included with your purchase. Sign in to read, or open it in your download.
Connecting a coding agent or another MCP client to the restaurant's tools.
Visitors' own keys in demo mode
Included with your purchase. Sign in to read, or open it in your download.
How a public demo runs the paid features on each visitor's own key.