Agents, not dashboards
An AI agent for every role in your restaurant
Restaurant Agent connects to the systems you already run — accounting, payments, payroll, reservations — and turns them into tools your team can drive by simply saying what they need.
One platform, five agents
Every role gets its own agent with exactly the tools that role is trusted with — nothing more.
Owner
P&L this month vs last, labor as % of sales, cash position — asked in plain language, answered from your books.
Manager
Who's over on labor, what stock is low, which timecards need approval — handled without opening five dashboards.
Host
Seat the party, text the waitlist, hold a table — the floor runs on intent, not screens.
Server
Fire the apps, split the check, comp an item — with manager approval built into the flow.
Guest
Order, pay, tip, and book through chat — on a public surface that's structurally walled off from staff systems.
Multi-unit operators get the same agents scoped across locations — compare stores, flag outliers, roll up the numbers.
How it works
Connect your systems
Link accounting, payments, payroll, and reservations with a guided OAuth flow — QuickBooks and Stripe today, more connectors on the way.
Each role gets an agent
Every persona sees only the tools its role is allowed to use. Access is decided by the gateway policy, never by the client.
State intent, review, confirm
Ask for what you need. Reads come back instantly; anything with financial or labor effect arrives as a proposal for you to approve.
Built safe from the first line of code
Agents that can touch money and payroll demand more than a disclaimer. Safety here is architecture, not policy text.
Two trust domains, structurally separate
The public guest agent and the authenticated staff agents never share a gateway, a tool registry, or a resolution path. A guest is never one jailbreak away from a refund or a payroll action.
Nothing moves money without you
Every action that touches money, payroll, or schedules is propose-then-confirm: the agent drafts it, a human signs off, and the write lands in an audit log.
Your credentials stay yours
Connector tokens are encrypted at rest and bound to your restaurant's tenant, so one restaurant's keys can never be read as another's.
Stop navigating screens. Start stating intent.
Set up your restaurant in minutes, connect QuickBooks and Stripe, and give your team agents that do the work.