DaedalMap - Complex data, made navigable.

# DaedalMap > If you are an agent, crawler, or developer bot, start with the agent lane, not the consumer app. DaedalMap exposes a live remote MCP server, a bot-facing discovery layer, and a paid dataset-query lane. For agents and crawlers, start with the MCP server, `server.json`, or the agent docs instead of the human app. ## MCP first - Remote MCP server: [https://app.daedalmap.com/mcp](https://app.daedalmap.com/mcp) - MCP server metadata: [https://app.daedalmap.com/mcp/server.json](https://app.daedalmap.com/mcp/server.json) - Registry identity: `com.daedalmap/county-map` - Short description: remote MCP server for earthquake, tsunami, volcano, disaster, and FX data queries - Current MCP transport: streamable HTTP - MCP note: the MCP server and HTTP API share the same live discovery and execution lane ## Start here for bots - [For Agents](https://daedalmap.com/docs/for-agents): shortest path to the live API lane, MCP endpoint, flagship packs, and first-call flow - [Agent Examples](https://daedalmap.com/docs/agent-examples): copyable free and paid examples for `currency`, `earthquakes`, `volcanoes`, and `tsunamis` - [loc_id Guide](https://daedalmap.com/docs/loc-id): how geography ids, hierarchy, and ocean-region ids work - [llms-full.txt](https://daedalmap.com/llms-full.txt): expanded machine-oriented map of the live hosted bot surface ## Live machine-facing endpoints - [GET /mcp/server.json](https://app.daedalmap.com/mcp/server.json): published MCP server metadata - [GET /mcp](https://app.daedalmap.com/mcp): MCP endpoint discovery - [POST /mcp](https://app.daedalmap.com/mcp): MCP tools/list and tools/call - [GET /api/v1/guide](https://app.daedalmap.com/api/v1/guide): free overview of the hosted API contract - [GET /api/v1/catalog](https://app.daedalmap.com/api/v1/catalog): free list of currently published hosted packs - [GET /api/v1/packs/{pack_id}](https://app.daedalmap.com/api/v1/packs/earthquakes): free pack detail and first-call hints - [POST /api/v1/q