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

Uruguay is a strong open procurement and supplier-data jurisdiction, but its legal company-register layer is controlled rather than a complete free bulk register. The practical official-source stack is DGR for legal registry services and certificates, ARCE/RUPE for supplier and procurement open data, the national open-data catalogue and open-data licence for reuse evidence, DGI for RUT and tax context, BCU for supervised financial entities, IMPO for legal-publication evidence and GLEIF for LEI cross-checks.

This refresh replaces the older thin Uruguay page with a deeper CompaniesData reference article. It separates DGR legal evidence from RUPE supplier data, DGI tax identifiers from legal registry status, OCDS contracting events from company master data, and public evidence from private marketing-contact use.

Key Takeaways

• Best open data angle: ARCE/RUPE and historical purchase datasets provide the strongest verified open-data evidence, including RUPE 2026 and OCDS-style procurement resources.
• Best legal registry layer: DGR is the legal registry authority, but access is through services, remote requests, certificates and controlled workflows.
• Best tax identifier layer: DGI RUT consultation validates tax context, not full company registration history.
• Best reuse evidence: the Catalogo Nacional and the Licencia de Datos Abiertos de Uruguay support open-data reuse where datasets adopt that licence.
• CompaniesData value: production use needs RUT/name normalization, source-date tracking, DGR/RUPE/DGI separation, supplier-scope flags and contact-data controls.

Editorial Methodology

This article follows the CompaniesData country-source method. Official sources are prioritized over private aggregators, and each source is classified by owner, authority, access model, reuse note, business use and limitation. Search, certificate, catalogue, dataset, resource, regulator and gazette routes are not merged into one evidence class.

Every final linked source was checked from this environment on 2026-06-09. Relevant official routes that timed out or produced SSL issues were held rather than linked as clean evidence. Source logos are decorative favicon cues only; the evidence remains the official URL, source owner, access model and reuse note.

Coverage, Access and Update-Risk Analysis

DGR boundary: DGR is the legal registry authority for registry certificates and Registro Nacional de Comercio information. It is a controlled service layer, not a verified unrestricted company bulk feed.

Remote-request boundary: remote requests and certificate workflows can require credentials, payments, limits or document-level context. They are appropriate for due diligence and proof, but not for blind bulk ingestion.

ARCE/RUPE boundary: RUPE 2026 is excellent for public-procurement supplier enrichment and includes supplier identification and status fields. It does not represent every company in Uruguay.

OCDS boundary: historical purchases are contracting events. Use them for buyer, supplier, procedure and award evidence, not as standalone proof of legal existence or current status.

DGI boundary: RUT consultation and DGI services validate tax context. They are not marketing-contact APIs and should be joined to legal evidence only with provenance and privacy flags.

Catalogue/licence boundary: Uruguay’s open-data licence is valuable, but each dataset still needs authority, licence, update cadence, personal-data and attribution review.

Regulator and gazette boundary: BCU and IMPO add high-confidence regulated-entity and legal-publication evidence, but they cover subsets and events rather than a complete company master.

Contact-data boundary: DGR, DGI, RUPE, ARCE, BCU, IMPO or GLEIF evidence does not create consent for cold email, phone lists, WhatsApp outreach or lead-list enrichment. Contact enrichment needs separate lawful basis, suppression, opt-out and privacy review.

Reuse Checklist

• Authority: store whether a field came from DGR, ARCE, RUPE, Catalogo Nacional, DGI, BCU, IMPO or GLEIF.
• Access route: separate legal registry certificate, remote request, CKAN dataset, CKAN resource, public supplier search, RUT consultation, regulator directory and gazette publication.
• Licence: preserve Licencia de DAG de Uruguay and dataset-specific metadata where catalogue datasets are used.
• Coverage: distinguish legal entities, suppliers, procurement participants, tax registrants, supervised financial entities, legal-publication subjects and LEI holders.
• Freshness: capture source access date, dataset update date, resource year, certificate issue date and transformation version.
• Privacy: flag natural-person, fiscal-address, representative, supplier-contact and taxpayer fields before reuse.
• Marketing: do not treat public registry, supplier, tax or gazette fields as outreach permission.
• Auditability: keep official-source fields and CompaniesData enrichment fields in separate columns.

