Restaurant Data API: the foodservice data layer for AI agents
Dashmote is the restaurant and foodservice data layer for AI-native teams and the agents they run. Outlets, menus and prices, beverage brands on menus, delivery app listings and availability, reviews, social signals and lead scores, covering 60+ countries and 100+ platforms. Connect it by API or MCP to any LLM or agent harness: frontier models such as Claude, GPT, Gemini and Microsoft Copilot, local and open models on your own hardware, and agent frameworks such as OpenClaw and Hermes Agent (Nous Research).
The trusted intelligence layer for teams selling to Hospitality & Retail
Built for AI-native teams, not for spreadsheets
Most foodservice data still arrives as a file: a quarterly export, a dashboard login, a list someone has to clean before anyone can use it. AI-native teams work differently. Their analysts ask an assistant, their reps ask a copilot, and their agents run jobs overnight. Those agents need a data source they can query on their own, at the moment the question is asked.
The Dashmote Restaurant Data API is that source. It puts licensed restaurant, menu and delivery data directly behind your models and agents, so an answer about outlets, prices or listings comes from dated records rather than from a web search and a guess. Your own apps, your data warehouse and your AI tools all read from the same governed layer, so the number in the board deck and the number your agent quotes are the same number.
Any model, any harness, one data layer
Dashmote does not lock you into one AI vendor. The same data connects by API or MCP to whatever your team runs today, and to whatever it switches to next quarter:
- Frontier models: Claude, GPT, Gemini and Microsoft Copilot.
- Local and open models: models you run on your own machines or in your own cloud, for teams that keep prompts and reasoning in-house.
- Agent frameworks and harnesses: OpenClaw, the free open-source personal AI agent that runs on your own machine and takes instructions through messaging apps; Hermes Agent (Nous Research), the open-source agent that connects to MCP servers and lets you switch model providers; and any other framework that can call an API or an MCP server.
- Your own software: internal apps, sales tools and warehouse jobs that need the same records your agents see.
Swap the model and the data stays. That matters when the AI landscape changes every few months: the restaurant data layer is the part of your stack that should not have to be rebuilt each time.
Which countries, platforms and data a workspace sees depends on its licence.
What your agents can answer
With Dashmote connected, an assistant or agent can work through the questions foodservice teams ask every week:
- Outlets: which bars, restaurants and cafes exist in a city or region, what type they are, and which chain or operator they belong to.
- Menus and prices: what an outlet sells and at what price, and how prices for the same item compare across a market.
- Beverage brands on menus: which drinks brands appear on which menus, and where a competitor is listed and you are not.
- Delivery app listings and availability: which outlets are live on which delivery platforms, by city, and how that changes from one refresh to the next.
- Reviews and social signals: how outlets are rated and talked about, and which ones are gaining momentum.
- Lead scores: which outlets fit your brand best, so the next visit or the next deal goes where it counts.
Your team asks in plain language. The agent picks up the right data and answers within what your workspace licenses.
For eCommerce managers: the delivery digital shelf
On delivery apps, the menu is the shelf. An eCommerce manager needs to know where the brand is listed, at what price, and whether it is actually available, platform by platform and city by city. With Dashmote behind an agent, those checks stop being a monthly manual audit:
- Ask which key accounts list your products on one platform but not another.
- Compare the price of your products, and your competitors', across platforms and cities.
- See where listings dropped out since the last refresh, so the account team can follow up while it still matters.
- Feed the same results into your own dashboards and alerts, so the agent and the report agree.
The result is a digital shelf you can manage week to week, refreshed monthly, rather than a snapshot that is out of date by the time it is shared.
For field sales reps: which outlets to visit first
A rep with a full territory has one real question each morning: where should I go today? Connected to Dashmote, a sales copilot can answer it with outlet-level facts instead of gut feel:
- Which outlets in my territory do not carry our brand yet, and what do they serve instead?
- Which outlets score highest for fit, so the first visits go to the best prospects?
- What does this outlet's menu look like, and which drinks are on it, before I walk in?
- Which outlets are new, newly listed on delivery, or rising in reviews?
Reps get a ranked list and the talking points behind it. Managers get a consistent way to plan coverage across the team.
Outlets and storefronts: the one definition to know
An outlet is a physical venue. A storefront is that venue's listing on one delivery app, so a venue on three apps has three storefronts. Every answer says which of the two it counts. Do not add storefront counts together and read the total as a number of venues; Dashmote states the definition so your agents do not make that mistake either.
Governed by design, in plain words
An agent will ask more questions, more often, than any analyst. The data behind it has to be safe to use at that pace:
- Licensed data only. Everything comes from data Dashmote licenses and maintains, not from scraping your agent does on its own.
- Scoped per workspace. Your workspace sees the countries, platforms and data it licenses, and nothing else. Another company's data is never in your answers.
- Dated and defined. Every answer carries its refresh month and the definition of what it counts, so a figure can be checked and quoted with confidence.
- Structured answers. Agents get clean, consistent records, which keeps their reasoning grounded and their outputs repeatable.
The business case for the budget holder
Whether you lead eCommerce, sales, or data and AI, the case comes down to the same three points:
- Head of eCommerce: a delivery digital shelf your team can query any day, across platforms and cities, without commissioning a new audit each time.
- Head of Sales: reps who walk into the right outlets with the right facts, ranked by fit, so territory time turns into listings.
- Data or AI lead: one licensed foodservice data layer for every model and agent you run, frontier or local, with no scraping to maintain and no vendor lock-in.
- Everyone: menus, prices and delivery listings refreshed monthly, with definitions stated, so the numbers hold up when they reach leadership.
How to get access
Dashmote is set up per workspace, not through a public sign-up. Tell us which countries, platforms and questions matter to your team, and which AI tools or agents you run. Our team sets up the connection for your workspace and makes sure your first questions return the answers you expect.
Prefer to plug the data straight into an assistant or agent harness? See the Restaurant Data MCP. For the full list of AI tools and connectors, see AI connectors.
Frequently asked questions
Which AI tools does it work with?
Any LLM or agent harness that can call an API or an MCP server. That includes frontier models such as Claude, GPT, Gemini and Microsoft Copilot, agent frameworks such as OpenClaw and Hermes Agent (Nous Research), and your own internal apps.
Does it work with local models?
Yes. Teams that run open or local models on their own hardware connect the same way, by API or MCP. The model stays where you run it; Dashmote supplies the restaurant and delivery data.
Do I need developers?
Not to get started. Our team sets up the connection for your workspace and your assistant or agent. Developers are useful if you want to build the data into your own apps or warehouse, and the same access covers that too.
Is the data licensed?
Yes. Dashmote data is licensed per workspace. Your agents answer only within the countries, platforms and data your workspace licenses, and every answer carries its refresh month and definition.
Does it cover delivery app menus and prices?
Yes, for the platforms and countries your workspace licenses: menus, item prices, listings and availability as seen on delivery apps, refreshed monthly.
How do I get access?
Request access and tell us what your team needs to answer. There is no public sign-up; our team sets up the connection for your workspace.