A phone’s GPS fixes wander off the street by metres. Send the trace and get back the roads it was actually on, as a clean line with a real distance and a real duration. One unit, up to a hundred fixes.
10,000 units free every month. No credit card, no sales call.
POST /map-matching/v1 · 37 points · costing: bicycleraw · 37 fixes, ±8 m
Nobody ships an endpoint. They ship a ride log whose distance a cyclist believes, a fleet map where the van is on the street and not in the canal, a mileage claim that holds up. This is what a matched trace looks like from the outside.
Centraal to the Vondelpark by bike, 37 fixes off by ±15 m
Thirty-seven fixes from one bike ride, each off by metres the way a phone in a coat pocket is. The matched line runs down the streets the rider actually took, and its length is the distance actually ridden.
The same road graph, routedThe same ride recorded at three noise levels comes back within a few dozen metres of the same length every time. Summing raw fixes would have given three different, longer answers.
Then navigate itA ride being recorded, one fix every few seconds
0 of 100 fixes
still 1 unit
A match costs one unit however many points it carries, up to a hundred per request. Longer traces go as an encoded polyline, or in chunks.
See what a month costsconst { trip } = await rijwind.mapMatching({ shape: fixes, // [{ lat, lon }, …] from the phone costing: 'bicycle', }); saveRide({ km: trip.summary.length, line: trip.legs[0].shape });
Same envelope as directions: a summary with the real distance and time, and a leg with the matched geometry and the streets it took. The code that draws a route draws a matched ride.
Read the quickstartThe response is the route the device took: the snapped start and end, a summary with the distance actually travelled, and a leg with the matched line and the streets along it. Nothing new to parse if you already draw routes.
Everything a developer scans a product page for, in one place, without the adjectives.
Numbers as of September 2026. The pricing page has the full ladder.
Taking a sequence of GPS positions, which are always a few metres off, and working out which roads the device was actually travelling on. The result is a line that follows the streets, with the distance and time of that line rather than of the jittery fixes.
Ride and run logs that show the real route and the real distance, fleet and delivery apps that need to know which streets a vehicle used, mileage claims, and any analysis that starts with 'which road was this on'. The matched line also draws cleanly, where raw fixes zigzag.
One unit per request, from the same monthly pool as maps, geocoding and routing, whatever the number of fixes up to the cap.
Up to a hundred fixes as a list of coordinates. Longer traces can be sent as a single encoded polyline instead, or split into chunks that are matched one after the other.
The three traces on this page were jittered by 4, 8 and 15 metres and all matched to within a few dozen metres of the true length. Much larger errors, long gaps or a device that stopped for a while can still be matched, but the further the fixes are from any road the more the matcher has to guess.
Car, bicycle and pedestrian. The profile tells the matcher which roads the device could have been on, so a bike trace is not snapped onto a motorway.
No. It takes positions in order and matches on geometry alone, which is enough for the route and the distance. If you need per-fix speeds, compute them from your own timestamps against the matched line.
The same envelope as a route: a summary with the matched distance and time, a leg with the matched geometry as an encoded polyline and the manoeuvres along it, and the snapped start and end. The code that handles a route handles this.
Yes. The free plan includes 10,000 units a month with no card and no sales call, which is 10,000 matched traces if that is all you spend them on. It is a hard cap, so a runaway loop cannot produce a bill.
In the European Union, end to end. No part of the request path touches a US-controlled provider, which is what makes the GDPR and data-residency conversation short. We publish a DPA and a full sub-processor list.
Turn-by-turn on the same road graph the trace is matched to.
The best order for your stops, solved for you.
Every source to every target in one request.
The matched ride with its climb profile.
One unit pool, one table, a cap you set.
What actually differs, feature by feature.
Ten thousand units a month, free. The same key covers maps, search and routing when you get to them.