Open Company Data in Mexico: Official Sources, APIs and Reuse Rights

Mexico is one of the most commercially useful Latin American markets for company-data work, but it has to be framed carefully. The Registro Publico de Comercio and SIGER are the legal-register route for mercantile-company acts, while INEGI’s DENUE API is a very strong official directory of establishments. Those two layers answer different questions and should not be collapsed into one claim.

The best practical source stack combines RPC/SIGER, DENUE API and INEGI reuse terms, datos.gob.mx, CompraNet, SAT known-RFC validation, IMPI open IP data, the Diario Oficial de la Federacion, CNBV supervised-entity information and GLEIF LEI data. The stack is strong, but it is not a single marketing-ready file and it is not a substitute for privacy, tax, contact-data or anti-spam review.

This Wave 44 refresh replaces the older thin Mexico page with a deeper reference article: editorial methodology, coverage and update-risk analysis, reuse checklist, source-by-source deep dives, practical manual/API/bulk options, missing-data gaps, a recommended data model, CompaniesData value and indexing/crawlability QA.

Key Takeaways

• Best legal-register backbone: Registro Publico de Comercio / SIGER for mercantile-company registrations and acts.
• Best official API layer: INEGI DENUE for establishments, locations, activity and size, with terms and attribution preserved.
• Best enrichment routes: datos.gob.mx, CompraNet open data, SAT known-RFC validation, IMPI open data, DOF, CNBV and GLEIF.
• Main caution: DENUE records establishments, not legal companies; SAT validates known RFCs, not open marketing lists.
• CompaniesData value: useful delivery needs entity/establishment separation, identifier normalization, Spanish-name handling, source provenance, update dates and contact-data governance.

Editorial Methodology

This article follows the CompaniesData country-source method. Official registry and official open-data sources are prioritized first. Statistics, procurement, tax identifier checks, intellectual property, gazette publications, financial regulators and LEI data are treated as enrichment layers because they answer different questions, have different update schedules and carry different reuse limits.

Each final linked source was checked from this environment on 2026-06-09. Hard 404/410 routes are excluded. Sources that are useful but do not prove the claim needed for publication are documented as held-source notes. Source logos are decorative favicon cues only; the evidence remains the official URL, owner, access model and reuse note.

Coverage, Access and Update-Risk Analysis

RPC/SIGER boundary: RPC/SIGER is the legal-register route and should anchor legal-company evidence, but this refresh does not claim a complete open bulk export of every Mexican mercantile company. Portal workflows, public-user access and document-level extracts need their own terms review.

DENUE boundary: DENUE is the strongest official machine-readable business layer in Mexico, but it is an establishment directory. A single legal company may have multiple establishments, and an establishment record should not be treated as the same object as a corporate registration.

Open-data boundary: datos.gob.mx is the federal discovery layer for public datasets. It is useful for finding machine-readable files, but licence, owner, update date, file availability and field quality must be checked dataset by dataset.

SAT/RFC boundary: SAT known-RFC validation can confirm whether an RFC is valid in the taxpayer register, including batch validation up to the source workflow’s stated limit. It is not a bulk company-discovery source, not a general enrichment API and not a contact-data source.

Procurement boundary: CompraNet can identify suppliers and buyer-unit activity, but it covers public procurement participation rather than the whole business universe. Store procurement as an activity layer, not as entity identity.

IP/regulator/gazette boundary: IMPI, DOF, CNBV and GLEIF are useful enrichment and verification routes. They are not interchangeable with RPC/SIGER or DENUE and should be joined with confidence scores.

Contact-data boundary: public registry, DENUE, SAT, procurement, IP, regulator or gazette evidence does not create permission for cold email or phone outreach. Marketing-contact enrichment needs separate lawful basis, suppression and opt-out handling.

Reuse Checklist

• Authority: record whether a field came from RPC/SIGER, INEGI/DENUE, datos.gob.mx, CompraNet, SAT, IMPI, DOF, CNBV or GLEIF.
• Access route: separate legal-register portal, API, dataset download, procurement file, known-RFC validation, IP publication, gazette search, regulator directory and LEI API workflows.
• Licence: preserve dataset licence, portal terms, attribution and no-endorsement notes before commercial reuse.
• Coverage: mark whether the source covers legal-register events, establishments, procurement suppliers, known RFCs, IP owners, official notices, regulated financial entities or LEI holders.
• Freshness: store source access date, dataset resource date, publication date, API response date or portal search date.
• Privacy: flag natural-person, address, representative, RFC, contact and small-business fields before reuse.
• Marketing: do not use public company records as a substitute for consent, suppression or contact-data compliance.
• Delivery: keep official evidence and commercial enrichment in separate fields so customers can audit provenance.

