# EDK > EDK-1 is a spatial model that gives humans and machines a compass for the world: position, condition, motion, navigation and stream. Find places, understand any spot, route between them and watch for change, through one API. - [Model](https://edk.earth/model): position, condition, motion, navigation and stream, the five primitives EDK-1 is built on - [Docs](https://edk.earth/docs): Discover, Inspect, Route, Compute Units, tiers, embeds, SDK, CLI and MCP - [Agent setup](https://edk.earth/agents.md): a prompt that connects an agent to EDK-1. Add ?for=claude-code, codex, cursor, gemini, claude or chatgpt for one platform - [Atlas](https://edk.earth/atlas): EDK-1 on a map, for signed-in accounts - [API](https://api.edk.earth/v1): base URL; authenticate with Authorization: Bearer edk_sk_… ## Discover, Inspect, Route or Monitor EDK-1 has four calls. Pick by what you already have and what you need back. **Discover** when you have a question and need places. It finds things; you get a list back. - "bridges in Pittsburgh", "solar farms near Phoenix": things you can see on the ground. - "high income areas in Denver", "low flood risk with tree canopy in Austin": areas that meet conditions. - Returns locations and areas with coordinates, imagery and an embed_url that opens them on the Atlas. - Name the city or region in the query. Set limit to what you will actually use (CU scales with results). Add answer: true only when the user wants a written summary. **Inspect** when you have a point and need to know about it. It describes one spot; you get facts back. - "what is at 40.4406, -79.9959", "is this address in a flood zone", "who lives around here". - Returns the place names, highlights (income, people nearby, elevation, flood risk, tree canopy, air quality) and every known fact by category. - It takes coordinates, not names. If you only have a name or address, Discover it first and Inspect the coordinates that come back. **Route** when you have a start and an end and need the way between them. - "drive from Point State Park to Carnegie Mellon avoiding pothole streets", "walking route from A to B". - from and to take a place name, an address, or coordinates. include is plain words for what to pass on the way ("a coffee shop"); conditions is plain words for what to stay clear of ("pothole streets"). EDK-1 finds those places along the way and routes through or around them. - Returns distance, duration, the path as GeoJSON, turn-by-turn steps, what it passes and avoided, and the direct route for comparison. - Conditions steer driving routes only. Read note and remaining in the response and tell the user when something could not be avoided. **Monitor** when the user wants to know about new events as they happen, not once. - "tell me when a building permit is filed in Pittsburgh", "watch for new potholes downtown every hour". - POST /v1/monitors with artifacts (names or ids from GET /v1/artifacts), an area (a place name or "lat, lng"), since (a date), interval ("15m", "1h", "6h", "1d") and a webhook_url. Events also appear in the console. - Each new event is 0.2 CU. Monitor is available from Tier 4; a 403 means the account is below it, so say so. Together: Discover to find candidates, Inspect the one or two that matter, Route to the one chosen. Don't Inspect every Discover result, and don't use Discover to describe a single known point. None of the calls returns live traffic or transit timetables. Say so instead of guessing. ## If you are a chat assistant without a terminal Do not install the CLI, SDK or MCP server and do not ask for an API key. Send the user an Atlas link instead: https://edk.earth/atlas?q=