Find the nearest roads to GPS coordinates via Google Maps Roads API, paid per call with pathUSD on Tempo.
What it does
This MPP (Micropayment Protocol) endpoint proxies the Google Maps Roads API's "nearest roads" feature through Tempo's payment layer. Given a set of GPS coordinates, it returns the nearest road segments, which is useful for snapping raw GPS traces to known roads, identifying which road a vehicle is traveling on, or enriching location data with road metadata.
The endpoint is live and responds with a standard MPP 402 Payment Required challenge. Settlement uses the Tempo method on chain ID 4217 with a per-call charge of 10,000 base units of pathUSD (a 6-decimal stablecoin), which equals $0.01 per request. The provider covers gas fees (feePayer: true), so callers only pay the stated amount. The upstream Google Maps Roads API typically accepts query parameters like `points` (a pipe-delimited list of latitude/longitude pairs) and returns snapped points with placeId references.
Documentation on the proxy itself is not available — the provider's root, /docs, /api, /pricing, and /README pages all return 404. Callers should refer to the official Google Maps Roads API documentation for parameter formats and response schemas, keeping in mind that this proxy may not support every parameter or feature of the upstream API.
Capabilities
Use cases
- —Snapping raw GPS traces from vehicle telematics to the nearest known road segments
- —Identifying which road a moving device is on for fleet tracking or ride-sharing applications
- —Enriching location datasets with road-level metadata for analytics or mapping pipelines
- —Building navigation or routing features that need to resolve noisy GPS points to roads
Fit
Best for
- —Agents or services that need per-call road-snapping without a Google Maps API key
- —Crypto-native applications that want to pay for geo services with stablecoins
- —Low-volume or sporadic nearest-road lookups at $0.01 per call
Not for
- —High-volume batch road snapping where a direct Google Maps API key would be cheaper
- —Use cases requiring the full Roads API feature set (e.g., speed limits) — proxy coverage is unverified
- —Applications that cannot settle payments on Tempo / chain 4217
Quick start
curl -H "Authorization: Payment <tempo-payment-token>" \
"https://googlemaps.mpp.tempo.xyz/roads/v1/nearestRoads?points=60.170880,24.942795|60.170879,24.942796"Endpoint
Quality
The endpoint is live and returns a valid MPP 402 challenge with clear pricing, but there is zero documentation from the provider (all doc pages return 404), no OpenAPI schema, and no example request/response. Most details are inferred from the endpoint path, the challenge metadata, and knowledge of the upstream Google Maps Roads API.
Warnings
- —No provider documentation available — root, /docs, /api, /pricing, /README all return 404
- —No OpenAPI or schema definition; request parameters and response format are inferred from upstream Google Maps Roads API
- —Proxy feature coverage is unverified — some upstream Roads API features may not be supported
- —Currency address 0x20c0…8b50 assumed to be pathUSD (6 decimals) on chain 4217; if decimals differ, the stated price ($0.01) would be incorrect
Citations
- —Endpoint is live and returns HTTP 402 with MPP challenge (method=tempo, intent=charge)https://googlemaps.mpp.tempo.xyz/roads/v1/nearestRoads
- —Per-call amount is 10000 base units on chain 4217 with feePayer=truehttps://googlemaps.mpp.tempo.xyz/roads/v1/nearestRoads
- —Challenge expires 2026-04-19T17:12:57.223Zhttps://googlemaps.mpp.tempo.xyz/roads/v1/nearestRoads