Resource Pack

Source-by-Source Deep Dives

1. DGR portal

Authority: Direccion General de Registros. Type: official legal registry authority. Access model: portal / remote requests / certificates. Reuse position: DGR service terms and registry-publicity limits.

Primary legal-register authority route for registry services and certificates. In a production dataset, store the source URL, access date, source owner, original identifier, licence note and parser version before using this evidence in a Uruguay company profile.

Limitations and operating notes: Controlled service portal, not open company bulk data. Treat the source as a defined evidence layer, not proof of complete coverage, official endorsement, unrestricted redistribution or contact permission.

2. DGR Registro Nacional de Comercio criteria

Authority: DGR. Type: official registry guidance. Access model: guidance page. Reuse position: official guidance and service limits.

Explains Registro Nacional de Comercio coverage and information-request criteria. In a production dataset, store the source URL, access date, source owner, original identifier, licence note and parser version before using this evidence in a Uruguay company profile.

Limitations and operating notes: Guidance and request criteria are not a reusable bulk dataset. Treat the source as a defined evidence layer, not proof of complete coverage, official endorsement, unrestricted redistribution or contact permission.

3. DGR remote request consultations

Authority: DGR. Type: official registry service guidance. Access model: remote request / certificate consultation guidance. Reuse position: DGR service terms and evidentiary limits.

Document-level path for remote registry certificates and consultations. In a production dataset, store the source URL, access date, source owner, original identifier, licence note and parser version before using this evidence in a Uruguay company profile.

Limitations and operating notes: May require credentials, payment, limits or certificate workflow. Treat the source as a defined evidence layer, not proof of complete coverage, official endorsement, unrestricted redistribution or contact permission.

4. ARCE

Authority: Agencia Reguladora de Compras Estatales. Type: official procurement authority. Access model: portal / procurement systems. Reuse position: ARCE publication and procurement-data terms.

Authority context for public procurement, RUPE and open contracting data. In a production dataset, store the source URL, access date, source owner, original identifier, licence note and parser version before using this evidence in a Uruguay company profile.

Limitations and operating notes: Procurement authority, not legal registry authority. Treat the source as a defined evidence layer, not proof of complete coverage, official endorsement, unrestricted redistribution or contact permission.

5. ARCE open data

Authority: ARCE. Type: official procurement open-data hub. Access model: open-data pages / downloads. Reuse position: Uruguay open-data licence and dataset-specific notes.

Source page for RUPE 2026, historical purchases and other procurement datasets. In a production dataset, store the source URL, access date, source owner, original identifier, licence note and parser version before using this evidence in a Uruguay company profile.

Limitations and operating notes: Procurement/supplier layer only. Treat the source as a defined evidence layer, not proof of complete coverage, official endorsement, unrestricted redistribution or contact permission.

6. ARCE Open Contracting

Authority: ARCE. Type: official OCDS procurement documentation. Access model: OCDS documentation / downloads context. Reuse position: open contracting and Uruguay open-data terms.

Explains the OCDS model used for Uruguay public contracting history. In a production dataset, store the source URL, access date, source owner, original identifier, licence note and parser version before using this evidence in a Uruguay company profile.

Limitations and operating notes: OCDS data is public procurement history, not all companies. Treat the source as a defined evidence layer, not proof of complete coverage, official endorsement, unrestricted redistribution or contact permission.

7. ARCE catalogue organization

Authority: Catalogo Nacional de Datos Abiertos / ARCE. Type: official open-data catalogue view. Access model: CKAN catalogue / datasets. Reuse position: Licencia de DAG de Uruguay and dataset-specific metadata.

Catalogue-level discovery for ARCE procurement and supplier datasets. In a production dataset, store the source URL, access date, source owner, original identifier, licence note and parser version before using this evidence in a Uruguay company profile.

Limitations and operating notes: Catalogue search should be filtered and dataset metadata checked individually. Treat the source as a defined evidence layer, not proof of complete coverage, official endorsement, unrestricted redistribution or contact permission.

8. RUPE 2026 dataset

Authority: ARCE / RUPE. Type: official supplier open dataset. Access model: CKAN dataset / CSV resources. Reuse position: Licencia de DAG de Uruguay according to dataset metadata.

