Snap GPS coordinates to nearest roads via Google Maps Roads API, paid per-call with pathUSD on Tempo L2.
What it does
This endpoint provides access to the Google Maps Roads API's Snap to Roads functionality through the Tempo MPP (Micropayment Protocol). It takes GPS coordinates and snaps them to the most likely road segments the vehicle traveled along, which is useful for cleaning up noisy GPS traces from devices.
The endpoint is live and responds with a standard MPP 402 payment challenge. Settlement occurs on Tempo L2 (chainId 4217) using pathUSD (6 decimals), with a per-call charge of $0.01 (10000 base units). The fee payer flag is set to true, meaning the gateway covers transaction fees on behalf of the caller.
No dedicated documentation is available at the gateway origin. The underlying API mirrors Google Maps Platform's Roads API snapToRoads endpoint, which accepts a path parameter (a list of latitude/longitude pairs) and an optional interpolate boolean, returning snapped points with place IDs and original indices.
Capabilities
Use cases
- —Cleaning noisy GPS traces from vehicle tracking devices
- —Matching raw GPS coordinates to known road segments for fleet management
- —Reconstructing driven routes from sparse location data
- —Improving location accuracy for ride-sharing or delivery apps
- —Preparing GPS data for distance or travel-time calculations
Fit
Best for
- —Agents needing per-call road-snapping without a Google API key
- —Programmatic GPS trace correction with crypto micropayments
- —Lightweight integration where managing Google Cloud billing is undesirable
Not for
- —High-volume batch processing where a direct Google Maps API key would be cheaper
- —Real-time turn-by-turn navigation requiring the Directions API
- —Non-road GPS correction (hiking trails, waterways, etc.)
Quick start
curl -X GET "https://googlemaps.mpp.tempo.xyz/roads/v1/snapToRoads?path=-35.27801,149.12958|-35.28032,149.12907&interpolate=true" \
-H "Authorization: Payment <tempo-payment-token>"Example
Response
{
"snappedPoints": [
{
"placeId": "ChIJoR7CbpNFbmsRQB9QbW7qABM",
"location": {
"latitude": -35.2780159,
"longitude": 149.1294692
},
"originalIndex": 0
},
{
"placeId": "ChIJiy6YT6RFbmsRkHQWIGG0OBM",
"location": {
"latitude": -35.2803415,
"longitude": 149.1290688
},
"originalIndex": 1
}
]
}Endpoint
Quality
The endpoint is confirmed live via a valid MPP 402 challenge with clear pricing, but no documentation, OpenAPI schema, or usage examples are available from the gateway itself. Capabilities are inferred from the Google Maps Roads API documentation.
Warnings
- —No documentation available at the gateway origin (all pages return 404)
- —No OpenAPI or schema definition provided
- —Response format inferred from Google Maps Roads API docs, not confirmed from this gateway
- —Currency address could not be independently verified as pathUSD; assumed based on Tempo L2 convention
Citations
- —Google Maps Roads API snapToRoads accepts a path of lat/lng pairs and returns snapped pointshttps://developers.google.com/maps/documentation/roads/snap
- —Endpoint returns 402 with MPP challenge, method=tempo, intent=charge, amount=10000https://googlemaps.mpp.tempo.xyz/roads/v1/snapToRoads