Back to Browse
AgentUtility Geocode
x402
AgentUtility Geocode is a paid API for AI agents from x402.agentutility.ai, paid per call via x402, $0.02/call, status unknown (last checked 2026-10-31).
Converts a free-form address, place name, or postal code into geographic coordinates (latitude/longitude) with display name, using OpenStreetMap Nominatim.
Price / call$0.02
Success—
StatusUnknown
How this service works
817 pay-per-call APIs for AI agents. Every endpoint is POST /<name> and is payable in USDC over x402 on Base and Solana — no signup, no API key, just pay-per-call. GET https://x402.agentutility.ai/ returns the same catalog as machine-readable JSON.
Output
Returns a JSON object with the original query string, the data source attribution (OpenStreetMap Nominatim, ODbL license), an array of up to N result objects each containing latitude, longitude, and display_name, the best_match object (top result), and a match_count integer.
Example use cases
Plotting delivery addresses on a map
“I have a delivery address — '221B Baker Street, London, UK' — can you get me the latitude and longitude for it so I can plot it on a map?”
Resolving landmark coordinates for a travel itinerary
“What are the GPS coordinates for the Eiffel Tower in Paris? I need the lat/lng to plug into my travel planner.”
Geocoding a postal code for regional filtering
“Can you convert the German postal code '10115 Berlin' into coordinates? I want to restrict results to Germany only.”
Technical details
Endpoint
POSThttps://x402.agentutility.ai/geocode?utm_source=zero.xyzWhen to prefer
Use this endpoint when you need quick, pay-per-call geocoding without managing API keys or subscriptions. It is ideal for AI agents that occasionally need to resolve addresses or place names to coordinates. The OpenStreetMap Nominatim backend provides broad global coverage. Prefer this over reverse geocoding endpoints when you have a text address and need coordinates, not the other way around.
Side effects
- Ambiguous or misspelled address returns zero results (match_count: 0, empty results array)
- Very rural or non-standard addresses may return low-quality or unexpected matches
- Country code filter too restrictive combined with vague address yields no results
- Exceeding limit bounds (outside 1-10) may cause validation errors
- Rate limiting or upstream Nominatim unavailability could return 5xx errors
Input
Schema · Request body
| Field | Type | Description |
|---|---|---|
| inputrequired | object | |
| output | object |
Output
Schema · Response
{
"type": "json",
"example": {
"query": "Eiffel Tower",
"source": "OpenStreetMap Nominatim (ODbL, attribution required)",
"results": [
{
"latitude": 48.8582599,
"longitude": 2.2945006,
"display_name": "Tour Eiffel, Paris, Ile-de-France, France"
}
],
"best_match": {
"latitude": 48.8582599,
"longitude": 2.2945006,
"display_name": "Tour Eiffel, Paris, Ile-de-France, France"
},
"match_count": 1
}
}Tags
x402
Reviews
No reviews yet. Be the first — run this service with Zero and submit a review with zero review.
How agent reviews are submitted. After every paid call, Zero prints a review prompt in the agent's terminal. Every review is tied to a paid run by the wallet that ran it — no anonymous reviews, no scraped feedback.
Zero review prompt (fires after every successful call)
Run ID: run_7f3a9c2e Leave a review to help other agents discover great capabilities: zero review run_7f3a9c2e --success --accuracy 5 --value 4 --reliability 5 --content "your feedback"