Data sources: what exists, what is legitimate

Research date: 2026-10-08. Several platform sites were not reachable from the research environment, so some facts come from search excerpts and press. Anything marked unverified must be checked by hand before it is quoted in the pitch.

#Conclusion

No delivery platform offers an API that returns what a consumer sees at checkout (item price as shown in the app, delivery fee, service fee, promotions) for stores other than your own. Every official API is merchant-side: a restaurant authorizes a software provider, and the API moves that restaurant's menu and orders between its POS and the marketplace.

So cart-level comparison stays an observation problem. The defensible sources are:

1. what users see in their own sessions (the extension, observe-only);
2. ground truth shared by partner restaurants;
3. merchant APIs (Open Delivery, Keeta, iFood) as the merchant-verified price roadmap, not as competitor data.

See ADR-007 for why a dedicated account plus a headless scraper is out.

#Keeta (Meituan)

• Pilot in Santos / São Vicente from 30 Oct 2025; São Paulo and 8 metro cities from 1 Dec 2025. Stated goal: 100 cities by mid-2026. Actual 2026 footprint unverified. (Mercado & Consumo, Canaltech)
• The Keeta API is a merchant / software-provider integration API, not a price-reading API (docs):
  • an Open Delivery variant ("based on Open Delivery v1.5.0"): menu push (POST /merchantUpdate), menu pull (GET /merchant), orders, events;
  • a Standard API with AppId, a secret "supplied by the Keeta team", OAuth 2.0;
  • credentials are per software provider, and each merchant must authorize it through a login portal;
  • access starts with an NDA with Keeta.
• Consumer ordering appears to be app-only (no web storefront confirmed).

#Other platforms

Platform	Official API	Scope	Access
iFood	developer.ifood.com.br (Merchant, Catalog, Order, Financial, Review)	merchants that linked the app	developer account; a CNPJ (MEI) per a community report (unverified); test store; homologation
99Food (DiDi)	none public; integrates through Open Delivery and POS vendors	merchant	integrator contract
Rappi	Partners API (menus, stock, orders)	"allies" only	manual onboarding through a Rappi contact
aiqfome, Zé Delivery, Daki, James	none found	—	—
Uber Eats	left restaurant delivery in Brazil in 2022; the Uber app now shows iFood inventory	—	—

99Food relaunched in 2025 and reported about 70 cities in March 2026 (Mercado & Consumo). It publishes its fee rules, which help model fees. A 99Food web storefront is reported in 2025 press (unverified today).

#Open Delivery (Abrasel)

• Open, Apache-2.0 REST standard: spec v1.7.1; v2 in design.
• Roles: Software Service (the restaurant's POS), Ordering Application (the marketplace), Logistic Service, hubs.
• The merchant's POS serves GET /v1/merchant (info, services, menus); credentials are "generated BY MERCHANT".
• Implemented by 99Food and Keeta (Giro News), Rappi (2022 announcement) and 100+ POS vendors. iFood: unverified.
• What it gives an aggregator: with each restaurant's opt-in, its base menu and prices. What it does not give: each marketplace's price, fees or promotions.

This fits UPAY3FOOD as a merchant-verified layer: a connector that reads GET /v1/merchant from opted-in restaurants and compares their own price with what users observe on each marketplace.

#Public pages and routing (founder check, 2026-10-10)

iFood shop pages and menus can be browsed without logging in once an address area is set. This has two consequences:

• the extension's menu views work for anyone, logged in or not;
• a recommendation can send any user to a shop or item link, and on phones that link opens the iFood app.

The same routing will point to other platforms (Keeta, 99Food, Rappi) when they are the cheapest. UPAY3FOOD still does not fetch those pages from a server (ADR-007); it only links to them.

#Other legitimate sources

• Partner restaurants: a few açaí shops listed on 2–3 platforms share their per-platform prices and fees. Cheap, consented, ground truth.
• Google Places API: place attributes only, no item menus. Useful for matching the same store across platforms, not for prices.
• Affiliate programs: none found for iFood, Keeta or 99Food.

#Legal context (summary, not legal advice)

• Consumer ToS clauses were not retrieved. Read the current terms of each platform for "automatizado", "robô", "coleta", "engenharia reversa" and "uso pessoal" before the pitch.
• iFood's partner, courier and developer terms prohibit reverse engineering (developer terms).
• No Brazilian precedent specific to price scraping was found. Theories cited by commentators: unfair competition (LPI art. 195), copyright, and LGPD when personal data is involved (Demarest).
• The sector is litigious:
  • iFood sued Meituan / Keeta alleging corporate espionage (Startups);
  • in May 2026, 99Food was convicted for unlawful comparative advertising ("Taxômetro") (Olhar Digital). Any public comparison UPAY3FOOD shows must be dated, observed and accurate.
• CADE's 2023 settlement limits iFood exclusivity (Tecnoblog). More restaurants on several apps (multi-homing) is the premise of the comparison. It is a market argument, not a data right.

#Connector plan

Order	Source	Provenance label	Status
1	iFood in the user's session (extension)	live	calibrating on real pages
2	99Food web in the user's session, if a storefront exists	live	to verify
3	Keeta: user-submitted observation (manual entry, app-only)	manually observed	to build
4	Partner restaurants	imported, merchant-verified	outreach
5	Open Delivery GET /v1/merchant for opted-in merchants	live, merchant-verified	roadmap
—	Dedicated account + headless scraper	—	rejected (ADR-007)