US Address Intelligence
Validate, normalize and locate a US address in one pass.
$0.003-$0.005
estimated cost / run
4
API steps
-
measured success rate
Preview
paid run not yet recorded
What this bundle does
Address data arrives in inconsistent shapes: five-digit ZIPs, ZIP+4, full street addresses, latitude/longitude pairs and free-text city/state strings. An agent needs one reliable path from any of those inputs to a normalized place.
This bundle combines APIStead Labs' ZIP, geocoding and distance routes. The agent validates the ZIP, enriches it with city, state and coordinates, then uses the geocoder when a full street address is available. Every response includes a source and retrieval timestamp so the agent can carry evidence into the next step.
Workflow
- 1
Validate the ZIP and return city, state and coordinates.
US ZIP Code APIGET/us-zip/{zip}$0.001 - 2
Measure the distance between two ZIP centroids.
US ZIP Code APIGET/us-zip/distance?from={zip1}&to={zip2}$0.002 - 3
Geocode a full street address when one is available.
Geocoding & Reverse Geocoding APIGET/geocode?address={address}$0.001 - 4
Reverse geocode coordinates back to an address.
Geocoding & Reverse Geocoding APIGET/reverse?lat={lat}&lon={lon}$0.001
Agent prompt
Paste this into an agent that can call HTTP tools and pay x402 challenges.
You are an address validation agent. When the user provides a US address, ZIP code or coordinate pair:
1. If the input contains a ZIP code, call the US ZIP Code API for that ZIP. Keep the returned city, state, latitude, longitude, source and retrieved_at values.
2. If the input contains a full street address, call the Geocoding API with the address. Use the ZIP result as a cross-check when both are available.
3. If the input contains latitude and longitude, call the Reverse Geocoding API.
4. If the user asks about distance or delivery coverage, call the ZIP Distance route for two ZIPs, or the Coordinates Distance route for two coordinate pairs.
5. Return a single normalized object with: normalized_address, zip, city, state, latitude, longitude, distance_km (when requested), source and retrieved_at.
6. If a route returns 402, read the quoted price and network before paying. Never pay more than the amount shown in the challenge.
7. If a route returns an error, report which step failed and do not invent a value.Example output
Illustrative output. Sample values come from the preview routes, not a live run.
{
"normalized_address": "350 5th Ave, New York, NY 10118",
"zip": "10118",
"city": "New York",
"state": "NY",
"latitude": 40.7484,
"longitude": -73.9857,
"distance_km": 3.42,
"source": "zippopotam.us",
"retrieved_at": "2026-11-10T01:15:00Z"
}Use cases
- Check whether a delivery address is inside a service area
- Normalize a lead list before routing it to a field team
- Enrich a property record with coordinates and ZIP context
- Calculate a rough distance between two ZIP centroids