Pay-per-call access to Google Maps 3D Tiles root tileset via MPP on Tempo L2.
What it does
This endpoint provides pay-per-call access to the Google Maps 3D Tiles root.json file through the Micro-Payment Protocol (MPP) settled on Tempo L2 (chain ID 4217). The root.json is the entry point for Google Maps' Photorealistic 3D Tiles dataset, which uses the OGC 3D Tiles specification to serve textured 3D meshes of real-world locations. Agents or applications can fetch this tileset root to begin traversing and rendering 3D map content.
Each request costs 6000 base units of pathUSD (token address 0x20c0…8b50 on chain 4217). Assuming pathUSD uses 6 decimals, this equates to $0.006 per call. The provider covers gas fees (feePayer: true), so callers only need to sign the payment attestation without worrying about on-chain transaction costs. Settlement is handled via the Tempo method, and the challenge expires far in the future (April 2026).
No additional documentation, OpenAPI schema, or examples are available from the provider's origin site. The endpoint is confirmed live, returning a proper 402 MPP challenge on unauthenticated GET requests. The response after successful payment is expected to be a standard 3D Tiles root.json document conforming to the OGC 3D Tiles specification.
Capabilities
Use cases
- —Fetching the 3D Tiles root tileset to begin rendering photorealistic 3D maps
- —Integrating Google Maps 3D content into autonomous agent workflows
- —Building 3D visualization applications that pay per tile fetch
- —Programmatic access to 3D geographic data without API key management
Fit
Best for
- —Agents needing on-demand 3D map tile access without subscription
- —Applications rendering photorealistic 3D city models
- —Pay-as-you-go geographic visualization pipelines
Not for
- —High-volume bulk tile downloads (per-call cost adds up)
- —Use cases requiring full tileset traversal with thousands of sub-tiles at similar per-call pricing
- —Non-crypto workflows that cannot sign Tempo L2 payment attestations
Quick start
# Fetch the 3D Tiles root via MPP (pseudo-flow)
# 1. GET the endpoint to receive 402 challenge
curl https://googlemaps.mpp.tempo.xyz/tiles/v1/3dtiles/root.json
# 2. Sign the payment attestation for 6000 base units pathUSD on Tempo L2
# 3. Re-send GET with Authorization: Payment <signed_token>
curl -H "Authorization: Payment <signed_token>" \
https://googlemaps.mpp.tempo.xyz/tiles/v1/3dtiles/root.jsonEndpoint
Quality
The endpoint is confirmed live with a valid MPP 402 challenge, but there is no documentation, no OpenAPI schema, and no example responses available from the provider. Pricing and settlement details are inferrable from the challenge, but the response format is only assumed based on the 3D Tiles standard.
Warnings
- —No documentation or OpenAPI schema available from the provider origin
- —Currency token address (0x20c0…8b50) and decimal assumption (6) could not be independently verified
- —Response payload format is assumed to be OGC 3D Tiles root.json but not confirmed
- —Provider root returns 404 — no landing page or docs exist