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

Chile is one of the strongest Latin American candidates for practical open company data because the electronic Registro de Empresas y Sociedades (RES) gives a public registration workflow, datos.gob.cl exposes RES datasets, ChileCompra and Mercado Publico support procurement enrichment, and official tax, IP, regulator, gazette, statistics and LEI sources can be joined when provenance is preserved.

The correct framing is narrower than “one file with every Chilean company.” RES is excellent for the simplified electronic regime, but Chilean company evidence can also involve SII known-RUT tax status, legal-publication routes, procurement records, IP records, CMF regulated entities, INE statistics and LEI records. Those layers are commercially useful, but they are not interchangeable.

This Wave 42 refresh replaces the older thin Chile page with a deep reference article: source-by-source analysis, reuse and privacy cautions, practical manual/API/bulk routes, missing-data gaps, a recommended data model, CompaniesData value and crawler/indexing QA.

Key Takeaways

• Best official backbone: Registro de Empresas y Sociedades, its public documentation, FAQ, advanced search and RES dataset on datos.gob.cl.
• Best bulk/open-data route: datos.gob.cl RES datasets provide a stronger machine-readable layer than the portal search alone, but dataset periods and fields still need inspection.
• Best enrichment routes: ChileCompra API, Mercado Publico, SII known-RUT checks, INAPI, CMF regulated entities, Diario Oficial, INE and GLEIF.
• Main caution: SII, RUT, procurement, IP and RES records are not consent sources for email or phone marketing.
• CompaniesData value: useful delivery needs identifier normalization, Spanish-name handling, source dates, enrichment joins, legal-route flags and contact-data governance.

Editorial Methodology

This article follows the CompaniesData country-source method. Official registry and open-data sources are prioritized first. Procurement, tax, intellectual-property, regulator, gazette, statistics and LEI sources are treated as enrichment layers because they answer different questions and update on different schedules.

Each final linked source was checked from this environment on 2026-06-09. Hard 404/410 sources are excluded. Routes returning 000, 500 or unstable responses are documented as held-source notes and are not used as clean public evidence. 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

RES boundary: RES is the central electronic source for simplified-regime registration and public search, but it should not be treated as proof that every Chilean company route is available as one complete free bulk file. Older legal-publication or notarial routes can require separate review.

Open-data boundary: datos.gob.cl gives valuable dataset access, including RES datasets and reuse guidance. Dataset-level metadata, resource dates, file formats and licence fields should be recorded before building commercial claims.

SII boundary: the Servicio de Impuestos Internos third-party situation page is useful for known-RUT verification, but it is not a broad company-profile API, a contact-enrichment source or a marketing permission signal.

Procurement boundary: ChileCompra and Mercado Publico can identify suppliers and tender activity, but procurement coverage is a subset of the business universe and should be stored as activity evidence.

Contact-data boundary: public registry, tax, 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 RES, datos.gob.cl, ChileCompra, SII, INAPI, CMF, Diario Oficial, INE or GLEIF.
• Access route: separate portal search, CKAN download, API, known-RUT lookup, legal publication and regulator directory workflows.
• Licence: preserve dataset licence, portal terms, attribution and no-endorsement notes.
• Coverage: mark whether the source covers RES entities, procurement suppliers, known-RUT checks, IP owners, regulated financial entities, gazette notices, statistics or LEI holders.
• Freshness: store source access date, dataset resource date, publication date or API response date when available.
• Privacy: flag natural-person, RUT, address, representative and contact 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 de Empresas y Sociedades

Authority: Ministry of Economy / Registro de Empresas y Sociedades. Type: official company register. Access model: portal / search / certificates / workflows. Reuse position: portal terms; reuse requires source-specific caution.

Primary official electronic company-registration workflow for simplified-regime entities. Store the exact URL, access date, original identifier, source class, licence note and update timestamp before merging the field into a normalized Chile company profile.

Limitations and operating notes: Portal access is not the same as unrestricted bulk reuse or full coverage of every company route. 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. About the Registro de Empresas y Sociedades

Authority: Registro de Empresas y Sociedades. Type: official registry documentation. Access model: documentation. Reuse position: portal terms and official-publication caution.

