# DaedalMap

> Agents and crawlers: start with the MCP endpoint and agent reference below.

DaedalMap exposes geographic reference and geometry tools, maintained data packs, a live remote MCP server, and a hosted HTTP API.
This file routes agents to the live interface, human setup guide, and copyable requests.

## Start here

- Agent interface: [https://www.daedalmap.com/agents](https://www.daedalmap.com/agents) - endpoint, tool entry points, and first call
- Developer guide: [https://www.daedalmap.com/devs](https://www.daedalmap.com/devs) - client setup and access
- Agent examples: [https://www.daedalmap.com/docs/agent-examples](https://www.daedalmap.com/docs/agent-examples) - copyable MCP and HTTP requests
- Umbrella MCP endpoint: [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)
- HTTP discovery: [https://app.daedalmap.com/api/v1/guide](https://app.daedalmap.com/api/v1/guide), [https://app.daedalmap.com/api/v1/catalog](https://app.daedalmap.com/api/v1/catalog), [https://app.daedalmap.com/api/v1/packs/earthquakes](https://app.daedalmap.com/api/v1/packs/earthquakes)
- Catalogs: [data](https://app.daedalmap.com/api/v1/catalog/download), [geometry](https://app.daedalmap.com/api/v1/geometry/catalog/download)
- Expanded machine guide: [https://www.daedalmap.com/llms-full.txt](https://www.daedalmap.com/llms-full.txt)

## Product surface

DaedalMap is geographic interoperability infrastructure: durable loc_id identities, reusable geometry, published crosswalks, and maintained data over one reference graph. Maps, Research, Ops, downloads, and agent tools are access surfaces over that foundation.

- [https://www.daedalmap.com/](https://www.daedalmap.com/) - project overview and conversion entrance
- [https://www.daedalmap.com/geometry](https://www.daedalmap.com/geometry) - published country geometry, families, representations, sources, and QA
- [https://www.daedalmap.com/explore](https://www.daedalmap.com/explore) - Mapping overview and local program download
- [https://www.daedalmap.com/research](https://www.daedalmap.com/research) - Research MCP, source-backed examples, and local program download
- [https://www.daedalmap.com/ops](https://www.daedalmap.com/ops) - hosted live watch over focused feeds
- [https://www.daedalmap.com/feeds](https://www.daedalmap.com/feeds) - hosted live-feed status surface under Ops
- [https://www.daedalmap.com/agents](https://www.daedalmap.com/agents) - machine-facing agent interface reference
- [https://www.daedalmap.com/devs](https://www.daedalmap.com/devs) - human MCP and HTTP setup guide
- [https://www.daedalmap.com/docs/agent-examples](https://www.daedalmap.com/docs/agent-examples) - copyable requests
- [https://www.daedalmap.com/tools](https://www.daedalmap.com/tools) - local program library and Launcher download
- [https://www.daedalmap.com/packs](https://www.daedalmap.com/packs) - public pack catalog
- [https://www.daedalmap.com/downloadable/](https://www.daedalmap.com/downloadable/) - downloads: programs, data packs, and geometry packages
- [https://www.daedalmap.com/about](https://www.daedalmap.com/about) - founder, mission, open-engine framing
- [https://github.com/xyver/daedal-map](https://github.com/xyver/daedal-map) - open engine source (self-host path)

## Recommended hierarchy

- Developers configuring clients start at `/devs`
- Agents reading HTML start at `/agents`
- Bots and crawlers start at `/llms.txt`
- MCP-capable clients should use `/mcp`
- Direct HTTP clients should use `/api/v1/guide`, `/api/v1/catalog`, `/api/v1/packs/{pack_id}`, and `/api/v1/query/dataset`
- Pack-specific MCP facades are listed in the expanded guide

## Live endpoints

- [GET /mcp/server.json](https://app.daedalmap.com/mcp/server.json)
- [GET /mcp](https://app.daedalmap.com/mcp)
- [POST /mcp](https://app.daedalmap.com/mcp)
- [GET /api/v1/guide](https://app.daedalmap.com/api/v1/guide)
- [GET /api/v1/catalog](https://app.daedalmap.com/api/v1/catalog)
- [GET /api/v1/packs/{pack_id}](https://app.daedalmap.com/api/v1/packs/earthquakes)
- [POST /api/v1/query/dataset](https://app.daedalmap.com/api/v1/query/dataset)

## Coverage

- Data: 18 maintained data packs across natural hazards, hazard risk, economic, business, and development indicators, population, and climate. Call GET https://app.daedalmap.com/api/v1/catalog for the live pack index and each pack's access lane.
- Geometry: global baseline plus 8+ deeper countries. Call `get_catalog(catalog='geometry')` or GET https://app.daedalmap.com/api/v1/geometry/catalog for current country and family coverage.
- Downloads: [https://www.daedalmap.com/downloadable/](https://www.daedalmap.com/downloadable/) - programs, data packs, and geometry packages

## Registry facades

- [cejst](https://app.daedalmap.com/mcp/cejst)
- [earthquakes](https://app.daedalmap.com/mcp/earthquakes)
- [era5_land_temperature](https://app.daedalmap.com/mcp/era5_land_temperature)
- [floods](https://app.daedalmap.com/mcp/floods)
- [hurricanes](https://app.daedalmap.com/mcp/hurricanes)
- [nws_alerts](https://app.daedalmap.com/mcp/nws_alerts)
- [tornadoes](https://app.daedalmap.com/mcp/tornadoes)
- [tsunamis](https://app.daedalmap.com/mcp/tsunamis)
- [un_sdg](https://app.daedalmap.com/mcp/un_sdg)
- [un_wpp](https://app.daedalmap.com/mcp/un_wpp) - registry-published under the searchable name `world-population-prospects`
- [usa_cbp](https://app.daedalmap.com/mcp/usa_cbp)
- [usa_lodes](https://app.daedalmap.com/mcp/usa_lodes)
- [usa_opportunity_zones](https://app.daedalmap.com/mcp/usa_opportunity_zones)
- [usa_susb](https://app.daedalmap.com/mcp/usa_susb)
- [volcanoes](https://app.daedalmap.com/mcp/volcanoes)
- [wildfires](https://app.daedalmap.com/mcp/wildfires)
- [world_bank_wdi](https://app.daedalmap.com/mcp/world_bank_wdi) - registry-published under the searchable name `world-development-indicators`
- [world_factbook](https://app.daedalmap.com/mcp/world_factbook)

## Geography utility tools (free per-call allowance)

A geographic reference and geometry family, free within each tool's per-call allowance: resolve coordinates and codes, inspect loc_id identities and relationships, discover country and family coverage, retrieve boundaries, and follow published crosswalks. The administrative spine is the main join surface; other geography families retain distinct identities.

- `geography` utility family (free per-call allowance) - Geography utilities built on the DaedalMap loc_id spine. Identify dataset geography, recognize and convert external references, resolve shallow or deep coordinate batches, inspect loc_ids, compare places, and retrieve bounded shapes. Future estimate/create/status workflows remain private until durable job delivery is ready.
  - facade: `https://app.daedalmap.com/mcp/geography` (registry name `com.daedalmap/geography`)
  - tools: `get_tool_help`, `get_catalog`, `get_pack`, `get_geography`, `identify_dataset_geography`, `identify_reference_system`, `convert_reference`, `compare_geographies`, `get_shape`, `resolve_point`, `resolve_deep_point`, `get_loc_id_info`
  - also reachable on the umbrella `https://app.daedalmap.com/mcp`; free within each tool's per-call allowance, account credit above it

### Choose the tool by question

1. Point to loc_id: call `resolve_point` with one coordinate or a bounded array; it stops at Admin 3. For Admin 4-6, group results by shallow scope and call `resolve_deep_point` with one coordinate or array plus one `shallow_loc_id` per call.
2. What a loc_id is directly connected to in the selected reference graph: call `get_loc_id_info`; results are capped per ID and say when more connections exist.
3. Dataset to loc_id: pass bounded named columns to `identify_dataset_geography`; it selects only a recognized code column or coordinate pair. If a code column was selected, declare one country_scope and call `identify_reference_system` on its bounded values to determine the system. Resolve a known outside code or name with `convert_reference` and omit `to_system`; provide `to_system` only when another reference system is the desired output.
4. Shape lookup: call `get_shape` with an exact loc_id and default `include_polygon=false` for availability, metadata, bbox, and centroid; set `include_polygon=true` only when shape coordinates are needed. If the requested record is historical, return it first; present any `supersession` prompt as a second question and do not fetch the successor until the caller chooses it.
5. Coverage discovery: call `get_catalog(catalog='geometry')`, then `get_geography(scope_id='<ISO3>')` for a scope's families or `get_geography(family_id='<family>')` for its scopes. Known vintage years do not prove effective coverage.
6. Relationship between two loc_ids: call `compare_geographies`. Obtain descendant loc_ids through the explicit scope resolver before requesting their shapes.
7. Batch rule: use a bounded batch where supported; split deep work by Admin1 owner.
8. If the right path is unclear: call `get_tool_help` with a topic, then with one exact visible tool name. Future estimate/create/status builder contracts are retained internally but are not part of the public MCP roster.

## Data tools

- `get_data` - Retrieve rows from one selected published data pack using exact metrics, loc_id-based region filters, time/metric filters, sorting, and a row limit. Disaster event rows include stable event_id values for get_event drill-down. A parent administrative loc_id selects matching descendant rows at the pack's published grain. Call get_pack first; geometry families use their focused next-step tools.
- `get_event` - Retrieve one exact disaster event and explicitly requested relationships, affected places, native observations, or geometry. Use get_data to obtain the stable event_id first.
- Access is set per pack: `get_catalog` and `get_pack` report whether a pack is free or paid before you query it.

## Current live contract

- MCP discovery first is valid: read `server.json`, then call `tools/list`, then follow `get_catalog` -> `get_pack` -> `get_data`
- Free discovery first: `guide`, `catalog`, and pack detail
- `request_id` is optional but recommended for tracing and idempotency
- Paid execution second: an unpaid request to `POST /api/v1/query/dataset` returns `402` with the exact price before any charge
- MCP is a wrapper over the same underlying hosted discovery and paid execution lanes
- Paid MCP calls on `/mcp` return `payment_choice_required`; pay with account credit on `/mcp/account` (`X-API-Key`)

## Related docs

- [For AI agents](https://www.daedalmap.com/agents)
- [Developer guide](https://www.daedalmap.com/devs)
- [Agent Examples](https://www.daedalmap.com/docs/agent-examples)
- [loc_id Guide](https://www.daedalmap.com/loc_id)
- [Geometry Family Definitions](https://www.daedalmap.com/docs/geometry-families)
- [Geometry Tools](https://www.daedalmap.com/docs/geometry-tools)
- [GitHub (open runtime)](https://github.com/xyver/daedal-map)