Resource Pack

Source-by-Source Deep Dives

1. Registro Publico de Comercio / SIGER

Authority: Secretaria de Economia / Registro Publico de Comercio. Type: official company register. Access model: portal / search / registration-document workflow. Reuse position: registry and portal terms; bulk reuse not evidenced.

Legal-register backbone for mercantile-company acts and registrations. Store the exact URL, access date, original identifier, source class, licence note and update timestamp before merging the field into a normalized Mexico company profile.

Limitations and operating notes: This is the legal register route, but it is not evidenced as one complete open bulk export. This source should be used as a defined evidence layer, not as blanket proof of complete coverage, official endorsement, contact permission or unrestricted redistribution.

2. SIGER FAQ

Authority: Secretaria de Economia / Registro Publico de Comercio. Type: official registry documentation. Access model: FAQ / portal documentation. Reuse position: official documentation; reuse claims require source-specific caution.

Explains the public-register route, operational support and user workflow context. Store the exact URL, access date, original identifier, source class, licence note and update timestamp before merging the field into a normalized Mexico company profile.

Limitations and operating notes: Documentation is not a bulk-data licence or a complete API specification. This source should be used as a defined evidence layer, not as blanket proof of complete coverage, official endorsement, contact permission or unrestricted redistribution.

3. SIGER public-user login

Authority: Secretaria de Economia / Registro Publico de Comercio. Type: official registry portal. Access model: login / public-user portal / controlled access. Reuse position: portal terms and controlled-use caution.

Manual legal-register verification and document-workflow access. Store the exact URL, access date, original identifier, source class, licence note and update timestamp before merging the field into a normalized Mexico company profile.

Limitations and operating notes: Login workflow is not crawler-safe bulk data and may require user-account review. This source should be used as a defined evidence layer, not as blanket proof of complete coverage, official endorsement, contact permission or unrestricted redistribution.

4. INEGI DENUE API

Authority: INEGI. Type: official statistics API. Access model: API / documented endpoints. Reuse position: INEGI free-use terms with attribution and no-endorsement caution.

High-value establishment identity, geography, activity and size enrichment. Store the exact URL, access date, original identifier, source class, licence note and update timestamp before merging the field into a normalized Mexico company profile.

Limitations and operating notes: DENUE is an establishment directory, not the legal company register. This source should be used as a defined evidence layer, not as blanket proof of complete coverage, official endorsement, contact permission or unrestricted redistribution.

5. DENUE map and search

Authority: INEGI. Type: official statistics search. Access model: map / search / manual verification. Reuse position: INEGI terms and source-citation caution.

Manual verification of establishments before API ingestion or matching. Store the exact URL, access date, original identifier, source class, licence note and update timestamp before merging the field into a normalized Mexico company profile.

Limitations and operating notes: Map search does not replace API limits, field checks or legal-entity matching. This source should be used as a defined evidence layer, not as blanket proof of complete coverage, official endorsement, contact permission or unrestricted redistribution.

6. INEGI terms of use

Authority: INEGI. Type: official reuse terms. Access model: terms / legal notice. Reuse position: free use with attribution, integrity and no-endorsement boundaries.

Reuse-rights basis for DENUE and other INEGI statistical products. Store the exact URL, access date, original identifier, source class, licence note and update timestamp before merging the field into a normalized Mexico company profile.

Limitations and operating notes: Dataset-specific notices and privacy controls still need review. This source should be used as a defined evidence layer, not as blanket proof of complete coverage, official endorsement, contact permission or unrestricted redistribution.

7. INEGI open data

Authority: INEGI. Type: official open data. Access model: downloads / APIs / open-data documentation. Reuse position: INEGI open-data terms and attribution requirements.

Official open-data context for statistical business datasets. Store the exact URL, access date, original identifier, source class, licence note and update timestamp before merging the field into a normalized Mexico company profile.

