Early data. We’re still double-checking entries.

Methodology & sources

This page explains how we set each label, what counts as a source, and how the announced-vs.-found scoreboard is built. A plain-English summary comes first. The strict rules that follow it are for anyone who wants to check our work. The same rules are in the project’s process documents.

How this works

Food Robot Index is a free list of robots working in restaurants and other food businesses. Every entry needs a public source, like a company announcement, a news story, or an official filing. We write down the date and keep a copy of the page. We don’t use private tips, and we never guess. If the proof is thin, we mark the entry “not yet confirmed” instead of leaving it out. When the news goes quiet, we ask for a fresh check. We don’t assume a robot is gone. This is a public record, not investment advice.

What the labels mean

in use
A dated source says the robot is working at this named place, in everyday service.
in a trial
A dated source says the robot is at this named place, but as a test or trial. It is not in everyday service yet.
announced
The company, or a major news outlet, said a robot will be installed at this named place. We have no sign yet that it is there.
removed
A robot was here before, and a dated source shows it is gone. A closed restaurant counts. We never say the robot “failed.”
not yet confirmed
We saw a public sign, such as a photo or a job post, but not enough proof to call it in use, in a trial, or announced.

The full rules, written for people who want to check our work, are on the methodology page.

Related documents on this site: verification rules (markdown), source monitoring plan (markdown).

Public sources only. Food Robot Index uses no logins, no scraping that breaks a site’s terms or robots.txt, and no private or leaked data. Every install needs a source. If the evidence is weak, use unconfirmed. Do not omit the signal, and do not overstate it. This is a public record, not investment advice.

Status bars

Each location-level record has exactly one current status. Announcement-level count claims belong in data/announcements.json, not here.

unconfirmed

Use when a public signal exists but does not meet the bar for announced, piloting, live, or removed.

Typical cases:

unconfirmed is a full status. Unconfirmed rows are public, like the others. Confidence is usually low.

announced

The location itself must be identified.

A first-party maker or operator source, or a tier-1/tier-2 news source, states a plan or commitment to install a named robot at that named site. There is no evidence yet that the unit is on site in a pilot or in service.

Chain-wide or count claims (“100 units,” “rollout across the brand”) are not location-level announced rows. Record them as announcements. Create an announced install only when the specific site is named.

A trade-show booth, lab demo, or “coming soon” teaser with no site name is not an install.

piloting

A dated first-party source, or a dated tier-1/tier-2 press or local-news source, says the robot is on site at the named location. The source may call it a test, pilot, limited trial, or “in a restaurant for testing,” but must not describe it as regular production service.

One such source is enough if it is first-party or tier-1/tier-2 and names the site. Otherwise two independent public signals are required.

live

All of the following:

1. The specific location is named (store, venue, or equivalent).

2. The robot product (or a clearly identified product family) is named or unambiguously pictured in context.

3. A dated source says the unit is in regular service, not only on display or in a trial.

Evidence options (either one):

Trade-show, investor-day, and lab demonstrations are not live restaurant installs.

removed

The site previously had a piloting or live (or, rarely, announced) record, and dated evidence shows the unit is no longer there.

Acceptable evidence is any one of these: a first-party statement that the unit was removed or decommissioned; credible press saying the same; or two independent recent on-site signals of absence plus the prior install record. If a store closed, mark the row removed and note the closure. Do not say the robot “failed.”

Do not mark removed only because sources went quiet. Quiet sources trigger needs_reverification and leave status unchanged until there is positive evidence.

Source tiers

TierTypesWhat it can do
1First-party operator or maker newsroom; official IR; SEC filing; on-the-record earnings remark posted on IR or EDGARCan establish any status if it names the needed facts and is dated
2Established trade press, local news, national news, or a press wire quoting a named officialSame as tier 1 for location-level facts those outlets actually state
3Official social accounts of the maker or operatorCan support announced or piloting when they name a site and date; alone they are not enough for live unless they are clearly an official newsroom equivalent (link the underlying post and archive it)
4User social posts, reviews, job postings, unlabeled photos or videosLeads and supporting signals only. A tier-4 item may be one of two independent signals; it cannot be the sole basis for live or removed

Independence means different organizations, not a syndicated copy of the same release. A maker press release and a wire reprint of that release count as one signal.

Staleness

Proposed windows are also listed in open-questions.md and can be tightened after the first seed pass.

Social posts, reviews, and job postings

Archiving

When a source is used to add a record or change a status, capture a public archive, preferably the Wayback Machine (https://web.archive.org/save/{url} or a save that produces a snapshot URL). Store that URL in archive_url.

If the archive fails, keep url, accessed_date, and a short quote_excerpt, set archive_url to null, and note the failure. Do not use an archive service that requires a login.

Re-archive if the live page changes in a way that affects the cited fact.

Removals and conflicts

Confidence

Map and timeline

Browse, search and near me

AI-assisted summaries

What counts as a robot

We list robots that make, cook, serve or deliver food and drinks inside a venue. That includes in-restaurant runner and bussing robots, fry stations, bowl lines and drink makers. As of Nov 18, 2026 it also includes every automated coffee kiosk, such as the Touch Coffee Smart Bar: a self-serve machine that makes a drink with no staff at the counter. A kiosk is listed only when a public, dated source names the place. A kiosk that only shows up in a company’s own social post is labeled “not yet confirmed”. Sidewalk delivery robots, cleaning-only robots and factory lines stay out.

Out of bounds