# 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)
- Narrow MCP facades:
  - [currency](https://app.daedalmap.com/mcp/currency)
  - [earthquakes](https://app.daedalmap.com/mcp/earthquakes)
  - [volcanoes](https://app.daedalmap.com/mcp/volcanoes)
  - [tsunamis](https://app.daedalmap.com/mcp/tsunamis)
- 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
- Publishing note: the umbrella MCP remains the canonical live product; narrow facades exist for official-registry discoverability, while Smithery stays pointed at the umbrella server

## Start here for bots

- [For Agents](https://daedalmap.com/docs/for-agents): canonical public listing for the live API lane, MCP endpoint, flagship packs, directory metadata, 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

## Publishing layers

- Ultimate listing: [https://daedalmap.com/docs/for-agents](https://daedalmap.com/docs/for-agents)
- Machine-readable listing: [https://daedalmap.com/llms.txt](https://daedalmap.com/llms.txt) and [https://daedalmap.com/llms-full.txt](https://daedalmap.com/llms-full.txt)
- Umbrella MCP: [https://app.daedalmap.com/mcp](https://app.daedalmap.com/mcp)
- Individual MCP facades: `currency`, `earthquakes`, `volcanoes`, and `tsunamis`
- Directory rule: broad directories and GitHub awesome lists should use one DaedalMap entry that links to the ultimate listing or umbrella MCP, not one entry per individual pack facade

## 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 /mcp/currency/server.json](https://app.daedalmap.com/mcp/currency/server.json): pack-specific currency MCP metadata
- [GET /mcp/currency](https://app.daedalmap.com/mcp/currency): currency MCP discovery
- [POST /mcp/currency](https://app.daedalmap.com/mcp/currency): currency MCP tools/list and tools/call
- [GET /mcp/earthquakes/server.json](https://app.daedalmap.com/mcp/earthquakes/server.json): pack-specific earthquakes MCP metadata
- [GET /mcp/earthquakes](https://app.daedalmap.com/mcp/earthquakes): earthquakes MCP discovery
- [POST /mcp/earthquakes](https://app.daedalmap.com/mcp/earthquakes): earthquakes MCP tools/list and tools/call
- [GET /mcp/volcanoes/server.json](https://app.daedalmap.com/mcp/volcanoes/server.json): pack-specific volcanoes MCP metadata
- [GET /mcp/volcanoes](https://app.daedalmap.com/mcp/volcanoes): volcanoes MCP discovery
- [POST /mcp/volcanoes](https://app.daedalmap.com/mcp/volcanoes): volcanoes MCP tools/list and tools/call
- [GET /mcp/tsunamis/server.json](https://app.daedalmap.com/mcp/tsunamis/server.json): pack-specific tsunamis MCP metadata
- [GET /mcp/tsunamis](https://app.daedalmap.com/mcp/tsunamis): tsunamis MCP discovery
- [POST /mcp/tsunamis](https://app.daedalmap.com/mcp/tsunamis): tsunamis 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/query/dataset](https://app.daedalmap.com/api/v1/query/dataset): paid query lane, challenge-first via HTTP `402`

## Current hosted packs

- `currency`
- `earthquakes`
- `volcanoes`
- `tsunamis`

## Current live contract

- MCP discovery first is valid: read `server.json`, then call `tools/list`, then use a named tool or `query_dataset`
- Free discovery first: `guide`, `catalog`, and pack detail
- Paid execution second: unpaid request to `POST /api/v1/query/dataset` returns `402`, then a payment-aware client retries
- MCP is a wrapper over the same underlying hosted discovery and paid execution lanes
- The current hosted paid rail is Base mainnet USDC via x402 exact payment

## Suggested broad directory entry

DaedalMap Geographic Data - Hosted MCP and agent-ready geographic data for disasters, FX, and location-linked datasets. Includes free currency and volcano lanes, x402-paid earthquake and tsunami lanes, and an always-current pack index at https://daedalmap.com/docs/for-agents.

## Human-facing pages

- [Open App](https://app.daedalmap.com): hosted map interface for people
- [Docs Index](https://daedalmap.com/docs): broader product documentation
- [How It Works](https://daedalmap.com/docs/how-it-works): engine, pack model, and hosted/local split
- [Hosted vs Local](https://daedalmap.com/docs/hosted-vs-local): runtime mode differences

## Related

- [GitHub (open runtime)](https://github.com/xyver/daedal-map): open engine and schema model