MPPtempoquality 0.62

Snap GPS traces to road networks via Mapbox Map Matching, paid per-call over MPP/Tempo.

Price
$0.005 / call
Protocol
mpp
Verified
no

What it does

This endpoint provides access to Mapbox's Map Matching API through the Locus MPP (Micropayment Protocol) gateway. Map matching takes noisy GPS traces (2–100 coordinate pairs) and snaps them to the most likely route on the road network using the Mapbox routing engine. It supports multiple routing profiles including driving, driving-traffic, walking, and cycling.

The API accepts semicolon-separated longitude/latitude coordinate pairs along with optional parameters such as timestamps (Unix epoch per coordinate), per-coordinate search radiuses (0–50 meters), geometry output format (GeoJSON, polyline, polyline6), annotation layers (distance, duration, speed, congestion, maxspeed), turn-by-turn step instructions, and a tidy flag to clean up clustered coordinates before matching. The response includes the matched route geometry and optional metadata.

Payment is handled via the MPP protocol using the Tempo method (pathUSD on Tempo L2). Each call costs 5,000 base units of pathUSD (6 decimals), which equals $0.005 per request. Note that the probe returned 404 on HEAD and GET — this endpoint is POST-only, which is consistent with the OpenAPI spec declaring only a POST method. The endpoint is part of a broader Mapbox suite on Locus MPP that also includes geocoding, directions, isochrone, matrix, static images, and tilequery endpoints.

Capabilities

map-matchinggps-trace-snappingroad-network-alignmentturn-by-turn-stepscongestion-annotationsmulti-profile-routinggeojson-outputpolyline-outputtimestamp-aware-matching

Use cases

  • Snapping raw GPS tracks from vehicle telematics to actual road segments
  • Reconstructing driven routes from sparse or noisy location pings
  • Adding speed, congestion, and distance annotations to recorded trips
  • Cleaning up cycling or walking GPS traces for activity analysis
  • Generating turn-by-turn directions retroactively from recorded coordinates

Fit

Best for

  • Agents needing per-call map matching without managing Mapbox API keys
  • Fleet and logistics applications reconstructing vehicle routes from GPS data
  • Developers wanting pay-as-you-go access to Mapbox routing without subscriptions

Not for

  • Real-time navigation requiring persistent WebSocket connections
  • Bulk batch processing of millions of traces where direct Mapbox enterprise pricing is cheaper
  • Use cases requiring more than 100 coordinates per request

Quick start

curl -X POST https://mapbox.mpp.paywithlocus.com/mapbox/map-matching \
  -H "Content-Type: application/json" \
  -d '{
    "profile": "mapbox/driving",
    "coordinates": "-117.1728,32.7157;-117.1700,32.7140;-117.1680,32.7120",
    "geometries": "geojson",
    "overview": "full"
  }'

Example

Request

{
  "tidy": false,
  "steps": true,
  "profile": "mapbox/driving",
  "overview": "full",
  "geometries": "geojson",
  "coordinates": "-117.1728,32.7157;-117.1700,32.7140;-117.1680,32.7120"
}

Endpoint

Transporthttp
Protocolmpp
CurrencypathUSD

Quality

0.62/ 1.00

Full OpenAPI schema with detailed request parameters and clear pricing from the x-payment-info block. However, the probe returned 404 on HEAD/GET (expected since the endpoint is POST-only), no example response is available, and crawled pages returned no useful documentation. Response schema is undocumented.

Warnings

  • Probe returned 404 on HEAD and GET — endpoint is POST-only; this does not indicate it is down but liveness via POST was not confirmed
  • No response schema documented in the OpenAPI spec
  • No example responses available from crawl or probe
  • Currency address 0x20c000000000000000000000b9537d11c60e8b50 assumed to be pathUSD with 6 decimals based on Tempo L2 convention; if incorrect, the $0.005 price may be wrong

Citations

Provenance

Indexed frommpp_dev
Enriched2026-04-19 17:33:46Z · anthropic/claude-opus-4.6 · v2
First seen2026-04-18
Last seen2026-04-22

Agent access