2026 monthly supplier dataset with supplier identification, denomination, fiscal address, locality, department and status fields. In a production dataset, store the source URL, access date, source owner, original identifier, licence note and parser version before using this evidence in a Uruguay company profile.

Limitations and operating notes: RUPE suppliers are a public-procurement subset, not all Uruguay legal entities. Treat the source as a defined evidence layer, not proof of complete coverage, official endorsement, unrestricted redistribution or contact permission.

9. RUPE public search

Authority: ARCE / RUPE. Type: official supplier-register search. Access model: public supplier search. Reuse position: RUPE consultation terms and supplier-data caution.

Manual verification route for public-procurement supplier status. In a production dataset, store the source URL, access date, source owner, original identifier, licence note and parser version before using this evidence in a Uruguay company profile.

Limitations and operating notes: Search workflow; not a general company register. Treat the source as a defined evidence layer, not proof of complete coverage, official endorsement, unrestricted redistribution or contact permission.

10. Historical purchases dataset

Authority: ARCE. Type: official procurement open dataset. Access model: CKAN dataset / OCDS resources. Reuse position: Licencia de DAG de Uruguay and OCDS terms.

Historical purchases and contracting evidence in OCDS-style form. In a production dataset, store the source URL, access date, source owner, original identifier, licence note and parser version before using this evidence in a Uruguay company profile.

Limitations and operating notes: Contracting events do not validate legal status by themselves. Treat the source as a defined evidence layer, not proof of complete coverage, official endorsement, unrestricted redistribution or contact permission.

11. Purchases 2025 resource

Authority: ARCE. Type: official procurement resource. Access model: JSON resource page. Reuse position: Licencia de DAG de Uruguay and dataset metadata.

Recent annual resource for public contracting activity and supplier matching. In a production dataset, store the source URL, access date, source owner, original identifier, licence note and parser version before using this evidence in a Uruguay company profile.

Limitations and operating notes: Annual resource is procurement-only and must be reconciled with RUPE/DGR/DGI. Treat the source as a defined evidence layer, not proof of complete coverage, official endorsement, unrestricted redistribution or contact permission.

12. Catalogo Nacional de Datos Abiertos

Authority: AGESIC / Uruguay open-data programme. Type: official open-data portal. Access model: CKAN catalogue. Reuse position: dataset-specific open-data licences.

National discovery layer for datasets beyond ARCE. In a production dataset, store the source URL, access date, source owner, original identifier, licence note and parser version before using this evidence in a Uruguay company profile.

Limitations and operating notes: Each dataset still needs authority, metadata and privacy review. Treat the source as a defined evidence layer, not proof of complete coverage, official endorsement, unrestricted redistribution or contact permission.

13. Uruguay open-data licence

Authority: Government of Uruguay / ARCE republication. Type: official open-data licence. Access model: licence text. Reuse position: Licencia de Datos Abiertos de Uruguay.

Reusable-rights baseline for open datasets that adopt the national licence. In a production dataset, store the source URL, access date, source owner, original identifier, licence note and parser version before using this evidence in a Uruguay company profile.

Limitations and operating notes: Licence does not override personal-data, dataset-specific or source-specific limits. Treat the source as a defined evidence layer, not proof of complete coverage, official endorsement, unrestricted redistribution or contact permission.

14. Catalog terms PDF

Authority: Catalogo Nacional de Datos Abiertos. Type: official catalogue terms. Access model: PDF terms. Reuse position: catalogue terms and associated open-data licence.

Terms context for catalogue reuse and attribution handling. In a production dataset, store the source URL, access date, source owner, original identifier, licence note and parser version before using this evidence in a Uruguay company profile.

Limitations and operating notes: Use the licence associated with each dataset and preserve attribution. Treat the source as a defined evidence layer, not proof of complete coverage, official endorsement, unrestricted redistribution or contact permission.

15. DGI RUT consultation

Authority: Direccion General Impositiva. Type: official tax identifier lookup. Access model: RUT consultation. Reuse position: DGI service terms, tax-data and privacy caution.

Known-RUT and taxpayer validation context. In a production dataset, store the source URL, access date, source owner, original identifier, licence note and parser version before using this evidence in a Uruguay company profile.

