← Back to Blog
philosophydeveloper-experienceapipricingannouncement

We Built the Postal Code API We'd Want to Use Ourselves

The PostalDataPI Team··5 min read

We asked one question before building PostalDataPI:

What would annoy us if we were our own customer?

Then we eliminated every single one of those things.

No Tiers

Most postal code APIs charge $75 for the small plan, $240 for the medium plan, $800 for the large plan. You pick a tier, you watch your usage nervously, and when you outgrow it you jump to the next price bracket — sometimes 3x more for 2x the volume.

That would annoy us.

PostalDataPI has one price: $0.000028 per query. That is 2.8 cents per thousand queries. A soccer mom doing a big mail-out for her soccer league pays the same rate as an enterprise company processing millions of shipments. Or she uses her 1,000 free queries and pays nothing at all.

No tiers. No "contact sales for enterprise pricing." No surprise at the end of the month.

Self-Serve Everything

We wanted full control over our own account — the kind of control that does not require emailing support and waiting 48 hours.

So we built it that way:

  • Recharge your balance in 3 clicks. Set up auto-recharge so you never run dry.
  • Reset your API key yourself, instantly, whenever you need to. No support ticket.
  • Set your own rate limits. You decide how fast your application can query — per minute, per hour, per day. Not us.
  • See your abuse activity. If something unusual happens on your account, you see it first. No black boxes.
  • Choose your maintenance windows. Your schedule, not ours.
  • Full recharge history and usage logs. Every transaction, every query pattern, transparent.
If you would not want to wait for it, neither would we. So we made it self-serve.

240+ Countries and Territories, Same Price

Some APIs charge different rates per country. US lookups at $0.01, UK at $0.02, Japan at $0.05. That would annoy us — especially if we needed 10 countries for a global checkout flow.

PostalDataPI serves 240+ countries and territories at the same $0.000028 per query. United States, United Kingdom, Germany, Japan, Brazil, Nigeria, Australia — same price, same API, same response format.

We built dedicated country pages for every one of them, with format references, regex patterns, and working code examples.

Rich Metadata, Not Just City and State

A postal code lookup that returns city and state is table stakes. We wanted more. When we look up a postal code, we want to know:

  • What timezone is it in?
  • What administrative regions does it belong to?
  • What is the elevation?
  • What are the coordinates?
PostalDataPI returns up to 18 metadata fields per postal code. Here is Mexico City 06000: 
{
  "postalCode": "06000",
  "country": "MX",
  "placeName": "Centro (Área 1)",
  "latitude": 19.4364,
  "longitude": -99.1553,
  "timezone": "America/Mexico_City",
  "adminLevel1": "Ciudad de México",
  "adminLevel2": "Cuauhtémoc",
  "elevation": 2239,
  "state": "Ciudad de México",
  "municipality": "Cuauhtémoc",
  "city": "Ciudad de México"
}

Timezone, three levels of admin hierarchy, elevation in meters, coordinates — all in one call.

Sub-5ms Because We Would Hate Waiting

If we were building a checkout form with address validation, we would want the response before the user finishes typing. Not after a loading spinner. Not after a round trip to a database on another continent.

PostalDataPI delivers sub-5ms cached responses. Most queries return in 1-3 milliseconds. Fast enough for autocomplete, form validation, and real-time applications.

One API Call, Every Country

We did not want to juggle different endpoints for different regions. We did not want country-specific SDKs. We did not want format-juggling middleware.

One call:

curl -s -X POST https://postaldatapi.com/api/lookup \
  -H "Content-Type: application/json" \
  -d '{"zipcode": "SW1A", "country": "GB", "apiKey": "YOUR_KEY"}'

Change the country parameter. That is it. Same endpoint, same format, same response structure, whether you are looking up a ZIP code in Montana or a postcode in Tokyo.

SDKs for Python and Node.js make it a one-liner. An MCP server gives AI agents direct access.

The Account Page Is the Philosophy

Every feature on the PostalDataPI account page exists because we asked: "Would this annoy us if we could not do it ourselves?"

The answer was always yes. So we built it.

  • Recharge balance → self-serve
  • Recharge history → fully transparent
  • API key management → instant reset
  • Rate control → your limits, not ours
  • Abuse monitoring → you see it first
  • Maintenance windows → your schedule
No hidden settings. No "contact support to change your plan." No features locked behind enterprise tiers.

Try It

If any of this resonates with how you think about developer tools, give it a try. 1,000 free queries on signup, no credit card required. Browse the 240+ country pages for format references. Read the API reference.

We built PostalDataPI for ourselves first. We think you will like using it too.

We Built the Postal Code API We'd Want to Use Ourselves | PostalDataPI Blog