Limitations and operating notes: Open statistical data is not automatically legal-register data. This source should be used as a defined evidence layer, not as blanket proof of complete coverage, official endorsement, contact permission or unrestricted redistribution.

8. datos.gob.mx

Authority: Government of Mexico. Type: official open-data portal. Access model: catalogue / dataset discovery / downloads. Reuse position: dataset-specific and portal open-data terms.

Federal data discovery for procurement, statistics, transparency and public datasets. Store the exact URL, access date, original identifier, source class, licence note and update timestamp before merging the field into a normalized Mexico company profile.

Limitations and operating notes: Dataset freshness, resource links and licence metadata vary by owner. This source should be used as a defined evidence layer, not as blanket proof of complete coverage, official endorsement, contact permission or unrestricted redistribution.

9. datos.gob.mx about

Authority: Government of Mexico. Type: official open-data documentation. Access model: portal documentation. Reuse position: portal terms and dataset-specific reuse notes.

Explains the official open-data portal context and governance framing. Store the exact URL, access date, original identifier, source class, licence note and update timestamp before merging the field into a normalized Mexico company profile.

Limitations and operating notes: About-page wording is context, not a licence for every dataset. This source should be used as a defined evidence layer, not as blanket proof of complete coverage, official endorsement, contact permission or unrestricted redistribution.

10. CompraNet

Authority: Government of Mexico / CompraNet. Type: official procurement portal. Access model: portal / public procurement information. Reuse position: procurement-publication and portal terms.

Tender, buyer-unit and supplier-activity enrichment for public-sector sales signals. Store the exact URL, access date, original identifier, source class, licence note and update timestamp before merging the field into a normalized Mexico company profile.

Limitations and operating notes: Procurement coverage is a supplier-activity subset, not a complete company universe. This source should be used as a defined evidence layer, not as blanket proof of complete coverage, official endorsement, contact permission or unrestricted redistribution.

11. CompraNet open data

Authority: CompraNet / Secretaria Anticorrupcion y Buen Gobierno. Type: official procurement open data. Access model: open-data page / downloads / data dictionaries. Reuse position: open-data and dataset-specific procurement terms.

Machine-readable procurement enrichment around buyer units, suppliers and contract history. Store the exact URL, access date, original identifier, source class, licence note and update timestamp before merging the field into a normalized Mexico company profile.

Limitations and operating notes: Fields and platform periods must be reviewed before longitudinal claims. This source should be used as a defined evidence layer, not as blanket proof of complete coverage, official endorsement, contact permission or unrestricted redistribution.

12. SAT RFC validation

Authority: Servicio de Administracion Tributaria. Type: official tax / identifier lookup. Access model: known-RFC validation / web workflow / batch up to source limit. Reuse position: SAT workflow terms, purpose limitation and privacy caution.

Known-RFC validation and authenticity checks for identifiers already held lawfully. Store the exact URL, access date, original identifier, source class, licence note and update timestamp before merging the field into a normalized Mexico company profile.

Limitations and operating notes: Not a company database, not a contact source and not an enrichment API for unknown entities. This source should be used as a defined evidence layer, not as blanket proof of complete coverage, official endorsement, contact permission or unrestricted redistribution.

13. IMPI open data

Authority: Instituto Mexicano de la Propiedad Industrial. Type: official IP open data. Access model: open-data portal / downloads. Reuse position: public/open-data terms and dataset-specific notices.

Trademark, patent and brand-owner enrichment for company profiles. Store the exact URL, access date, original identifier, source class, licence note and update timestamp before merging the field into a normalized Mexico company profile.

Limitations and operating notes: IP owner names require normalization and are not proof of full legal-company coverage. This source should be used as a defined evidence layer, not as blanket proof of complete coverage, official endorsement, contact permission or unrestricted redistribution.

14. IMPI data-open transparency page

Authority: Instituto Mexicano de la Propiedad Industrial. Type: official open-data guidance. Access model: open-data documentation. Reuse position: open-data guidance with dataset-specific caveats.

Reuse and access context for IMPI open IP datasets. Store the exact URL, access date, original identifier, source class, licence note and update timestamp before merging the field into a normalized Mexico company profile.

