API archive entry · source-reported
Mexico
Mexico RESTful zip codes API
From the publisher
README & documentation
Source previewRead the project’s overview, installation instructions and usage examples. The original README is the source of truth.
Every Mexican zip code, state, municipality, city and settlement — one bundled SQLite database, no API key, no rate limit. [](https://github.com/IcaliaLabs/sepomex/releases) [](https://github.com/IcaliaLabs/sepomex/actions) [](https://codecov.io/gh/IcaliaLabs/sepomex) [](.ruby-version) [](Gemfile) [](#-mcp-server) [](LICENSE) Quick start · Hosted instance · Querying the API · MCP server · Development · Architecture Looking up a Mexican postal code usually means scraping the official Correos de México site or wrangling a clunky Excel export. Sepomex turns that same official dataset into a clean, paginated JSON API you can query by zip code, state, city, municipality or colony — and, as of v1.0.0, exposes it to AI agents through the Model Context Protocol as well. The whole catalog (154k settlements) ships inside the app as a SQLite database, so there's nothing external to provision: clone, load, run. Sepomex is designed to be self-hosted — the whole catalog ships with the code, so standing up your own copy is a few commands.…
Read the full README ↗ · Preview checked 2026-10-28T23:32:46.770Z
Inside the original README — Document outline
- 📮 Sepomex
- The open REST and MCP API for Mexico's postal codes
- Why Sepomex?
- ✨ Features
- 🌐 Hosted instance
- 🚀 Quick start
- 🧭 Querying the API
- Searching zip codes
- States, municipalities & cities
- Pagination
- 🤖 MCP server
- 🛠️ Development
Headings are captured from the source. Links open the publisher’s document, not a locally hosted copy.
Links from the README
References supplied by the publisher, not independently verified endorsements. Check the destination before downloading files or entering credentials.
Documentation belongs to its respective authors. A listing is not a grant of reuse or training rights. Confirm the document’s own terms at the source.
Where these facts came from
AltAPIs imported it from public-apis/public-apis. The source link and dates remain visible for independent inspection.
What is reported
- Name, category, and short description
- Authentication label
- HTTPS and CORS labels
- Provider/source URL
What is not established
- Current uptime or availability
- Pricing, quotas, and rate limits
- Security, compliance, or licensing posture
- SDK quality or endpoint completeness
Record checkpoints
- First observed: Sep 14, 2026
- Last directory-field change: Sep 14, 2026
- Current source observation: Oct 30, 2026
Source reference
This page separates source-reported facts from questions that need live provider verification.