What is EDK?
EDK is programmable infrastructure for the physical world.
Documentation navigation
Geography as a software primitive
EDK gives developers and AI systems a common way to search, locate, understand, measure, route across, compute over, and render geography. The physical world becomes structured output that an application can continue to use—not only a map marker.
A place, road, permit, incident, or visual detection can be searched, filtered, compared, measured, mapped, routed to, or passed into the next operation. That is programmable geography.
From a geographic question to structured output
| Question | What EDK provides |
|---|---|
| What exists in this area? | Searchable geographic features and records. |
| What is nearby, inside, or along a route? | Spatial relationships, geometry, and measurements. |
| What is reachable within 20 minutes? | Routes, travel times, matrices, and reachable areas. |
| What evidence supports this result? | Source context and observation provenance where available. |
| How can an agent use this reliably? | Deterministic MCP tools that return actual geography. |
One connected geographic layer
EDK operations compose. A search result can become a map layer. A place can become a routing destination. A route can define a corridor for another search. A Region can scope a dataset, and a set of features can be measured with Compute. The output of one operation remains useful to the next.
Cloud, local, or both
Use EDK Cloud for managed APIs, Compute, storage, routing, and search. Use supported local workflows when you need offline operation, privacy, portability, or direct control of local data. Applications can combine both according to their needs.
EDK and EDK
EDK is the platform described throughout these docs. EDK remains the technical name used by existing interfaces such as the JavaScript client, the e2 CLI, and e2_* MCP tools.