Distances, without the per-call bill.
A wire-compatible distance-matrix API on the edge. Distances within ~1% of the panel median on most route categories (up to ~5% off on toll-routed and dense urban); durations are free-flow — no live traffic (see how we measure). $0 per call, no key, no analytics. Type an origin and a destination, or copy the curl.
One honest job, done cheaply.
It returns a number, not a map. Knowing exactly what you trade is the whole pitch.
✓ What you get
The useful 90%, for free.
- ✓Driving distance + duration between any two US points
Addresses or raw lat,lng — lower 48 + DC, including cross-country. - ✓A 25-pair matrix in one call
Up to 25 origin × destination elements. - ✓Wire-compatible JSON response
Same shape as the legacy Distance Matrix API; clients keep parsing. - ✓Self-host the whole thing
Fork it, deploy to your own edge, set your own limits.
✗ What you give up
If you need these, use a routing engine.
- ✗Route geometry / a polyline
No line is drawn — just the scalar numbers. - ✗Turn-by-turn directions
It isn’t a navigation product. - ✗Live / predicted traffic
Numbers come from a static routed graph. - ✗Walking, transit, or non-US
Driving only, continental US only — today.
From nothing to first call in a minute.
One endpoint. No key, no SDK, no signup. Swap your base URL and go. Read the full docs →
Point at the endpoint
GET /maps/api/distancematrix/json — the only route you need.
Single pair, or a matrix
Pipe-separate origins and destinations to score up to 25 elements (N origins × M destinations) in one call. Single pair is just N=M=1.
Read the standard JSON
Same shape you already parse — rows[i].elements[j] = origin i to destination j. Plus additive *_matches confidence fields.
Self-throttle on headers
Every response carries X-RateLimit-Remaining-* so you can back off cleanly.
The questions, sorted by what you’re asking.
No marketing answers. If something’s a bad fit, this page will tell you.