Use cases and integration patterns

1. AI itinerary assistants

Question: “Plan two days in Madrid with great museums, parks and restaurants.”

Pattern: Resolve Madrid → discover attractions and restaurants by type → filter for the traveler's preferences → rank candidates using Place Score → fetch rich details → let the application build a schedule, with a separate route/time provider. Do not treat a place recommendation as confirmation that it will be open at a particular time.

2. Place-knowledge assistants

Question: “Tell me about the Prado Museum and how to find it.”

Pattern: Resolve the place or search within Madrid → fetch get_venue (MCP) or node (GraphQL) → ground the answer in descriptions, address, coordinates and original source links. Sanitize any HTML before rendering.

3. Local discovery and neighbourhood guides

Question: “Which areas of London should we explore?”

Pattern: Resolve London → list direct subareas → look for places within each subarea. Use the hierarchy rather than assuming that neighbourhood strings in addresses form the complete geographic model.

4. Personalized venue recommendations

Question: “Find family-friendly outdoor attractions that are highly ranked.”

Pattern: Apply audience, environment and score filters, then compare resulting venues. Attribute arrays use AND semantics: request only the tags that must all be present.

5. Tourism and hospitality content enrichment

Use GraphQL to request only the title, address, category, coordinates and descriptions your product needs. Reuse stable IDs and resolve full details on demand. Plan for absent optional fields and dynamic data updates.

Example prompts for agents

• “Find affordable Italian restaurants in Prague with at least a 4.5 rating and 50 reviews.”
• “Show scenic outdoor attractions suitable for families in Scotland.”
• “Find rooftop bars around central Madrid; use short keyword search scoped to Madrid.”
• “Show attractions with Place Score at least 85.”
• “Explore neighbourhoods in a city, then recommend notable local venues.”

Integration tips

Prefer one call to resolve the destination, then bounded filtered queries. Use pagination rather than requesting everything. Fetch full details selectively. Combine Evendo with external scheduling or real-time services when a use case requires them.