Limitations and operating notes: Guidance is not a matching key to legal-company status. This source should be used as a defined evidence layer, not as blanket proof of complete coverage, official endorsement, contact permission or unrestricted redistribution.

15. IMPI trademarks data

Authority: Instituto Mexicano de la Propiedad Industrial. Type: official IP data. Access model: open data / downloads / publications. Reuse position: public/open-data terms and dataset-specific notices.

Trademark-owner and brand-signal enrichment. Store the exact URL, access date, original identifier, source class, licence note and update timestamp before merging the field into a normalized Mexico company profile.

Limitations and operating notes: Trademark ownership is an enrichment signal, not a full company record. This source should be used as a defined evidence layer, not as blanket proof of complete coverage, official endorsement, contact permission or unrestricted redistribution.

16. Diario Oficial de la Federacion

Authority: Diario Oficial de la Federacion. Type: official gazette / legal publication. Access model: search / official publications / documents. Reuse position: official-publication terms and document-specific caution.

Legal notices, regulations and company-related publication context. Store the exact URL, access date, original identifier, source class, licence note and update timestamp before merging the field into a normalized Mexico company profile.

Limitations and operating notes: Document publication is not normalized company master data. This source should be used as a defined evidence layer, not as blanket proof of complete coverage, official endorsement, contact permission or unrestricted redistribution.

17. CNBV supervised entities

Authority: Comision Nacional Bancaria y de Valores. Type: financial regulator / supervised entities. Access model: directory / regulator publication. Reuse position: regulator-publication terms and source-citation caution.

Financial-sector regulated-entity enrichment and compliance context. Store the exact URL, access date, original identifier, source class, licence note and update timestamp before merging the field into a normalized Mexico company profile.

Limitations and operating notes: Sector-specific coverage only; not a general company register. This source should be used as a defined evidence layer, not as blanket proof of complete coverage, official endorsement, contact permission or unrestricted redistribution.

18. GLEIF LEI API for Mexico

Authority: Global Legal Entity Identifier Foundation. Type: global legal-entity identifier data. Access model: API / open LEI data. Reuse position: GLEIF API and open-data terms.

LEI cross-checks for Mexican legal entities in finance, KYB and compliance workflows. Store the exact URL, access date, original identifier, source class, licence note and update timestamp before merging the field into a normalized Mexico company profile.

Limitations and operating notes: LEI coverage is a regulated subset and is not comprehensive Mexico company coverage. This source should be used as a defined evidence layer, not as blanket proof of complete coverage, official endorsement, contact permission or unrestricted redistribution.

Practical Manual, API and Bulk Options

1. Start with RPC/SIGER for legal-company evidence

The safest legal-register workflow starts with RPC/SIGER documentation and the public-user portal. Store the source URL, search date, document reference, act type and confidence level. Do not claim unrestricted scraping or complete free bulk unless the exact extract route and terms prove it.

2. Use DENUE for establishment-scale API coverage

DENUE is the best automated route for official establishment data. Treat each record as an establishment with activity, geography and size evidence. When matching to a company master, preserve a separate establishment table and matching confidence rather than overwriting the legal entity.

3. Use datos.gob.mx for dataset discovery

datos.gob.mx can surface federal datasets that help with procurement, transparency and public-sector context. Each dataset needs a resource URL, owner, file format, update date, licence note and parser version.

4. Add procurement, tax, IP, regulator, gazette and LEI layers

CompraNet open data can enrich suppliers and public contracts. SAT known-RFC validation can confirm identifiers already held lawfully. IMPI enriches IP and brand-owner evidence. DOF provides legal-publication context. CNBV identifies regulated financial entities. GLEIF adds LEI cross-checks for a subset of entities.

Held Source-Risk Findings

Two useful but legally sensitive claims are deliberately held rather than published as broad statements.

• Complete RPC/SIGER bulk export: RPC/SIGER is official and live, but this cycle does not use it to claim one complete free legal-company bulk file.
• General SAT taxpayer universe: SAT known-RFC validation is useful, but a general taxpayer universe is not treated as public company-discovery data or marketing-contact evidence.

Missing Data Gaps

