ZIP Codes API MCP. Audit locations and calculate distances by asking questions.

ZIP Codes API connects your AI client straight to authoritative location data covering the whole US and Canada. This isn't just a lookup sheet; it lets your agent run serious geographic queries—think market analysis or complex logistics planning—without you having to manually cross-reference maps or call anyone. It gives you the raw data, period.

Finding Locations by Jurisdiction:

You can pinpoint areas using several reliable methods. If you know a state or province, your agent uses find_zips_by_state to list every single 5-digit ZIP code in that entire area. Need to narrow it down further? You've got the option to pull all codes based on a governmental county boundary by calling find_zips_by_county.

Better yet, if you know both the city and state, your agent can use find_zips_by_city to grab only the ZIPs tied to that specific combination. These tools let you filter down huge areas quickly.

Targeting by Proximity or Detail:

Want to find everything within a certain area? You tell it a starting ZIP code and a mile radius, and find_zips_in_radius returns every single ZIP that falls inside that circle. For deep dives on a single location, you can get the full picture for one exact ZIP with get_zip_details. This tool pulls all the metadata: city, state, county, latitude, and longitude—all in one go.

Need to know how far apart two spots are? You just pass two different ZIPs to get_zip_distance, and it calculates the precise straight-line or driving mileage between them.

How Your Agent Uses This Data:

Your agent doesn't just run a single query; it chains these tools together based on your request. Say you ask, "Show me all delivery zones within 10 miles of 90210 that are in Los Angeles County." The agent won't guess—it knows it has to first use find_zips_in_radius with the starting point and the distance limit.

Then, it takes those results and filters them using data from a call to find_zips_by_county. It synthesizes all that geographic junk into one clean answer for you.

You talk to your agent naturally; it handles the whole geography stack. You can combine multiple calls—like getting an initial list of ZIPs by state, then passing those results through a radius check, and finally fetching detailed metadata on the top five results—all in one go. It's about making verifiable decisions with hard data.

Advanced Use Cases:

If you need to compare two separate areas for logistics planning, your agent can use get_zip_distance repeatedly across many pairs of ZIP codes and compile a full matrix of distances. This saves hours compared to checking mileage on a map yourself. You're not limited by what one tool does; the combination is where the power is.

You can pull all location data in layers: first, you define the boundaries using find_zips_by_state, then refine those results by county using find_zips_by_county, and finally narrow that down to a specific city group via find_zips_by_city. This layered approach lets you audit boundaries with extreme precision. If your initial query is too broad, say for an entire state, you can immediately limit the scope by calculating distances from a key metropolitan area using find_zips_in_radius to get actionable results fast.

If you need verification that a ZIP code actually exists and what its full demographic profile is—including latitude and longitude—you rely on get_zip_details. This single function serves as the ultimate data check for any specific 5-digit code.

The system supports complex, multi-step reasoning: You could ask your agent to identify all ZIP codes in a state that are also within five miles of another specific ZIP code, and then give you the detailed county information for each one. The API handles this entire chain: find_zips_by_state -> (Filter/Pass) -> find_zips_in_radius -> (Result Set) -> get_zip_details / find_zips_by_county.

It's rock solid. You feed it the request, and it spits out usable geographic metrics for US and Canadian locations every time.