Limitations and operating notes: Tax lookup is not a legal-company register and is not marketing permission. Treat the source as a defined evidence layer, not proof of complete coverage, official endorsement, unrestricted redistribution or contact permission.

16. DGI online services list

Authority: DGI. Type: official tax service directory. Access model: service directory. Reuse position: DGI service terms and privacy limits.

Maps certificate, RUT and taxpayer service routes. In a production dataset, store the source URL, access date, source owner, original identifier, licence note and parser version before using this evidence in a Uruguay company profile.

Limitations and operating notes: Service descriptions, not a downloadable company dataset. Treat the source as a defined evidence layer, not proof of complete coverage, official endorsement, unrestricted redistribution or contact permission.

17. AGESIC DGI service context

Authority: AGESIC / DGI. Type: official interoperability/service context. Access model: service references. Reuse position: interoperability and service-specific terms.

Context for RUT/certificate services in public digital workflows. In a production dataset, store the source URL, access date, source owner, original identifier, licence note and parser version before using this evidence in a Uruguay company profile.

Limitations and operating notes: Interoperability context does not equal public bulk access. Treat the source as a defined evidence layer, not proof of complete coverage, official endorsement, unrestricted redistribution or contact permission.

18. BCU supervised banks list

Authority: Banco Central del Uruguay. Type: financial regulator directory. Access model: supervised-entity list. Reuse position: BCU publication terms and citation caution.

Financial-sector entity enrichment and supervised-status verification. In a production dataset, store the source URL, access date, source owner, original identifier, licence note and parser version before using this evidence in a Uruguay company profile.

Limitations and operating notes: Sector-specific subset only. Treat the source as a defined evidence layer, not proof of complete coverage, official endorsement, unrestricted redistribution or contact permission.

19. BCU Superintendencia de Servicios Financieros

Authority: Banco Central del Uruguay / SSF. Type: financial regulator authority. Access model: regulator portal. Reuse position: BCU publication terms and citation caution.

Authority context for supervised financial entities and sanctions/regulatory data. In a production dataset, store the source URL, access date, source owner, original identifier, licence note and parser version before using this evidence in a Uruguay company profile.

Limitations and operating notes: Regulator source, not a general business register. Treat the source as a defined evidence layer, not proof of complete coverage, official endorsement, unrestricted redistribution or contact permission.

20. IMPO Diario Oficial today

Authority: IMPO. Type: official gazette / legal publication. Access model: Diario Oficial daily publication route. Reuse position: official-publication terms and document-specific limits.

Corporate notices, legal publications, judicial notices and regulatory-event context. In a production dataset, store the source URL, access date, source owner, original identifier, licence note and parser version before using this evidence in a Uruguay company profile.

Limitations and operating notes: Gazette corpus, not normalized company master data. Treat the source as a defined evidence layer, not proof of complete coverage, official endorsement, unrestricted redistribution or contact permission.

21. GLEIF LEI API

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

LEI cross-checks for Uruguay entities in finance, KYB and compliance workflows. In a production dataset, store the source URL, access date, source owner, original identifier, licence note and parser version before using this evidence in a Uruguay company profile.

Limitations and operating notes: LEI coverage is a subset and not comprehensive Uruguay company coverage. Treat the source as a defined evidence layer, not proof of complete coverage, official endorsement, unrestricted redistribution or contact permission.

Practical Manual, API and Bulk Options

1. Use DGR for legal proof, not bulk ingestion

Start legal verification with DGR portal routes, Registro Nacional de Comercio criteria and remote certificate workflows. Use DGR when the customer needs legal proof, certificates, inscriptions or document-level evidence.

2. Use RUPE 2026 and ARCE datasets for open supplier data

RUPE 2026 and historical purchases are the strongest open data layers verified in this cycle. Capture dataset id, resource id, update date, licence and field dictionary before ingestion.

3. Use DGI for tax context

DGI RUT services are useful for known-identifier checks and taxpayer context. Keep RUT fields separate from DGR legal evidence and never treat DGI as a marketing-contact endpoint.

4. Add BCU, IMPO and GLEIF as enrichment

BCU identifies supervised financial entities, IMPO adds official legal-publication evidence and GLEIF provides LEI cross-checks. These layers improve confidence for subsets and events.

Held Source-Risk Findings