• No one-file universe: do not claim a single complete free legal-company bulk database for all Mexican business entities.
• Legal-register scope: RPC/SIGER is the legal route, while DENUE and procurement are separate evidence layers.
• Establishment scope: DENUE can include multiple locations for one business and should not be deduplicated into companies without matching logic.
• Tax scope: known-RFC checks support verification, not full profile extraction or marketing enrichment.
• Procurement subset: procurement suppliers represent public-sector activity, not every company.
• IP and regulator subset: IMPI, CNBV and GLEIF enrich profiles but do not prove comprehensive legal status.
• Personal-data caution: RFC, representatives, addresses and contact fields require privacy review before commercial reuse.

Recommended Data Model

A Mexico company dataset should use a stable entity table plus separate evidence tables. The data model should not hide whether a field came from RPC/SIGER, DENUE, datos.gob.mx, CompraNet, SAT, IMPI, DOF, CNBV or GLEIF.

• Entity core: normalized legal name, country, RFC/identifier where lawful, entity type, status, internal CompaniesData identifier and source confidence.
• Registry evidence: RPC/SIGER URL, search route, registration act, document reference, date, access route and parser version.
• Establishment evidence: DENUE id, establishment name, activity, geography, size band, source date and company-match confidence.
• Open-data evidence: datos.gob.mx dataset URL, owner, resource date, licence metadata, file format and transformation date.
• Tax checks: SAT known-RFC result, response date, purpose flag and privacy limitation.
• Enrichment joins: CompraNet supplier activity, IMPI owner names, DOF notices, CNBV regulated status and LEI records.
• Risk flags: personal-data caution, marketing-use blocked, licence unclear, held-source dependency, outdated source and manual-review required.
• Delivery fields: normalized names, deduplicated IDs, source URLs, activity segments, CRM-ready categories and suppression markers.

How CompaniesData Adds Value

CompaniesData turns fragmented Mexican public-source evidence into a usable dataset. The value is normalization, deduplication, source provenance, identifier matching, establishment-to-entity separation, update tracking and delivery formats that do not force users to parse portals manually.

For English and international users, CompaniesData.cloud is the preferred owned route: request a CompaniesData sample for Mexico. For Spanish-speaking or Hispanic contact-data workflows, CentraldeComunicacion.es is the preferred owned property. Contact-data enrichment remains separate from official company-data reuse.

No complete-bulk claim: this article deliberately avoids claiming one single complete free legal-company bulk database for all Mexican business entities; the safe statement is that Mexico combines a legal-register route, a strong establishment API and separate enrichment layers.

Source Matrix

Source	Owner / authority	Access model	Reuse note	Main limitation
Registro Publico de Comercio / SIGER	Secretaria de Economia / Registro Publico de Comercio	portal / search / registration-document workflow	registry and portal terms; bulk reuse not evidenced	This is the legal register route, but it is not evidenced as one complete open bulk export.
SIGER FAQ	Secretaria de Economia / Registro Publico de Comercio	FAQ / portal documentation	official documentation; reuse claims require source-specific caution	Documentation is not a bulk-data licence or a complete API specification.
SIGER public-user login	Secretaria de Economia / Registro Publico de Comercio	login / public-user portal / controlled access	portal terms and controlled-use caution	Login workflow is not crawler-safe bulk data and may require user-account review.
INEGI DENUE API	INEGI	API / documented endpoints	INEGI free-use terms with attribution and no-endorsement caution	DENUE is an establishment directory, not the legal company register.
DENUE map and search	INEGI	map / search / manual verification	INEGI terms and source-citation caution	Map search does not replace API limits, field checks or legal-entity matching.
INEGI terms of use	INEGI	terms / legal notice	free use with attribution, integrity and no-endorsement boundaries	Dataset-specific notices and privacy controls still need review.
INEGI open data	INEGI	downloads / APIs / open-data documentation	INEGI open-data terms and attribution requirements	Open statistical data is not automatically legal-register data.
datos.gob.mx	Government of Mexico	catalogue / dataset discovery / downloads	dataset-specific and portal open-data terms	Dataset freshness, resource links and licence metadata vary by owner.
datos.gob.mx about	Government of Mexico	portal documentation	portal terms and dataset-specific reuse notes	About-page wording is context, not a licence for every dataset.
CompraNet	Government of Mexico / CompraNet	portal / public procurement information	procurement-publication and portal terms	Procurement coverage is a supplier-activity subset, not a complete company universe.
CompraNet open data	CompraNet / Secretaria Anticorrupcion y Buen Gobierno	open-data page / downloads / data dictionaries	open-data and dataset-specific procurement terms	Fields and platform periods must be reviewed before longitudinal claims.
SAT RFC validation	Servicio de Administracion Tributaria	known-RFC validation / web workflow / batch up to source limit	SAT workflow terms, purpose limitation and privacy caution	Not a company database, not a contact source and not an enrichment API for unknown entities.
IMPI open data	Instituto Mexicano de la Propiedad Industrial	open-data portal / downloads	public/open-data terms and dataset-specific notices	IP owner names require normalization and are not proof of full legal-company coverage.
IMPI data-open transparency page	Instituto Mexicano de la Propiedad Industrial	open-data documentation	open-data guidance with dataset-specific caveats	Guidance is not a matching key to legal-company status.
IMPI trademarks data	Instituto Mexicano de la Propiedad Industrial	open data / downloads / publications	public/open-data terms and dataset-specific notices	Trademark ownership is an enrichment signal, not a full company record.
Diario Oficial de la Federacion	Diario Oficial de la Federacion	search / official publications / documents	official-publication terms and document-specific caution	Document publication is not normalized company master data.
CNBV supervised entities	Comision Nacional Bancaria y de Valores	directory / regulator publication	regulator-publication terms and source-citation caution	Sector-specific coverage only; not a general company register.
GLEIF LEI API for Mexico	Global Legal Entity Identifier Foundation	API / open LEI data	GLEIF API and open-data terms	LEI coverage is a regulated subset and is not comprehensive Mexico company coverage.

