Vegan restaurant intelligence for your product
Matching vegan dishes for US restaurants, with the date each menu was collected, so your planner recommends real meals, not guesses.
60-day pilot for three US travel and planning products. The founders help you integrate.
Your planner today
Dinner: Niu Kitchen
104 NE 2nd Ave, Miami
With Compass
Dinner: Niu Kitchen
104 NE 2nd Ave, Miami
Vegan options: Vegan Paella, Artichoke, Pa Amb Tomàquet
Menu collected Oct 16, 2026
The challenge your team faces
Your app finds the restaurant, fits it into the itinerary, and explains why it belongs. Then a vegan user asks what they can actually eat there. That is where a convincing recommendation needs supporting information.
One traveler's dietary needs often decide where the whole group eats, so a restaurant only works if they can order something there.
Do these follow-up questions sound familiar?
Menu detail
Knowing a place is vegan-friendly does not tell your product which menu items support that claim. A plausible dish name or ingredient list can sound just as convincing as a supported one.
Your team needs to distinguish menu evidence from generated detail.
Supporting information
A confident answer needs a clear source and a menu collection date. Your team needs both to explain the recommendation.
Your team needs to see what the answer rests on.
User experience
Your product recommends a restaurant, then sends the user to other sites to find out whether it suits them. Give them the menu details behind the recommendation in your own product.
Give users useful context inside your product.
When a recommendation cannot stand up to a simple follow-up, it is your product's credibility on the line.
You have already built the experience. Your team shouldn't have to build and maintain a specialist vegan evidence layer just to explain its restaurant recommendations.
Your users deserve to know what supports a recommendation.
How Compass helps
Keep the recommendation experience you have built. Compass adds vegan dishes and menu collection dates for US restaurants, so your product can explain its recommendations.
Read how we handle evidence →At Estancia 460, Compass found 9 vegan dishes on the collected menu, but not enough for a meal. It returned “unknown” instead of guessing.
See the full result →What you can build
Start with the task your product needs to accomplish.
Help users discover restaurants for their vegan or plant-based preferences, with information your product can use to explain the results.
Search API
Explore restaurant search →Already have restaurant records? Match them with Compass to add the vegan information available for each place.
Enrich API
Explore restaurant enrichment →Check a restaurant against a user's profile and get a suitability decision with the reasons behind it.
Decision API
Explore suitability decisions →See the difference
Two real results: a restaurant with vegan dishes, and one where Compass says there isn't enough to go on.
Each menu date is the date Compass collected that menu, so your product can show users how recent the evidence is.
{
"matched": true,
"restaurant": { "name": "Niu Kitchen",
"vegan_dining": {
"matched_dishes": [
{ "name": "Vegan Paella" },
{ "name": "Artichoke" },
{ "name": "Pa Amb Tomàquet" } ],
"menu_collected_at": "2026-10-16T12:30:02.649Z"
} }
}Real Compass result (shortened)
See the full result →When Compass isn't sure, it says so
460 Greenwich St, New York
Arcadian Greens, Broccoli with Garlic & Olive Oil, Fries, Grilled Asparagus, Grilled Vegetables
Verdict: unknown · VEGAN_OPTIONS_LIMITED
“Compass found vegan dishes on the collected menu, but not enough for a meal (menu collected 2026-10-13).”
Menu collected Oct 13, 2026.
What this makes possible
Show users why a restaurant works for them, while giving your team a clear basis for the recommendation.
Use the menu information returned with a result to explain why a restaurant matches a user's preferences.
Show when Compass collected the menu alongside the dishes behind your recommendation.
Add Compass's vegan context alongside your existing restaurant provider or AI workflow.
Who it helps
Add vegan restaurant options and explanations to itineraries and destination recommendations.
Add vegan context to restaurant records without replacing your broader place-data provider.
Connect your product through our API, or use our connector for compatible AI tools. The developer guides explain how to find or match a restaurant and assess it for a user's profile.
Follow the API quickstart and integration examples.
Read the quickstart →Connect through MCP in compatible tools such as Claude Desktop, Cursor, or Codex.
View the AI connector guide →Get started
Check Compass against the restaurants and questions that matter to your users before you integrate.
and send back the vegan dishes and menu dates.
during a 60-day pilot.
Before you start
US restaurants. Coverage is deepest in the city areas we've processed. Ask us for a sample in your city.
Yes. You can match a restaurant you already have and add the available Compass vegan context, alongside your existing place data.
Compass can report that it does not have enough evidence to confirm a match. Your product can show that uncertainty and ask users to confirm details with the restaurant.
No. Compass is focused on vegan and plant-based suitability. It is not an allergy-certification service and does not replace direct restaurant confirmation for safety-sensitive decisions.
Yes. The free Sandbox plan includes restaurant search, enrichment, and suitability decisions, with 1,000 credits per month. No credit card is required. See pricing for limits and account terms.
3 slots
Free API access for 60 days, hands-on integration help, and a founder-led channel — for live products with real users and a US audience.
Build recommendations that explain why a restaurant may suit them—and give your team a clear basis for every answer. Start by testing Compass with the places your users care about.
Talk about your integration →