• gub.uy RNC tramite page: source-relevant but timed out from this node; DGR portal and DGR RNC guidance remain linked.
• INE business directory and demography routes: produced SSL/timeout behaviour and are held until a clean route is verified.
• Uruguay XXI exporter directory contact fields: useful market context but timed out here and includes contact-like fields requiring privacy review.
• Complete free DGR company bulk claim: no unrestricted DGR company bulk route was verified.
• DGI/RUT or RUPE as marketing-contact permission: blocked; use CompaniesData.cloud or CentraldeComunicacion.es for owned contact-data routes.

Missing Data Gaps

• Legal-company bulk: DGR is controlled and no complete free DGR bulk file was verified.
• Supplier scope: RUPE covers public-procurement suppliers, not every enterprise.
• Event scope: historical purchases and IMPO publications are events, not master records.
• Tax scope: DGI validates taxpayer context, not full legal registration history.
• Statistics gap: INE routes were held this cycle due access instability from this node.
• Contact-data gap: public-source fields must not be promoted into lead lists without separate legal basis.

Recommended Data Model

• Entity core: normalized legal name, RUT where lawful, CompaniesData id, country, registry context and source confidence.
• DGR evidence: certificate workflow, registry section, request/certificate date, act/document reference and controlled-access flag.
• RUPE/ARCE evidence: supplier id, denomination, status, locality, department, dataset id, resource id, procurement event ids and update date.
• DGI evidence: RUT validation, taxpayer context and privacy flags.
• Regulator/publication evidence: BCU supervised-entity records, IMPO notices and GLEIF LEI rows with separate provenance.
• Risk flags: dgr-controlled, rupe-supplier-only, dgi-tax-only, impo-event-only, bcu-regulator-subset, contact-use-blocked and manual-review-required.

How CompaniesData Adds Value

CompaniesData turns Uruguay’s official-source stack into a usable dataset by normalizing RUTs, legal names, supplier records, procurement events, regulator entries, gazette evidence and LEI identifiers. It keeps DGR legal evidence, DGI tax context and ARCE/RUPE open-data evidence separate so downstream users can see exactly which claim came from which authority.

For English and international users, CompaniesData.cloud is the preferred owned route: request a CompaniesData sample for Uruguay. 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 unsafe claim: this article can say Uruguay has strong ARCE/RUPE open supplier and procurement data plus controlled DGR/DGI legal and tax services. It should not imply that DGR, DGI or RUPE provides one complete, unrestricted, marketing-ready company bulk file.

Source Matrix

