Plans like a chef
Grams per guest become packs in Valio's own units, with the arithmetic and its sources one click away.
Junction 2026 · Valio Aimo: Trusted Trade Agents
Mandate plans a kitchen's order from Valio Aimo's catalogue, finds substitutes when products run out, and orders on its own only within the chef's mandate. Everything else waits for a person, with the reason.
Every visitor gets a private sandbox. Nothing is sent to Valio.
Whole ham is out. Ordered HK Palvikinkku instead.
Same use, Valio states stock for it, and it fits the weekly cap.
Within the mandateA substitute changes the allergens.
The chef never delegates allergen changes, so it waits for a person.
Needs your approvalAn extra order would pass the hard limit.
No approval can lift it, even if the order is split.
RefusedThe limits are data, checked in code at the moment of ordering, the same way for the kitchen screen, the built-in agent and any outside agent.
Grams per guest become packs in Valio's own units, with the arithmetic and its sources one click away.
If the price or the quantity changes after approval, the approval is void and the screen shows what changed.
A retried order returns the same receipt. Products whose supply Valio doesn't state are labelled unknown, never counted as covered.
Mandate is an open gate, not a closed app. Your agent gets the same tools over MCP and REST as ours, inside your own sandbox. It can plan and order within the mandate. It can never approve.
Get a key. Open app.mandate.kitchen/agents to mint one for your sandbox.
Connect. Point any MCP client at https://app.mandate.kitchen/mcp/k/<key>.
Start. Call get_context, then ask it to plan the buffet. Try asking it to approve.
Labelled on every screen, too.