FAQ

Is Mexico a strong country for open company data?

Yes. Mexico is strong because RPC/SIGER provides the legal-register route, DENUE provides a powerful official establishment API, and procurement, tax validation, IP, gazette, regulator and LEI layers can enrich company profiles.

Is there one official bulk dataset covering all Mexican companies?

No. The safe claim is that Mexico has strong official sources and open-data layers, not one universal free legal-company file covering every company route and enrichment field.

What should I use first?

Start with RPC/SIGER for legal-register evidence and DENUE for establishment data. Then add datos.gob.mx, CompraNet, SAT known-RFC validation, IMPI, DOF, CNBV and GLEIF as separate evidence layers.

Can DENUE be used as a company register?

No. DENUE is official and very useful, but it is an establishment directory. Treat it as location/activity evidence and match it to a company master only with source provenance and confidence scoring.

Can SAT data be used for bulk enrichment?

SAT known-RFC validation is useful for checking identifiers already held lawfully, but it should not be treated as a bulk company-profile database or marketing-contact source.

Can public Mexico company data be used for cold email?

Not automatically. Marketing requires a separate lawful basis, suppression logic, opt-out handling and contact-data compliance review.

Why use CompaniesData instead of collecting Mexico sources manually?

Manual collection is slow because sources have different identifiers, languages, update schedules, legal meanings and access models. CompaniesData normalizes, matches, deduplicates and packages the evidence for practical use.

Official Sources

• Registro Publico de Comercio / SIGER – Secretaria de Economia / Registro Publico de Comercio
• SIGER FAQ – Secretaria de Economia / Registro Publico de Comercio
• SIGER public-user login – Secretaria de Economia / Registro Publico de Comercio
• INEGI DENUE API – INEGI
• DENUE map and search – INEGI
• INEGI terms of use – INEGI
• INEGI open data – INEGI
• datos.gob.mx – Government of Mexico
• datos.gob.mx about – Government of Mexico
• CompraNet – Government of Mexico / CompraNet
• CompraNet open data – CompraNet / Secretaria Anticorrupcion y Buen Gobierno
• SAT RFC validation – Servicio de Administracion Tributaria
• IMPI open data – Instituto Mexicano de la Propiedad Industrial
• IMPI data-open transparency page – Instituto Mexicano de la Propiedad Industrial
• IMPI trademarks data – Instituto Mexicano de la Propiedad Industrial
• Diario Oficial de la Federacion – Diario Oficial de la Federacion
• CNBV supervised entities – Comision Nacional Bancaria y de Valores
• GLEIF LEI API for Mexico – Global Legal Entity Identifier Foundation