Forward & Reverse Geocoding
Resolve a location or address query to current place candidates and coordinates through Open-Meteo.
Preview request
The preview path is rate-limited and does not charge. Production requests use the same parameters and return a standard x402 challenge when no payment signature is present.
curl --request GET \ "https://ai-data-marketplace-1042299154756.us-central1.run.app/api/v1/geocoding?preview=true&address=1600+Amphitheatre+Parkway%2C+Mountain+View%2C+CA"
Input contract
| Parameter | Type | Required | Description |
|---|---|---|---|
address | string | No | Address to convert to coordinates. |
lat | number | No | Latitude for reverse geocoding. |
lng | number | No | Longitude for reverse geocoding. |
Guaranteed response metadata
Every successful product response identifies how the result was produced. Product-specific output fields are documented in the paid OpenAPI contract and can be inspected through the preview request where available.
{
"marketplace_metadata": {
"data_mode": "live_source",
"billable": true,
"availability": "operational",
"source": "Open-Meteo Geocoding API"
}
}Agent payment flow
Request the product, read the base64 PAYMENT-REQUIRED challenge, sign the exact Base-USDC authorization with an x402 buyer client, and retry using PAYMENT-SIGNATURE. A successful response includes PAYMENT-RESPONSE.