Explains the RES model, legal purpose and public/free framing. Store the exact URL, access date, original identifier, source class, licence note and update timestamp before merging the field into a normalized Chile company profile.

Limitations and operating notes: Documentation is context; it is not a bulk-data licence or 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. RES FAQ

Authority: Registro de Empresas y Sociedades. Type: official registry documentation. Access model: FAQ / documentation. Reuse position: portal terms.

Confirms public-register framing and helps explain operational limits. Store the exact URL, access date, original identifier, source class, licence note and update timestamp before merging the field into a normalized Chile company profile.

Limitations and operating notes: FAQ wording should not be stretched into a broad redistribution right. 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. RES advanced search

Authority: Registro de Empresas y Sociedades. Type: official registry search. Access model: advanced search / RUT, CVE, name and date filters. Reuse position: portal terms and privacy caution.

Manual and semi-structured lookup for RES entities by identifiers and date windows. Store the exact URL, access date, original identifier, source class, licence note and update timestamp before merging the field into a normalized Chile company profile.

Limitations and operating notes: Search workflow, not a full bulk export service. 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. RES dataset on datos.gob.cl

Authority: Chilean open-data portal / RES dataset owner. Type: official open data. Access model: CKAN dataset / downloads. Reuse position: dataset licence and datos.gob.cl terms.

Bulk/open-data route for RES incorporation datasets and update-window analysis. Store the exact URL, access date, original identifier, source class, licence note and update timestamp before merging the field into a normalized Chile company profile.

Limitations and operating notes: Dataset periods, files and fields must be checked before claims about 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.

6. datos.gob.cl reuse guide

Authority: datos.gob.cl. Type: official open-data guidance. Access model: PDF guidance. Reuse position: open-data guidance and dataset-specific terms.

Context for reuse, attribution and responsible data-portal consumption. Store the exact URL, access date, original identifier, source class, licence note and update timestamp before merging the field into a normalized Chile company profile.

Limitations and operating notes: Guide, not legal advice and not a licence for every external source. 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. ChileCompra API

Authority: ChileCompra. Type: official procurement API. Access model: API / procurement data services. Reuse position: ChileCompra API terms, attribution and endpoint-specific conditions.

Supplier, tender, purchase-order and public-contract enrichment. Store the exact URL, access date, original identifier, source class, licence note and update timestamp before merging the field into a normalized Chile company profile.

Limitations and operating notes: Procurement-only coverage; not a legal company register or marketing list. 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. Mercado Publico

Authority: ChileCompra / Mercado Publico. Type: official procurement portal. Access model: portal / tenders / suppliers / workflows. Reuse position: portal and procurement notice terms.

Manual verification of supplier participation and public procurement activity. Store the exact URL, access date, original identifier, source class, licence note and update timestamp before merging the field into a normalized Chile company profile.

Limitations and operating notes: Procurement participation is a subset and may involve portal workflows. 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. SII third-party tax-status lookup

Authority: Servicio de Impuestos Internos. Type: official tax / identifier lookup. Access model: known-RUT lookup / web workflow. Reuse position: SII terms, purpose limitation and privacy caution.

Known-RUT tax-status verification and risk checks. Store the exact URL, access date, original identifier, source class, licence note and update timestamp before merging the field into a normalized Chile company profile.

Limitations and operating notes: Not a bulk company database, contact source or general enrichment API. 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. INAPI

Authority: Instituto Nacional de Propiedad Industrial. Type: official intellectual-property portal. Access model: search / services / publications. Reuse position: INAPI terms and dataset-specific conditions.

Trademark, patent and owner-name 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 Chile company profile.

Limitations and operating notes: IP data must be matched and is not proof of full legal entity 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.

11. INAPI open data

Authority: INAPI. Type: official IP open data. Access model: open-data portal / downloads. Reuse position: dataset-specific open-data terms.

Open IP datasets for patents, trademarks and related enrichment. Store the exact URL, access date, original identifier, source class, licence note and update timestamp before merging the field into a normalized Chile company profile.

Limitations and operating notes: IP open data is an enrichment layer, not a company-register 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.

12. CMF regulated entities

Authority: Comision para el Mercado Financiero. Type: financial regulator / supervised entities. Access model: directory / regulator publication. Reuse position: CMF 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 Chile company profile.

