A coordinate goes in. A place comes out.
One call resolves any location to the country and region that contain it, plus matches from your own custom boundary sets. Delivery zones, service areas, territories. Start free, no card required.
a route costs
10lookups
From the same allowance. Pro's $29 a month covers 25,000 routes, or any mix with lookups.
a lookup costs
1lookup
Country, region, municipality, the street layer and every one of your own sets — all in the same call.
extra systems to maintain
0
The zones you already draw are the avoid rules. Same key, same bill, nothing to keep in step.
What AtlasFetch does
01
Location data
A coordinate in, and the country, region and municipality that contain it out, each with a name and a code, plus the nearest street and house number.
- Every country and over 3,000 regions, worldwide
- New: the nearest street and house number, worldwide
02
Directions
Road routes between your points that go around the zones you name, and say how far they ran inside the ones you measure.
- Your existing sets become avoid rules — nothing new to maintain
- Turn-by-turn steps, alternatives and stops in one call
03
Custom boundaries
Your own delivery zones, service areas and territories, with your properties attached, matched in the same call as the place names.
- Draw in the browser or upload in seconds
- Share each set with only the keys you choose
Compared with Mapbox and Google Routes
Routes that know your zones. A bill with a ceiling.
Built for routes that have to respect zones you maintain, beside the boundary lookups you already make. The delivery zones you drew this morning are the avoid rules this afternoon, on the key you already have.
only here
Routes around polygons you drew
Name a set and the route goes around every zone in it, whatever shape you drew.
- AtlasFetchAny set your key can read
- MapboxPoints only
- Google RoutesTolls, highways, ferries
only here
Distance driven inside your zones
Name a set to measure and the answer lists each zone the route entered, the metres inside, and the zone's own properties.
- AtlasFetchPer zone, with its properties
- MapboxNot offered
- Google RoutesNot offered
the most Pro costs in a month
$29
Flat, for 25,000 routes or any mix with lookups.
when the allowance is gone
402
A refusal, not an invoice. Nothing is billed on top.
surprise bills
0
Mapbox and Google bill each request past their free tier.
The whole picture: free tiers, prices and limits
| Compared on | AtlasFetch | Mapbox | Google Routes |
|---|---|---|---|
| Routes around polygons you drew | Yes, any set your key can read | Points only | No |
| Distance driven inside your zones | Yes, in metres per zone | No | No |
| Free each month | 100 routes (1,000 lookups) | 100,000 requests | 10,000 requests |
| After that | $9 for 5,000 or $29 for 25,000, flat | $2.00 per 1,000, less at volume | $5.00 per 1,000, down to $0.38 at volume |
| Past your limit | A 402, never a bill | Billed per request | Billed per request |
Competitor figures are the published list prices of Mapbox Directions and Google Routes (Compute Routes Essentials), checked October 2026, and are the only figures on this page we did not measure ourselves. Check them before you rely on them, as we do.
Base layers
Every point resolves to a clean hierarchy
Country, region and municipality. Each one comes back as a clear name and a code — official ISO codes where they exist. Never a raw geometry dump, never an internal id.
countries
every
No regional gaps and no per-country pricing.
regions
3,000+
States, provinces, counties, with ISO codes where they exist.
layers per call
1lookup
Ask for one or ask for all of them. The price does not move.
map data
2026-08-27
One dated OpenStreetMap snapshot behind boundaries, streets and routes.
GET /location/lookup?lat=51.5072&lng=-0.1276&set=delivery_zones
{
"base": {
"country": { "code": "GB", "name": "United Kingdom" },
"region": { "code": "GB-ENG", "name": "England" },
"municipal": { "code": "GB-WSM", "name": "City of Westminster" }
},
"sets": {
"delivery_zones": [
{ "name": "Zone A", "properties": { "category": "express" } }
]
},
"errors": []
}- Standard names and codes, like GB and GB-ENG
- Every country and over 3,000 regions, worldwide
- Ask for just the layers you need on each call
- New: the nearest street and house number, worldwide
Custom boundaries
Your boundaries, same lookup
Draw delivery zones, service areas, or sales territories in the built-in editor, or upload your own. Attach properties, group them into sets, share each set with exactly the keys you choose, and check them in the very same call as the country and region layers.
- Draw in the browser or upload in seconds
- Share each set with only the keys you choose
- Your own properties come back with every match
- One lookup per call, however many sets you check
what you get on each plan
- Boundary sets
- 1
- 5
- 25
- Boundaries per set
- 10
- 1,000
- 10,000
- Points per boundary
- 50
- 50
- 50
- Properties per boundary
- 5
- 10
- 25
1Draw your zones
In the editor, or upload GeoJSON. Each zone carries properties you choose.
2Group them, share the set
Your zones go into a set, granted to exactly the keys that may read it.
3Every lookup checks them
A point inside a zone returns it, with its properties, in the same call as the place names.
Directions
Now it routes around them too
Ask for the road line between two points and name the sets you want kept clear. The route goes around every zone in them, and the response tells you which ones it applied and which it could not. Car, bike, foot and truck.
- shortest
- 3.0 km
- around your zone
- 3.6 km
- the zone cost you
- +568 m
shortest line
3.0km
4 min 54 s
around your zone
3.6km
8 min 18 s
the zone cost you
+568m
And 3 min 24 s. Worth knowing before a driver does.
a route costs
10lookups
Stops, steps, alternatives and zones all included.
A real recorded response, Vaduz to Schaan, with one zone from a no_go set applied.
- Your existing sets become avoid rules — nothing new to maintain
- Or name a set to measure, and get the metres you travelled inside it
- Turn-by-turn steps, alternatives and stops in one call
- Worldwide, from the same key and the same allowance
Use it inside Claude Code
Ask Claude where a point is. It calls AtlasFetch instead of guessing.
The AtlasFetch MCP server gives Claude Code the lookup and the route as tools. Ask which municipality a coordinate is in and the answer comes from a real point-in-polygon lookup, with ISO codes — not from the model's memory. Ask for a route around your zones and it calls the routing engine.
claude mcp add atlasfetch -- npx -y atlasfetch-mcpWithout a key it uses the shared demo key, 1,000 lookups a month across everyone. Add your own with -e ATLASFETCH_API_KEY.
- lookup_location
- Country, region, municipality, nearest street, and your own sets.
- get_route
- Car, bike or foot (truck on Pro), with turn-by-turn steps, around your zones or measured against them. 10 lookups a route.
- list_boundary_sets
- Your sets, their counts, and which keys may read them.
- create_boundary_set
- A new, empty set for your own polygons.
- add_boundary
- One GeoJSON polygon, with properties returned on every match.
Works the same in Claude Desktop, Cursor and VS Code. Needs Node 20 or newer.
What it is not
The list we would rather you read now
Every one of these is worth knowing before you build on it, so it is here rather than in a support thread six weeks in.
- Live traffic
- None. Durations are free-flow, from the road graph.
- Geocoding
- None. Coordinates in, coordinates out.
- Road and boundary data
- A dated OpenStreetMap snapshot, not a live feed. Its date is published at /route/coverage.
- Overage billing
- None. You get a 402 when the allowance is gone, never an invoice you did not expect.
- Volume discounts
- None. A route is ten lookups on every plan; to send more, you move up a plan.
Plans for every scale
A lookup costs one, however many layers and sets it touches. A route costs ten. Start free, upgrade when you scale.
GET /location/lookup
1lookup
Every layer, all of your sets, the street layer
POST /route
10lookups
Stops, steps, alternatives, avoid zones and exposure
refused requests
0lookups
A 400, 401, 403 or 429 is free.
when the allowance runs out
402
A hard stop, not a bigger bill. Custom exists for businesses that need more.
Public
$0
The shared community key — zero signup
- Shared community API key
- 1,000 lookups / month (shared)
- 2 requests / second
- 1 shared boundary set
Personal
$0
Your own account, keys and private sets
- Your own API keys
- 1,000 lookups / month
- 5 requests / second
- 1 private boundary set
Basic
$9/mo
For apps in production
- Everything in Personal
- 50,000 lookups / month
- 10 requests / second
- 5 boundary sets
Pro
$29/mo
High volume, big territories
- Everything in Basic
- 250,000 lookups / month
- 25 requests / second
- 25 boundary sets
Custom
Talk to us
Fleets and businesses past Pro
- Allowance sized to you
- Agreed rate limit
- Truck routing included
- Monthly or annual
Contact form coming soon.
A lookup is one lookup, however much you ask of it. A route is ten.
See it for yourself →live