# mpire > mpire connects every system a multi-branch restaurant group or retail brand runs (POS, ERP, inventory, delivery apps, > payments, banks, sheets and the company's own AI agents) and checks the food and the money across them every day, > down to the ingredient. Each gap goes, with its money and its papers, to the person who knows what happened; finance > approves; the month closes signed, with the trail for the auditor. mpire is in closed beta: an invited company starts > at https://mpireapp.com/join. mpire reads and never changes anything in a company's systems. Every figure carries its basis, its window and its coverage; what isn't known is returned as unknown, never as a number. Each company's data sits in its own walled space, and no other business sees it unless the company shares it: chosen, expiring, revocable, logged. Data is kept in Frankfurt (the EU) today. Items marked "Soon" are shown as they will work and are not live yet; https://mpireapp.com/previews lists what is built and what is next. ## Pricing - Free to start: a few sources, the daily checks, each gap sent to the person who knows what happened, and links for suppliers and accountants. - Paid to go deeper: more sources, longer history, deeper analytics and unlimited AI connections. Talk to us: hello@mpireapp.com. ## The site's versions - English, the US version: https://mpireapp.com (its example is a made-up restaurant group in Austin, in dollars). - The MENA version, in English and in Arabic: its own section below. ## What mpire reads - Read today: any database on the company's own server (a POS, an ERP, a stock system) through a read-only connector, Shopify every hour, Meta Ads, sheets in Google Drive and Excel, and statement files (banks, suppliers, delivery apps). - In the US, still to come: Toast, Square and Oracle MICROS Simphony (Soon: not live yet); QuickBooks and NetSuite (Soon: not live yet); DoorDash, Uber Eats and Grubhub statements (Soon: not live yet); Stripe (Soon: not live yet); Shopify Payments' payouts (Soon: not live yet); UPS and FedEx (Soon: not live yet). ## For AI agents - One connector, MCP and an API with the same tools, within the company's permissions. - Claude, ChatGPT and Gemini connect by signing in (OAuth, with dynamic client registration): mpire's own page says what the AI will read, as the person and in their role; it writes nothing unless the owner allows it, and the person removes it in one click. - The company's own agents are members: a role, a scope, an expiry, a log of every read, revoked at once. - Read tools: `company`, `list_pages`, `read_page`, `figures`, `provenance`, `definition`, `findings`, `context_search`, `capabilities`. - Write tools: `add_explanation`, `submit_finding`, `send_to_mpire`. Every write is attributed to the agent and to the person who set it up, and logged; an agent never changes a computed number, and its money is shown as its estimate. - A person's waiting asks arrive inside their own ChatGPT or Claude, and their answer reaches mpire as their own explanation ("via Claude", "via ChatGPT"). - AI work: every figure an agent cites is checked against mpire's numbers; a person can send it on, make it a gap, hand it to another agent or keep it as company knowledge; each agent has a track record (Soon: not live yet). - Skills files for the company's agents, kept current as finance's rules change (Soon: not live yet); onboarding run by the company's own agent, the owner confirming by email before any data moves (Soon: not live yet). - The controls stay with people: approving, signing off the month, reopening a signed period, giving an AI access, adding an agent. Asked for from a chat, they open a one-tap confirm in mpire. - The tools' reference, the OpenAPI file (/v1/agent/openapi.json on the API) and a small CLI (Soon: not live yet). ## Pages The US version's addresses; the same page is at /mena/… in the MENA version's English and at /ar/… in Arabic. - [How it works](https://mpireapp.com/how-it-works): the whole of mpire, stage by stage - [For restaurant groups](https://mpireapp.com/restaurants): food cost, the commissary or central kitchen, the delivery apps and cash - [For retail brands](https://mpireapp.com/retail): Shopify, payments, returns and Meta Ads - [For AI agents](https://mpireapp.com/ai): signing in from Claude, ChatGPT or Gemini, the tools, agents as members, their work checked - [One gap, start to finish](https://mpireapp.com/walkthrough): a gap from found to signed - [Security](https://mpireapp.com/security): what mpire reads, what it never reads, and who can see it - [Pricing](https://mpireapp.com/pricing) and [Contact](https://mpireapp.com/contact) - [What's built, and what's next](https://mpireapp.com/previews): every built feature, then every feature marked "Soon", as it will work - [Closed beta](https://mpireapp.com/join): an invited company starts here - The demo company, opened with a code from mpire: https://app.mpireapp.com/demo?lang=en (the US group), ?lang=ar or ?lang=en®ion=mena (the MENA group) ## The MENA version Arabic first, built for restaurant groups and retail brands across MENA (https://mpireapp.com/mena in English, https://mpireapp.com/ar in Arabic). Its example is a made-up group in Riyadh and Jeddah, in riyals. - Read today there too: Paymob, Bosta's cash on delivery, and Talabat's statements in Egypt. - Still to come: Foodics (Soon: not live yet); Oracle MICROS, Odoo, Geidea, Tap and the other Saudi systems (Soon: not live yet); HungerStation, Jahez and Keeta statements (Soon: not live yet); WhatsApp (Soon: not live yet); e-invoices matched against ZATCA or Egypt's tax authority (Soon: not live yet). - Where data is kept: Frankfurt today; Doha, Dammam or the company's own servers to come.