How Much Does It Cost to AI-Parse a Menu? (Under a Cent.)

When people hear that Travel Eat runs every menu through a large AI model — extracting each dish with its price, ingredients, allergens, dietary type, and nutrition estimate — the first question is usually some version of "doesn't that cost a fortune?"

It's a fair question, because three years ago the answer was yes. Today the honest answer is: parsing a full menu costs about as much as a grain of rice. Under a cent per dish, all-in, and the raw AI portion is a rounding error. Here's the actual math.

What "parsing a menu" means here

To be clear about what you're pricing: this isn't OCR. For every dish, the pipeline extracts:

• Name (translated) and original name as printed
• Category and price, with currency
• Atomic ingredients — pesto gets decomposed into basil, pine nuts, parmesan, olive oil — each with EU-14 allergen flags and confidence levels
• Dietary type (vegan / vegetarian / pescetarian) with an explanation
• Estimated nutrition per serving
• A one-line origin story, because food is culture

That's a lot of structured output per dish, and output tokens are the expensive kind. Keep that in mind — this is the maximalist version of menu parsing, and it still costs pennies.

The math

Our pipeline runs on Gemini 2.5 Flash by default. Take a typical menu: six photos, about 35 dishes.

Input: six menu photos plus our parsing prompt come to roughly 10,000 tokens. At Google's published Flash input rate (about $0.30 per million tokens as we write this), that's $0.003.

Output: 35 dishes at a few hundred tokens each is roughly 9,000 tokens of structured JSON. At about $2.50 per million output tokens, that's $0.022.

So the AI bill for the entire menu is around 2–3 cents — well under a tenth of a cent per dish. Simpler menus, or the Flash-Lite model (which is what our photo matcher uses), come in several times cheaper still. Model prices drift — always check Google's current pricing — but they've only drifted one direction for years: down.

Why we made it bring-your-own-key

When we published our pipeline as public Apify actors, we had a pricing decision to make. The industry-standard move is to bundle the AI cost into a per-menu fee with a healthy markup — the going rate for menu extraction on scraping marketplaces is somewhere between $0.05 and $0.10 per menu, and you never see where the money goes.

We went the other way: you bring your own Gemini key (free to create, with a generous free tier), and you pay Google's actual rates for the AI — the 2–3 cents above, or $0.00 while you're inside the free tier. The actor itself charges a small fee for the pipeline: the AI Restaurant Menu Parser starts at half a cent per run plus a fifth of a cent per dish extracted.

All-in for that 35-dish menu: about $0.075 in actor fees + ~$0.02 to Google = roughly $0.10, or about a quarter of a cent per dish — with the full allergen and nutrition treatment, not just names and prices. And because the AI spend is on your key, you control the quota, you see the real cost, and when Google cuts prices again, you pocket the difference instead of us.

The whole toolkit

The parser is one of three actors we've published from Travel Eat's production pipeline:

• AI Restaurant Menu Parser — menu photo URLs in, structured dishes out. The math above.
• Google Maps Menu Scraper — don't have photos? Start from a Google Maps place URL; it finds the menu photos and parses them in one run.
• Restaurant Dish Photo Matcher — attach the place's real food photos to each parsed dish, for a fraction of a cent per photo.

And if you'd rather skip the key setup entirely, each actor has a managed twin with the API keys included — Menu Parser, Menu Scraper, Photo Matcher. You pay a higher per-dish rate for the convenience, which is exactly the trade-off this post is about: bring your own key and the AI is nearly free; have us bring it and you're paying for zero configuration.

Three years ago, "structured menu data with allergen analysis" was an enterprise data contract with a sales call attached. Now it's a cent and an API key. We think that's worth writing down.

Travel Eat scans, translates, and allergen-checks restaurant menus in 36 languages — powered by exactly this pipeline.