Limitations and operating notes: Sector-specific and not comprehensive 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.

13. Diario Oficial

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

Legal-publication context for company events and notices outside RES datasets. Store the exact URL, access date, original identifier, source class, licence note and update timestamp before merging the field into a normalized Chile company profile.

Limitations and operating notes: Document publication, not normalized company 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.

14. Instituto Nacional de Estadisticas

Authority: INE Chile. Type: official statistics. Access model: statistics portal / publications / datasets. Reuse position: statistics/publication terms and attribution caution.

Business-demography, sector and geography context for market-size checks. Store the exact URL, access date, original identifier, source class, licence note and update timestamp before merging the field into a normalized Chile company profile.

Limitations and operating notes: Aggregate statistics do not validate individual companies. 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. GLEIF LEI API for Chile

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 Chilean 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 Chile company profile.

Limitations and operating notes: LEI coverage is a regulated subset and is not comprehensive Chile 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 RES and datos.gob.cl

The best Chile workflow starts with RES public search and documentation, then uses the RES dataset on datos.gob.cl as the structured open-data layer. Store RUT or entity identifiers where lawful, legal name, creation or modification date, source URL, resource date and source confidence.

2. Add procurement and regulated-sector evidence

ChileCompra API and Mercado Publico add public-sector activity. CMF regulated-entity records add financial-sector context. These sources can materially improve commercial segmentation and compliance checks, but they must remain enrichment tables rather than the entity master.

3. Use SII only for known-RUT status checks

SII third-party status lookup should be used for a known identifier and a specific verification purpose. Do not describe it as bulk company data, do not infer marketing permission, and preserve response date and purpose limitation.

4. Join IP, gazette, statistics and LEI layers

INAPI can enrich companies with trademarks, patents and owner-name evidence. Diario Oficial adds legal-publication context. INE provides aggregate statistics for coverage benchmarking. GLEIF supports financial-sector legal-entity cross-checks. Each source needs its own matching confidence and source date.

Held Source-Risk Findings

Three researched official or high-quality routes are not linked as clean final evidence in this refresh because current live QA from this node did not return stable crawler-safe content.

• ChileCompra open-data subdomain: `abiertos.chilecompra.cl` returned 000; ChileCompra API and Mercado Publico are used instead.
• CMF API root and legacy SBIF terms: API/terms routes returned 000 or 500; CMF regulated-entities evidence is used instead.
• Boletin Oficial API: API route returned 000; Diario Oficial web route is used as the legal-publication source.

Missing Data Gaps

• No one-file universe: do not claim a single complete free legal-company bulk database for all Chilean business entities.
• RES scope: RES simplified-regime coverage is strong, but it is not the same as every historic or alternative legal-publication route.
• Tax scope: known-RUT 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: INAPI and CMF enrich profiles but do not prove comprehensive legal status.
• Personal-data caution: RUT, representatives, addresses and contact fields require privacy review before commercial reuse.

Recommended Data Model

A Chile company dataset should use a stable entity table plus separate evidence tables. The data model should not hide whether a field came from RES, a datos.gob.cl file, SII, procurement, IP, CMF, gazette, statistics or LEI.

• Entity core: normalized legal name, country, RUT/identifier where lawful, entity type, status, internal CompaniesData identifier and source confidence.
• RES evidence: RES URL, search route, dataset resource, creation/update dates, CVE/RUT fields and parser version.
• Open-data evidence: datos.gob.cl dataset URL, resource date, licence metadata, file format and transformation date.
• Tax checks: SII known-RUT status, response date, purpose flag and privacy limitation.
• Enrichment joins: ChileCompra supplier activity, INAPI owner names, CMF regulated status, Diario Oficial notices, INE geography/sector context 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 Chilean public-source evidence into a usable dataset. The value is normalization, deduplication, source provenance, identifier matching, 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 Chile. 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 Chilean business entities; the safe statement is that Chile combines strong RES/open-data evidence with separate enrichment and controlled-use layers.

Source Matrix

