AI Menu Parser — Flat Price per Menu, No API Key
Pricing
$990.00 / 1,000 menu parseds
AI Menu Parser — Flat Price per Menu, No API Key
One flat price per menu, charged only on success — no API key, no per-item metering. Menu photos in, structured dishes out: translated names, prices, atomic ingredients, EU-14 allergens, dietary type, nutrition estimates. 15 languages.
Pricing
$990.00 / 1,000 menu parseds
Rating
0.0
(0)
Developer
NomadDev
Maintained by CommunityActor stats
0
Bookmarked
2
Total users
1
Monthly active users
6 days ago
Last modified
Categories
Share
AI Menu Parser — Flat Price per Menu
One flat charge per menu. Charged only when parsing succeeds. No API key.
Upload up to 10 photos of a menu (or send URLs/base64 through JSON), get the whole menu back as structured JSON — one record per dish, however many dishes it has. A 12-dish café card and a 60-dish restaurant board cost exactly the same.
Each dish record includes:
name(translated to your language) +originalName(as printed)category,price(with currency, as shown)ingredients— atomic base ingredients, each with an English database name, translated display name, and EU-14 allergens with confidencedietaryType— Vegan / Vegetarian / Pescetarian / Other, with explanationnutritionInfo— estimated serving size, calories, protein, fat, carbsstory— origin story / cultural significanceisAlcoholicfor beverages
15 output languages. The prompt is the production pipeline of a dietary-restrictions travel app — battle-tested on real menus worldwide.
Why flat pricing
You know the cost before you run: one menu, one price. No per-dish metering, no bill surprises on dense menus. If the parse fails or the photos are unreadable, you are not charged — a non-billed diagnostic row explains what went wrong instead.
Prefer usage-based pricing or your own Gemini key? The same parser is also listed as ai-menu-parser (bring your own key, per dish) and ai-menu-parser-managed (no key, per dish).
Input example
Notes
- The Console accepts local JPEG, PNG, or WebP uploads directly. API callers
may use HTTP(S) URLs, base64 data URIs, or raw base64 in
imageUrls. - Each decoded image is limited to 10 MiB. Inline payloads and signed URL credentials are replaced with safe references in output records and logs.
- Up to 10 images per run, parsed together as one menu. One run = one menu — for several restaurants, start one run each.
- Unreadable items are skipped rather than guessed; empty results produce a non-billed diagnostic row explaining why.
Support & links
- Questions, bug reports and FAQ: github.com/Exdenta/traveleat-support
- This actor runs the same menu pipeline as Travel Eat — scan a menu, get allergens, ingredients and dietary filters in 36 languages.
