Developers
MCP available

Choose MCP or GraphQL

Both interfaces expose the Evendo World Model. You may use one or both.

MCP GraphQL
Main audience AI assistants and agent frameworks App developers, custom backends, analysis pipelines
Endpoint https://mcp.evendo.com/mcp https://evendo.com/api/locationSearchGraphQL
Interaction tools/list, tools/call in an initialized MCP session HTTPS POST with JSON query and optional variables
Primary capabilities Six higher-level place-discovery tools Six root queries, projections and recursive hierarchy access
Result control Tool-specific response objects Select requested fields and connection pagination
Authentication Not currently required None required
Rate limit 200 requests/minute 200 requests/minute
Best for Agents generating recommendations Apps needing custom field selection or query composition

Mental model

MCP translates common tasks into stable tools, such as resolve_place and find_venues. GraphQL exposes building blocks such as search, descendantsOf and node. The two tool sets do not have one-to-one names, and MCP tool JSON is not GraphQL query syntax.

Goal MCP GraphQL
Resolve a city resolve_place search with city node type
Discover all venues under a city find_venues descendantsOf
Search “ramen” in a known area search_venues search with ancestor_id
List immediate child areas list_subareas childrenOf
Place details by ID or slug get_venue node / bySlugId
Details for up to 50 places at once get_venues Several node fields in one query, using aliases
Global inventory count Not available in MCP nodeCount

Recommendation: Start with MCP for agent-driven exploration; use GraphQL directly if your backend needs field-level selection, specialized queries or global counts. For production distribution, confirm GraphQL licensing and separate operational policy.

Full GraphQL specification: Source-derived SDL · Argument catalog · Node field catalog · End-to-end recipes.