Source	Owner / authority	Access model	Reuse note	Main limitation
Registro de Empresas y Sociedades	Ministry of Economy / Registro de Empresas y Sociedades	portal / search / certificates / workflows	portal terms; reuse requires source-specific caution	Portal access is not the same as unrestricted bulk reuse or full coverage of every company route.
About the Registro de Empresas y Sociedades	Registro de Empresas y Sociedades	documentation	portal terms and official-publication caution	Documentation is context; it is not a bulk-data licence or API specification.
RES FAQ	Registro de Empresas y Sociedades	FAQ / documentation	portal terms	FAQ wording should not be stretched into a broad redistribution right.
RES advanced search	Registro de Empresas y Sociedades	advanced search / RUT, CVE, name and date filters	portal terms and privacy caution	Search workflow, not a full bulk export service.
RES dataset on datos.gob.cl	Chilean open-data portal / RES dataset owner	CKAN dataset / downloads	dataset licence and datos.gob.cl terms	Dataset periods, files and fields must be checked before claims about coverage.
datos.gob.cl reuse guide	datos.gob.cl	PDF guidance	open-data guidance and dataset-specific terms	Guide, not legal advice and not a licence for every external source.
ChileCompra API	ChileCompra	API / procurement data services	ChileCompra API terms, attribution and endpoint-specific conditions	Procurement-only coverage; not a legal company register or marketing list.
Mercado Publico	ChileCompra / Mercado Publico	portal / tenders / suppliers / workflows	portal and procurement notice terms	Procurement participation is a subset and may involve portal workflows.
SII third-party tax-status lookup	Servicio de Impuestos Internos	known-RUT lookup / web workflow	SII terms, purpose limitation and privacy caution	Not a bulk company database, contact source or general enrichment API.
INAPI	Instituto Nacional de Propiedad Industrial	search / services / publications	INAPI terms and dataset-specific conditions	IP data must be matched and is not proof of full legal entity status.
INAPI open data	INAPI	open-data portal / downloads	dataset-specific open-data terms	IP open data is an enrichment layer, not a company-register universe.
CMF regulated entities	Comision para el Mercado Financiero	directory / regulator publication	CMF terms and source-citation caution	Sector-specific and not comprehensive company coverage.
Diario Oficial	Diario Oficial de la Republica de Chile	search / official publications / documents	official-publication terms and document-specific caution	Document publication, not normalized company data.
Instituto Nacional de Estadisticas	INE Chile	statistics portal / publications / datasets	statistics/publication terms and attribution caution	Aggregate statistics do not validate individual companies.
GLEIF LEI API for Chile	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 Chile company coverage.

FAQ

Is Chile a strong country for open company data?

Yes. Chile is strong for Latin America because RES is public, datos.gob.cl exposes RES datasets, and procurement, IP, regulator, gazette, statistics and LEI layers can enrich company profiles.

Is there one official bulk dataset covering all Chilean companies?

No. The safe claim is that Chile 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 RES and the RES dataset on datos.gob.cl, then add ChileCompra/Mercado Publico, SII known-RUT checks, INAPI, CMF, Diario Oficial, INE and GLEIF as separate evidence layers.

Can SII data be used for bulk enrichment?

SII known-RUT status checks are useful for verification, but they should not be treated as a bulk company-profile database or marketing-contact source.

Can public Chile 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 Chile 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 de Empresas y Sociedades – Ministry of Economy / Registro de Empresas y Sociedades
• About the Registro de Empresas y Sociedades – Registro de Empresas y Sociedades
• RES FAQ – Registro de Empresas y Sociedades
• RES advanced search – Registro de Empresas y Sociedades
• RES dataset on datos.gob.cl – Chilean open-data portal / RES dataset owner
• datos.gob.cl reuse guide – datos.gob.cl
• ChileCompra API – ChileCompra
• Mercado Publico – ChileCompra / Mercado Publico
• SII third-party tax-status lookup – Servicio de Impuestos Internos
• INAPI – Instituto Nacional de Propiedad Industrial
• INAPI open data – INAPI
• CMF regulated entities – Comision para el Mercado Financiero
• Diario Oficial – Diario Oficial de la Republica de Chile
• Instituto Nacional de Estadisticas – INE Chile
• GLEIF LEI API for Chile – Global Legal Entity Identifier Foundation