Postalia and PostalKit, compared
Let us get the awkward part out of the way first: Postalia is cheaper than PostalKit, at every volume, and it is not close. This page is about what the difference in price is actually buying, so that you can decide whether you want any of it.
What Postalia is
A Mexican postal code API with a deliberately small surface: one lookup, a token to authenticate, JSON back. Give it a postal code and it answers with código postal, estado, municipio, ciudad, zona, colonias, all in a single response. It reads the same national SEPOMEX catalog everything else here reads.
It publishes at this address:
postalia.com.mx
Side by side
| Item | PostalKit | Postalia |
|---|---|---|
| Free tier | 100 requests a month, no card | 1,000 queries a day |
| Paid | $149 MXN a month for 5,000, up to $1,499 MXN for 250,000 | $100 MXN a month, with no query ceiling |
| API surface | 21 endpoints across eight resource groups | One postal code lookup |
| A postal code lookup returns | estado, municipio, ciudad and colonias with their settlement type | código postal, estado, municipio, ciudad, zona, colonias |
Prices verified on August 17, 2026.
Where Postalia is the better buy
On price, and it is worth being specific rather than vague about it.
-
The free tier is far larger.
A thousand queries a day works out at roughly 30,000 a month against our 100. If your volume fits inside that, you would be paying us for something you can have for nothing.
-
The paid plan undercuts every tier here.
At $100 MXN a month with no ceiling against $149 MXN a month for 5,000 requests, there is no volume at which we are the cheaper postal code lookup. If a postal code lookup is what you are buying, buy theirs.
The other side
Where the extra buys you something
The comparison stops being about price the moment your question stops being “what is at this postal code”.
-
You can walk the hierarchy in either direction.
List the municipios of an estado, page every postal code in a municipio, or search colonias by name. Those are endpoints here rather than a lookup you call in a loop and stitch together.
-
Identifiers you can store.
The catalog is kept as related tables and the ids survive a refresh, so a colonia id on a customer record still resolves next month. A lookup that returns names as text leaves you matching on strings.
-
Knowing which version answered you.
The source is re-checked on the first of every month, nothing moves unless it changed, and GET /v1/account/db-version tells you what you are reading. Useful exactly when a customer insists their colonia exists.
-
A published spec.
An OpenAPI document and a Postman collection, regenerated on every deploy, and rate-limit headers on every response.
Which one to pick
If you want a postal code turned into an estado, a municipio and a list of colonias, and you want it at the lowest price, Postalia is the better purchase and this page is not going to pretend otherwise. If you are modelling Mexican addresses rather than filling in one form field — joining on identifiers, listing a state’s municipios, tracking what changed between releases — that is what the difference pays for.
The same comparison against the other two: Copomex, DIPOMEX. If you have not picked a provider at all yet, the SEPOMEX catalog guide covers the free official file first.