Pay-per-call Google Maps Directions API via MPP on Tempo L2
What it does
This endpoint provides Google Maps Directions data through a Micropayment Protocol (MPP) gateway hosted at googlemaps.mpp.tempo.xyz. Each call returns driving/transit/walking/cycling directions between locations, proxying the Google Maps Directions API. Payment is settled per-request on Tempo L2 (chainId 4217) using pathUSD.
The MPP challenge confirms the endpoint is live and uses the "charge" intent, meaning each request is a one-shot payment. The cost is 5000 base units of pathUSD (6 decimals), which equals $0.005 per call. The provider covers gas fees (feePayer: true), so callers only pay the stated amount. The endpoint accepts GET requests and mirrors the standard Google Maps Directions JSON response format (origin, destination, waypoints, steps, polylines, duration, distance).
No dedicated documentation, OpenAPI schema, or landing page is available on the gateway itself. Callers should refer to the upstream Google Maps Directions API documentation for query parameter details (e.g., origin, destination, mode, waypoints, alternatives, avoid). The gateway likely passes these through as query parameters on the GET request.
Capabilities
Use cases
- —Get driving directions between two addresses for a logistics agent
- —Compute transit routes and estimated travel times for a travel planning assistant
- —Retrieve step-by-step walking or cycling directions for a mobile app agent
- —Compare alternative routes between origin and destination
- —Calculate distance and duration for delivery cost estimation
Fit
Best for
- —AI agents needing on-demand directions without managing Google API keys
- —Pay-per-call access to Google Maps Directions without monthly billing
- —Crypto-native applications that want to pay for geo services with stablecoins
Not for
- —High-volume batch geocoding or bulk route optimization (per-call pricing adds up)
- —Use cases requiring real-time traffic layer data or Street View imagery
- —Applications that need Places, Geocoding, or other non-Directions Google Maps endpoints (separate endpoints exist)
Quick start
curl -H "Authorization: Payment <tempo-payment-token>" \
"https://googlemaps.mpp.tempo.xyz/maps/directions/json?origin=New+York,NY&destination=Boston,MA&mode=driving"Endpoint
Quality
The MPP challenge is live and well-formed, confirming the endpoint works and pricing is clear ($0.005/call in pathUSD on Tempo L2). However, there is no documentation, no OpenAPI schema, no example responses, and the gateway root returns 404. All query parameter details are inferred from the upstream Google Maps Directions API.
Warnings
- —No documentation or OpenAPI schema available on the gateway
- —Gateway root and all doc paths return 404
- —Query parameters and response format are inferred from upstream Google Maps Directions API, not confirmed by the provider
- —Currency address 0x20c0...8b50 assumed to be pathUSD with 6 decimals based on Tempo L2 convention; if decimals differ, the stated price would be wrong
Citations
- —Endpoint is live and returns a 402 MPP challenge with intent=charge, method=tempo, chainId=4217https://googlemaps.mpp.tempo.xyz/maps/directions/json
- —Amount is 5000 base units; recipient is 0xca4e835F803cB0b7C428222B3A3B98518d4779Fe; feePayer is truehttps://googlemaps.mpp.tempo.xyz/maps/directions/json
- —Part of a broader Google Maps suite including geocoding, directions, places, routes, tiles, weather, and air qualityhttps://googlemaps.mpp.tempo.xyz/maps/directions/json