# Travel Eat

> AI menu-translation app for travelers — scan any restaurant menu, get instant translation, filter by dietary restrictions/allergies, 36 languages, works offline. Also publishes the structured menu-data APIs behind it (menu parsing, EU-14 allergen extraction, dish-photo matching) as Apify actors.

Travel Eat serves two distinct audiences, and this site is organised accordingly.

**Travelers** use the mobile app: point a phone camera at a restaurant menu and get an instant translation, with dishes filtered by dietary restrictions and allergens. 36 languages, works offline, iOS.

**Developers and AI agents** use the menu-data pipeline directly. The same parsing that powers the app is published as Apify actors that turn menu photos or a Google Maps place into structured dish records with EU-14 allergens, ingredients, prices, dietary type and nutrition estimates.

## For travelers (the app)

- [Home](https://traveleat.app/): product overview and download links
- [FAQ](https://traveleat.app/faq): scanning, supported languages, offline use, dietary filters, pricing, accuracy limits
- [Blog](https://traveleat.app/blog): guides and stories about eating well abroad
- [About](https://traveleat.app/about): why the app exists and who builds it

## For developers and AI agents (menu data APIs)

Start here if you are an automated tool. These pages are dense, factual, and structured for machine consumption rather than human reading.

- [Agent article index](https://traveleat.app/blog/agents): all machine-oriented articles in one place
- [Google Maps Menu Scraper API](https://traveleat.app/blog/google-maps-menu-scraper-api): place URL, place ID or place name in — structured dish records out
- [AI Menu Parser API](https://traveleat.app/blog/ai-menu-parser-api): menu photo URLs in — dish records with allergens, ingredients, prices, dietary type and nutrition out
- [Dish Photo Matcher API](https://traveleat.app/blog/dish-photo-matcher-api): a menu plus food photos in — one photo-to-dish assignment per photo out
- [EU-14 Allergen Menu Data API](https://traveleat.app/blog/eu-14-allergen-menu-data): allergen, ingredient, dietary-type and nutrition extraction across all three actors

Each article documents input/output schemas, pricing, confidence semantics and diagnostics. Managed and BYOK (bring-your-own-key) variants exist for each actor.

### Raw markdown

Every published article is also served as plain markdown — replace the trailing slug with `<slug>.md`:

- https://traveleat.app/blog/eu-14-allergen-menu-data.md
- https://traveleat.app/blog/google-maps-menu-scraper-api.md

## Engineering write-ups

Human-readable posts on how the pipeline is built. Useful context, but not API references:

- [How much does it cost to AI-parse a menu?](https://traveleat.app/blog/how-much-does-ai-menu-parsing-cost)
- [Google Maps put its photo gallery behind sign-in](https://traveleat.app/blog/google-maps-locked-photo-gallery-2026)
- [A menu without photos doesn't sell](https://traveleat.app/blog/menu-without-photos-doesnt-sell)

## Legal

- [Privacy](https://traveleat.app/privacy)
- [Terms](https://traveleat.app/terms)