Get travel time and distance between origin-destination pairs via Google Maps Distance Matrix API, paid per call with pathUSD on Tempo.
What it does
This MPP (Micropayment Protocol) endpoint wraps the Google Maps Distance Matrix API, returning travel time and distance calculations for one or more origin-destination pairs. It is hosted on Tempo's payment gateway at googlemaps.mpp.tempo.xyz and settles payments in pathUSD on the Tempo L2 chain (chainId 4217).
Each API call costs 5,000 base units of pathUSD. Assuming pathUSD uses 6 decimals (consistent with other USD stablecoins), this translates to $0.005 (half a cent) per request. The endpoint accepts GET requests and mirrors the Google Maps Distance Matrix JSON interface — callers pass query parameters such as `origins`, `destinations`, and `mode` (driving, walking, bicycling, transit) and receive a JSON response with rows of distance/duration elements. The provider pays transaction fees on behalf of the caller (feePayer: true).
No OpenAPI schema, dedicated documentation, or example responses were found on the provider's domain. The endpoint is confirmed live via a valid 402 Payment Required challenge with a Tempo-method WWW-Authenticate header. Because the upstream API is the well-documented Google Maps Distance Matrix API, callers familiar with that API can construct requests accordingly, but the exact parameter pass-through behavior and any provider-specific limitations are not documented.
Capabilities
Use cases
- —Calculate driving, walking, or transit time between multiple origins and destinations for logistics planning
- —Estimate delivery ETAs in real time for ride-sharing or food-delivery apps
- —Compare travel distances across transport modes for trip-planning agents
- —Power cost or time optimization in multi-stop route planning workflows
Fit
Best for
- —AI agents needing per-call geo distance lookups without managing Google API keys
- —Micropayment-native applications that want to pay per request in crypto
- —Developers who want Google Maps Distance Matrix results settled via Tempo L2
Not for
- —High-volume batch geocoding or places search (this endpoint is distance-matrix only)
- —Users who need detailed turn-by-turn navigation or rendered map tiles
- —Applications requiring fiat billing or traditional API-key authentication
Quick start
curl -H "Authorization: Payment <tempo_payment_token>" \
"https://googlemaps.mpp.tempo.xyz/maps/distancematrix/json?origins=New+York,NY&destinations=Boston,MA&mode=driving"Example
Response
{
"rows": [
{
"elements": [
{
"status": "OK",
"distance": {
"text": "215 mi",
"value": 346007
},
"duration": {
"text": "3 hours 40 mins",
"value": 13200
}
}
]
}
],
"status": "OK",
"origin_addresses": [
"New York, NY, USA"
],
"destination_addresses": [
"Boston, MA, USA"
]
}Endpoint
Quality
The endpoint is confirmed live with a valid MPP 402 challenge and clear pricing. However, no OpenAPI schema, documentation, or example responses are available from the provider. The response format is inferred from the well-known Google Maps Distance Matrix API, not from provider-supplied docs.
Warnings
- —No documentation or OpenAPI schema found on the provider domain — all crawled pages return 404.
- —Response format and supported query parameters are inferred from the upstream Google Maps Distance Matrix API and are not confirmed by the provider.
- —The currency address 0x20c000000000000000000000b9537d11c60e8b50 is assumed to be pathUSD with 6 decimals; if decimals differ, the per-call price would change.
Citations
- —Endpoint returns HTTP 402 with a Tempo-method MPP challenge, confirming it is live.https://googlemaps.mpp.tempo.xyz/maps/distancematrix/json
- —Per-call amount is 5000 base units on chainId 4217 (Tempo L2) with feePayer true.https://googlemaps.mpp.tempo.xyz/maps/distancematrix/json
- —Description states: Travel time and distance for origin-destination pairs.https://googlemaps.mpp.tempo.xyz/maps/distancematrix/json