Validate postal addresses via Google Maps Address Validation API, settled over MPP/Tempo.
What it does
This endpoint exposes Google Maps Platform's Address Validation API through the Tempo MPP (Micropayment Protocol) gateway at googlemaps.mpp.tempo.xyz. The Address Validation API checks whether a postal address is deliverable, returns standardized/corrected address components, geocode data, and USPS metadata (for US addresses). It is intended for pay-per-call usage settled in pathUSD on the Tempo L2 network.
The endpoint path follows the Google Maps Address Validation v1 REST convention (`/validation/v1:validateAddress`), which normally accepts a POST request with a JSON body containing the address to validate. Callers should expect to receive an MPP 402 payment challenge when calling with the correct HTTP method (POST), after which payment can be completed to unlock the response.
Note: During probing with HEAD and GET methods, the endpoint returned 404 rather than the expected 402 payment challenge. This is consistent with the endpoint being routed exclusively to POST requests. The root domain and all documentation paths also return 404, so no pricing, schema, or usage documentation could be verified from the provider directly. All capability claims are inferred from the endpoint path and the existing listing description.
Capabilities
Use cases
- —Validating customer shipping addresses at checkout before dispatching orders
- —Standardizing and correcting user-entered addresses in CRM or ERP systems
- —Checking deliverability of postal addresses for direct mail campaigns
- —Enriching address records with geocode coordinates and metadata
Fit
Best for
- —E-commerce platforms needing real-time address validation
- —Logistics and shipping applications requiring standardized addresses
- —Data-quality pipelines that clean and normalize address fields
Not for
- —Reverse geocoding (coordinate-to-address lookups)
- —Driving directions or route optimization
- —Bulk offline address validation without per-call payment capability
Quick start
curl -X POST https://googlemaps.mpp.tempo.xyz/validation/v1:validateAddress \
-H "Content-Type: application/json" \
-d '{"address":{"addressLines":["1600 Amphitheatre Parkway","Mountain View, CA 94043"]}}'Example
Request
{
"address": {
"addressLines": [
"1600 Amphitheatre Parkway",
"Mountain View, CA 94043"
]
}
}Endpoint
Quality
The endpoint returned 404 on HEAD and GET probes (likely because it only accepts POST), and all documentation/root paths are 404. No pricing, schema, or live 402 challenge was captured. All claims are inferred from the URL path and existing listing metadata; nothing could be directly verified.
Warnings
- —Endpoint returned 404 on HEAD and GET — likely POST-only, but no 402 challenge was captured to confirm liveness.
- —No documentation, pricing, or OpenAPI schema available from the provider domain.
- —Root domain returns 404; provider landing page is absent.
- —Price and settlement details (pathUSD amount, decimals) could not be verified.
- —All capability claims are inferred from the URL path and Google Maps Address Validation API conventions, not from direct evidence.