Source	Owner / authority	Access model	Reuse note	Main limitation
DGR portal	Direccion General de Registros	portal / remote requests / certificates	DGR service terms and registry-publicity limits	Controlled service portal, not open company bulk data.
DGR Registro Nacional de Comercio criteria	DGR	guidance page	official guidance and service limits	Guidance and request criteria are not a reusable bulk dataset.
DGR remote request consultations	DGR	remote request / certificate consultation guidance	DGR service terms and evidentiary limits	May require credentials, payment, limits or certificate workflow.
ARCE	Agencia Reguladora de Compras Estatales	portal / procurement systems	ARCE publication and procurement-data terms	Procurement authority, not legal registry authority.
ARCE open data	ARCE	open-data pages / downloads	Uruguay open-data licence and dataset-specific notes	Procurement/supplier layer only.
ARCE Open Contracting	ARCE	OCDS documentation / downloads context	open contracting and Uruguay open-data terms	OCDS data is public procurement history, not all companies.
ARCE catalogue organization	Catalogo Nacional de Datos Abiertos / ARCE	CKAN catalogue / datasets	Licencia de DAG de Uruguay and dataset-specific metadata	Catalogue search should be filtered and dataset metadata checked individually.
RUPE 2026 dataset	ARCE / RUPE	CKAN dataset / CSV resources	Licencia de DAG de Uruguay according to dataset metadata	RUPE suppliers are a public-procurement subset, not all Uruguay legal entities.
RUPE public search	ARCE / RUPE	public supplier search	RUPE consultation terms and supplier-data caution	Search workflow; not a general company register.
Historical purchases dataset	ARCE	CKAN dataset / OCDS resources	Licencia de DAG de Uruguay and OCDS terms	Contracting events do not validate legal status by themselves.
Purchases 2025 resource	ARCE	JSON resource page	Licencia de DAG de Uruguay and dataset metadata	Annual resource is procurement-only and must be reconciled with RUPE/DGR/DGI.
Catalogo Nacional de Datos Abiertos	AGESIC / Uruguay open-data programme	CKAN catalogue	dataset-specific open-data licences	Each dataset still needs authority, metadata and privacy review.
Uruguay open-data licence	Government of Uruguay / ARCE republication	licence text	Licencia de Datos Abiertos de Uruguay	Licence does not override personal-data, dataset-specific or source-specific limits.
Catalog terms PDF	Catalogo Nacional de Datos Abiertos	PDF terms	catalogue terms and associated open-data licence	Use the licence associated with each dataset and preserve attribution.
DGI RUT consultation	Direccion General Impositiva	RUT consultation	DGI service terms, tax-data and privacy caution	Tax lookup is not a legal-company register and is not marketing permission.
DGI online services list	DGI	service directory	DGI service terms and privacy limits	Service descriptions, not a downloadable company dataset.
AGESIC DGI service context	AGESIC / DGI	service references	interoperability and service-specific terms	Interoperability context does not equal public bulk access.
BCU supervised banks list	Banco Central del Uruguay	supervised-entity list	BCU publication terms and citation caution	Sector-specific subset only.
BCU Superintendencia de Servicios Financieros	Banco Central del Uruguay / SSF	regulator portal	BCU publication terms and citation caution	Regulator source, not a general business register.
IMPO Diario Oficial today	IMPO	Diario Oficial daily publication route	official-publication terms and document-specific limits	Gazette corpus, not normalized company master data.
GLEIF LEI API	Global Legal Entity Identifier Foundation	API / open LEI data	GLEIF API and open-data terms	LEI coverage is a subset and not comprehensive Uruguay company coverage.

FAQ

Is Uruguay good for open company data?

Uruguay is especially strong for open procurement and supplier data through ARCE/RUPE. Legal registry evidence is available through DGR services, but not as a verified unrestricted company bulk file.

Can I download Uruguay company data in bulk?

You can download strong supplier and procurement datasets from ARCE/RUPE and historical purchases. That is not the same as a complete DGR legal-company bulk register.

Does RUPE cover every company?

No. RUPE covers public-procurement suppliers and supplier status. It is highly useful but should be flagged as procurement-supplier coverage.

Can DGI RUT data replace DGR?

No. DGI is the tax authority. Use it for RUT/tax context while preserving DGR as legal-register evidence.

Is IMPO a company register?

No. IMPO is a legal-publication and Diario Oficial layer. Use it for corporate notices, legal events and publication evidence.

Can public Uruguay data be used for cold email?

Not automatically. Public registry, supplier, tax and gazette evidence is not consent for marketing outreach.

Why use CompaniesData?

CompaniesData adds normalization, deduplication, source provenance, update tracking, risk flags and delivery formats across DGR, DGI, ARCE/RUPE, BCU, IMPO and GLEIF.

Official Sources

• DGR portal – Direccion General de Registros
• DGR Registro Nacional de Comercio criteria – DGR
• DGR remote request consultations – DGR
• ARCE – Agencia Reguladora de Compras Estatales
• ARCE open data – ARCE
• ARCE Open Contracting – ARCE
• ARCE catalogue organization – Catalogo Nacional de Datos Abiertos / ARCE
• RUPE 2026 dataset – ARCE / RUPE
• RUPE public search – ARCE / RUPE
• Historical purchases dataset – ARCE
• Purchases 2025 resource – ARCE
• Catalogo Nacional de Datos Abiertos – AGESIC / Uruguay open-data programme
• Uruguay open-data licence – Government of Uruguay / ARCE republication
• Catalog terms PDF – Catalogo Nacional de Datos Abiertos
• DGI RUT consultation – Direccion General Impositiva
• DGI online services list – DGI
• AGESIC DGI service context – AGESIC / DGI
• BCU supervised banks list – Banco Central del Uruguay
• BCU Superintendencia de Servicios Financieros – Banco Central del Uruguay / SSF
• IMPO Diario Oficial today – IMPO
• GLEIF LEI API – Global Legal Entity Identifier Foundation