DaedalMap documentation.
Query the managed data layer via API or MCP, or run your own runtime.
Reference
FAQ
Quick answers to the main questions about the engine, packs, hosted access, contributor workflows, and self-hosting.
Data
Packs
Pack structure, release tiers, and the difference between a durable pack library and a hosted runtime.
Data
Source Map
See which source families are live, where the strongest maintained paths exist, and where the gaps are still visible.
Deployment
How It Works
Technical runtime internals: DuckDB, parquet, catalog loading, MCP routing, and pack execution pipeline.
Deployment
Self-Host
Clone, configure, and run the open runtime. Full control, local performance, private catalogs.
Contributor
Make A Pack
A walkthrough for contributors who want to build a source pack, document it, and release it.
Contributor
Source Data
The source sheet format for packs: maintainer, methodology, update dates, coverage, and caveats.
Agent
loc_id Guide
Learn the shared location key used across packs, why joins stay clean, and why tsunami ocean-region ids look different.
Reference
Research Mode
Explore vs Research, what corpus-bound analysis means, and how saved corpora scope results.
Agent
For Agents
The shortest path for developers and agents: live endpoints, flagship packs, paid-lane flow, and the main MCP quickstart.
Agent
Agent Examples
Copyable free and paid calls built around the live flagship packs and the first successful earthquake flow.
Reference
Roadmap
What is being built, what is stable, and where the product is headed.