Mandate

Junction 2026 · Valio Aimo: Trusted Trade Agents

An agent that orders for your kitchen, only inside the limits you set.

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.

A mandate the agent can't talk its way around

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

Plans like a chef

Grams per guest become packs in Valio's own units, with the arithmetic and its sources one click away.

Approval covers exact terms

If the price or the quantity changes after approval, the approval is void and the screen shows what changed.

No double orders

A retried order returns the same receipt. Products whose supply Valio doesn't state are labelled unknown, never counted as covered.

Bring your own agent

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.

  1. Get a key. Open app.mandate.kitchen/agents to mint one for your sandbox.

  2. Connect. Point any MCP client at https://app.mandate.kitchen/mcp/k/<key>.

  3. Start. Call get_context, then ask it to plan the buffet. Try asking it to approve.

What's real, what's simulated

Labelled on every screen, too.

  • RealValio Aimo's catalogue, and live price and availability calls for shortlisted products, cached with the time fetched.
  • SimulatedThe booking, the clock, stock on hand, recipes, and the order itself. Valio's API has no order endpoint, so nothing is sent to Valio.
  • ModelsGemini parses requests and ranks substitutes. Every check that decides what may be ordered runs in plain code.