Compute driving/transit/walking routes between locations via Google Maps on Tempo MPP.
What it does
This endpoint wraps the Google Maps Routes API (computeRoutes v2) behind the Tempo MPP (Micropayment Protocol), allowing AI agents and applications to request route computations between locations and pay per call using pathUSD on the Tempo L2 network. The underlying Google Maps computeRoutes API accepts origin and destination waypoints (plus optional intermediates) and returns detailed route information including distance, duration, polylines, and step-by-step directions for driving, transit, walking, or cycling modes.
The endpoint is hosted at googlemaps.mpp.tempo.xyz and is part of a broader Google Maps MPP gateway that also exposes geocoding, places, tiles, weather, air quality, and other Google Maps Platform services. However, during probing the endpoint returned 404 on both HEAD and GET requests rather than the expected 402 MPP payment challenge. This may indicate the endpoint expects POST requests (consistent with the Google Maps computeRoutes API which is POST-only), or it may be temporarily unavailable. No documentation, pricing information, or OpenAPI schema was found at the provider's origin.
Because no 402 challenge was captured and all crawled pages returned "Not Found," concrete details about pricing, supported payment methods, and exact request/response schemas cannot be confirmed from the probe data alone. The endpoint path and naming strongly suggest it proxies the standard Google Maps Routes v2 computeRoutes API, but users should verify availability and pricing before relying on it.
Capabilities
Use cases
- —Computing optimal driving routes between two or more locations for logistics or delivery planning
- —Getting transit directions with estimated travel times for trip-planning agents
- —Calculating walking or cycling routes with distance and duration for fitness or mobility apps
- —Generating encoded polylines for map visualization of planned routes
- —Comparing multiple route alternatives by distance and ETA
Fit
Best for
- —AI agents needing pay-per-call route computation without managing Google API keys directly
- —Applications requiring multi-modal route planning (drive, transit, walk, cycle)
- —Developers who want crypto-settled access to Google Maps routing
Not for
- —High-volume batch geocoding (this endpoint is specifically for route computation)
- —Real-time traffic monitoring or live navigation turn-by-turn guidance
- —Use cases requiring free or pre-paid API access without per-call micropayments
Quick start
curl -X POST https://googlemaps.mpp.tempo.xyz/routes/directions/v2:computeRoutes \
-H 'Content-Type: application/json' \
-d '{
"origin": {"location": {"latLng": {"latitude": 37.7749, "longitude": -122.4194}}},
"destination": {"location": {"latLng": {"latitude": 34.0522, "longitude": -118.2437}}},
"travelMode": "DRIVE"
}'Example
Request
{
"origin": {
"location": {
"latLng": {
"latitude": 37.7749,
"longitude": -122.4194
}
}
},
"travelMode": "DRIVE",
"destination": {
"location": {
"latLng": {
"latitude": 34.0522,
"longitude": -118.2437
}
}
},
"routingPreference": "TRAFFIC_AWARE"
}Endpoint
Quality
The endpoint returned 404 on HEAD and GET probes (it likely requires POST but no 402 challenge was captured on any method). All crawled pages returned Not Found, so there is no documentation, pricing, or schema available. The listing is largely inferred from the endpoint path and the known Google Maps computeRoutes v2 API.
Warnings
- —Endpoint returned 404 on HEAD and GET — no 402 MPP challenge was captured. It may only respond to POST, or it may be down.
- —No documentation, pricing, or OpenAPI schema found at the provider origin (all pages returned 404).
- —Pricing and payment details (amount, currency, decimals) are unknown — no MPP challenge was observed.
- —Request and response schemas are inferred from the standard Google Maps Routes API and are not confirmed for this MPP wrapper.