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

Paraguay is one of the stronger Latin American jurisdictions for open company-data source mapping because it combines company-opening services, legal-structure and beneficial-ownership portals, national open-data infrastructure, procurement open data, tax-authority context, intellectual-property services, official statistics and LEI records. The source landscape is commercially useful, but it also carries higher privacy risk than a simple registry-only page because beneficial owners, socios, directivos and taxpayer identifiers may involve natural persons.

This 2026 refresh converts the older CompaniesData Paraguay page into a deep reference article. The clean source stack includes SUACE, DRFS, Abogacia open data, datos.gov.py, DNCP procurement open data, DNIT, DINAPI, Joaju, INE and GLEIF. The Banco Central del Paraguay supervised-entity route remains held after automated QA saw challenge behavior, so it is source-mapped but not linked as clean evidence here.

Key Takeaways

• Best starting point: use SUACE and DRFS to understand company formation, legal structures and beneficial-ownership workflows.
• Strongest structured layer: DNCP and GLEIF provide the clearest API/open-data style routes, but they cover procurement and LEI subsets, not every company.
• Privacy caution: beneficial owners, socios, directivos, RUC/taxpayer fields and supplier contacts require lawful-use, minimization and retention controls.
• Bulk/API caution: no complete free official commercial-register bulk API was verified in this cycle.
• CompaniesData role: normalization adds value by reconciling legal-structure evidence, beneficial-ownership privacy flags, procurement events, tax identifiers, IP records, statistics, LEIs and source provenance.

Editorial Methodology

This article follows the CompaniesData source-first editorial standard. Official sources are preferred over private aggregators. Each source is classified by authority, access model, reuse note, limitation and practical business value. The 2026-06-10 source recheck found 15 stable public links, 1 held route, 0 hard 404/410 failures and 1 soft or controlled-access warning.

The methodology separates source layers. A company-opening portal is not a company master table. A beneficial-ownership dataset is not a marketing list. A procurement supplier record is not the full company universe. A tax portal is not outreach permission. A trademark record is partial enrichment. A LEI record is structured but optional. These distinctions make the resulting dataset auditable and reduce overclaiming.

The live Paraguay page is crawlable and indexable, but the observed word estimate is 1887 words, below the current 2,400-word minimum. This article expands the page into a deep reference while keeping beneficial-ownership privacy, BCP source-risk and no-bulk-register cautions visible.

Coverage, Access and Update-Risk Analysis

Formation and legal-structure coverage: SUACE and DRFS explain how companies and legal structures enter formal workflows. They are strong context and service layers, but should not be overdescribed as an unrestricted commercial-register bulk file. Store workflow source, access date, query route and evidence type separately from normalized entity attributes.

Beneficial ownership: Paraguay’s beneficial-ownership and legal-structure open-data routes are valuable for KYB, ownership-chain analysis and compliance screening. They also create the highest privacy risk in the Paraguay stack. Beneficial-owner, socio, director or representative fields should have privacy flags, minimization rules, role-based access and purpose restrictions.

Open data and procurement: datos.gov.py and DNCP provide strong reuse context. DNCP Datos Abiertos can support structured procurement analysis, supplier intelligence and public-contract enrichment. Procurement is still a subset: companies that do not participate in public tenders may not appear.

Tax, IP, statistics and LEI: DNIT provides RUC/tax context, DINAPI and Joaju provide IP workflow context, INE provides aggregate market context and GLEIF provides structured global identifiers for entities with LEIs. These sources improve matching and analysis, but none replaces a complete legal-entity source of truth.

Held regulator route: Banco Central del Paraguay supervised-entity pages should be useful for financial-sector enrichment, but this automated run received challenge behavior. Keep BCP source-mapped and add it only after browser/crawl QA confirms real content for normal and bot-like profiles.

Reuse Checklist

• Source owner: record whether each observation came from SUACE, DRFS, Abogacia open data, datos.gov.py, DNCP, DNIT, DINAPI, INE or GLEIF.
• Access model: separate service portal, login workflow, public consultation, DKAN metadata, procurement API/download, tax portal, IP services, statistics and LEI API records.
• Licence and terms: preserve dataset-level Paraguay public-information licence notes, DNCP terms, GLEIF attribution and no-endorsement conditions.
• Update date: store access date, dataset publication date and event date where available. Procurement and legal-structure data may update on different schedules.
• Privacy flag: mark beneficial-owner, socio, directivo, representative, taxpayer, address, email and phone fields as privacy-sensitive or contact-sensitive.
• Marketing boundary: official access to company, ownership, supplier, RUC, IP or LEI data is not sales-prospecting permission.
• Completeness claim: do not claim a complete free commercial-register bulk API unless a specific official register dataset proves it.
• Audit trail: retain exact URL, query route, dataset resource, timestamp, transformation path and reviewer status for each normalized record.

Resource Pack

Source-by-Source Deep Dives

1. SUACE

Authority: Sistema Unificado de Apertura y Cierre de Empresas, Paraguay. Type: official company opening and closing service. Access model: official services portal. Reuse note: official portal terms and service rules. Business use: Company formation, formalization and business-opening workflow context.

SUACE is the company-opening and formalization workflow layer. It is useful for explaining how businesses are opened, changed or closed in a unified service environment. It should be treated as official process evidence, not as proof of complete bulk registry availability. Store SUACE observations as workflow metadata and route context, then link them to registry or open-data evidence only when a specific official record supports the match.

Limitation: Service portal, not a complete reusable company-register bulk dataset.

2. Direccion General de Personas y Estructuras Juridicas y Beneficiarios Finales

Authority: Abogacia del Tesoro / Direccion General de Personas y Estructuras Juridicas y Beneficiarios Finales. Type: official persons, legal structures and beneficial ownership portal. Access model: portal / login workflow. Reuse note: official portal terms, privacy and beneficial-ownership rules. Business use: Core legal-structures and beneficial-ownership workflow context.

The DRFS layer is commercially valuable and legally sensitive because it covers persons, legal structures and beneficial-ownership context. It can support KYB, ownership-chain analysis and compliance review, but natural-person fields such as beneficial owners, socios, directivos or representatives require minimization, purpose limitation, role-based access and retention controls. It is not a marketing-contact source.

Limitation: Login/account workflow; natural-person fields require privacy and lawful-use controls.

3. DRFS document consultation

Authority: Abogacia del Tesoro / DRFS. Type: official document/tramite consultation. Access model: public consultation form. Reuse note: official portal terms and privacy rules. Business use: Follow-up and document-consultation route for company/legal-structure procedures.

The DRFS document-consultation route helps users follow filings, procedures or evidence documents. It is a practical verification route, not a bulk data API. Capture procedure identifiers, query date and source URL, and keep these observations separate from normalized entity attributes until a reviewer confirms the match.

Limitation: Document workflow, not an unrestricted company master API.

4. Datos Abiertos Abogacia del Tesoro

Authority: Abogacia del Tesoro / MEF. Type: official open-data portal for legal structures and beneficial owners. Access model: open-data portal. Reuse note: Paraguay public information open-data licence and dataset terms. Business use: Open-data route for beneficial owners, partners and directors of registered companies.

The Abogacia open-data layer is one of Paraguay's strongest differentiators, because it gives structured public-data context around legal structures and beneficial ownership. That strength increases privacy responsibility. Field-level review is required before production use, and downstream products should avoid exposing or repurposing natural-person data for outreach.

Limitation: High privacy sensitivity; not marketing-contact permission.

5. Datos.gov.py DRFS beneficial ownership dataset page

Authority: Datos.gov.py / MEF / DRFS. Type: official metadata page. Access model: DKAN metadata and resource page. Reuse note: Licencia de Uso de la Informacion Publica del Gobierno Paraguayo. Business use: Dataset metadata, publication date, licence and access context for DRFS open data.

The DRFS layer is commercially valuable and legally sensitive because it covers persons, legal structures and beneficial-ownership context. It can support KYB, ownership-chain analysis and compliance review, but natural-person fields such as beneficial owners, socios, directivos or representatives require minimization, purpose limitation, role-based access and retention controls. It is not a marketing-contact source.

Limitation: Metadata page; dataset fields involving people need minimization and lawful-use review.

6. Datos.gov.py

Authority: Government of Paraguay. Type: national open-data portal. Access model: DKAN open-data catalogue. Reuse note: dataset-specific Paraguay open-data licence. Business use: Government open-data discovery and reuse context.

Datos.gov.py is the national catalogue layer. It is useful for dataset discovery, metadata, licences and update cadence. It should not be treated as a source of a company universe by itself; every dataset needs its own field review, licence check and freshness test before reuse claims.

Limitation: Dataset-by-dataset licence and freshness review required.

7. Datos.gov.py DNCP open-data page

Authority: Datos.gov.py / DNCP. Type: official procurement open-data metadata. Access model: open-data portal metadata. Reuse note: Paraguay public information open-data licence and DNCP terms. Business use: Confirms the official public-procurement open-data portal and API availability.

The DNCP open-data metadata page confirms the official procurement open-data ecosystem. It is useful for reuse and API claims around procurement, but procurement data is a subset. A company that never sells to the public sector may never appear in this layer.

Limitation: Procurement participants are a subset, not the whole company universe.

8. DNCP public procurement portal

Authority: Direccion Nacional de Contrataciones Publicas. Type: official procurement portal. Access model: public procurement portal. Reuse note: DNCP portal and procurement publication rules. Business use: Tender, supplier and award enrichment.

The DNCP public procurement portal is the tender and supplier evidence layer. It can enrich company profiles with buyer agencies, process references, awards, supplier names and public-sector activity. Store it as event evidence linked back to a normalized legal entity with confidence scoring.

Limitation: Public-sector supplier universe only.

9. DNCP Datos Abiertos

Authority: Direccion Nacional de Contrataciones Publicas. Type: official procurement open-data/API route. Access model: open data / API / downloads. Reuse note: DNCP open-data and reuse terms. Business use: Structured procurement data for tenders, awards, suppliers and contracting processes.

DNCP Datos Abiertos is the strongest structured data route in the Paraguay stack. It supports API/download-style procurement analysis and can power supplier intelligence. It still should not be described as a complete commercial register because it only reflects procurement activity.

Limitation: Procurement subset; not an economy-wide company register.

10. DNIT portal

Authority: Direccion Nacional de Ingresos Tributarios. Type: tax authority / RUC context. Access model: official tax portal. Reuse note: tax privacy and service rules. Business use: RUC/taxpayer identifier context for lawful verification workflows.

DNIT provides tax-authority and RUC context. Tax identifiers are valuable for matching and validation, but taxpayer information is not contact permission. Keep tax identifiers in a controlled identifier table, use lawful-basis notes and avoid exporting them into marketing workflows without a separate legal basis.

Limitation: Tax identifiers and taxpayer data are not marketing-contact permission.

11. DINAPI

Authority: Direccion Nacional de Propiedad Intelectual. Type: official intellectual-property office. Access model: IP portal. Reuse note: DINAPI website and IP-service terms. Business use: Trademark, patent and rights-owner enrichment.

DINAPI and Joaju add intellectual-property context. Trademark, patent and filing records can help match companies to brands and rights, especially when trading names differ from legal names. Coverage is partial and should be stored as an IP enrichment table rather than a registry master.

Limitation: IP coverage is partial and does not represent all companies.

12. DINAPI marcas

Authority: Direccion Nacional de Propiedad Intelectual. Type: official trademark information. Access model: trademark services and guidance. Reuse note: DINAPI website and IP-service terms. Business use: Brand and trademark workflow context for entity enrichment.

DINAPI and Joaju add intellectual-property context. Trademark, patent and filing records can help match companies to brands and rights, especially when trading names differ from legal names. Coverage is partial and should be stored as an IP enrichment table rather than a registry master.

Limitation: Guidance/services layer; not a bulk company source.

13. Joaju DINAPI

Authority: Direccion Nacional de Propiedad Intelectual. Type: official DINAPI electronic services portal. Access model: electronic IP services. Reuse note: DINAPI service terms. Business use: IP filing/search workflow context.

DINAPI and Joaju add intellectual-property context. Trademark, patent and filing records can help match companies to brands and rights, especially when trading names differ from legal names. Coverage is partial and should be stored as an IP enrichment table rather than a registry master.

Limitation: Service workflow, not complete company-data coverage.

14. Instituto Nacional de Estadistica Paraguay

Authority: Instituto Nacional de Estadistica. Type: official statistics office. Access model: statistics / publications. Reuse note: INE website terms. Business use: Business, demographic and economic context.

This source is useful as one evidence layer, but its access model, scope and limitation must travel with the record. Do not turn a service page, dataset catalogue or sector register into a complete company universe.

Limitation: Aggregate/statistical layer, not legal-entity master data.

15. GLEIF LEI records for Paraguay

Authority: Global Legal Entity Identifier Foundation. Type: LEI API. Access model: public API. Reuse note: GLEIF open data licence with attribution and no-endorsement conditions. Business use: Structured cross-border identifier enrichment for Paraguayan entities with LEIs.

GLEIF provides the structured LEI API layer. It is useful for cross-border entity matching and financial-sector identity. Coverage is partial and skewed toward entities that need LEIs, so it should enrich rather than replace official Paraguay sources. Preserve attribution and no-endorsement conditions.

Limitation: Partial coverage, skewed toward financial and cross-border entities.

Practical Manual, API and Bulk Options

Manual lookup workflow

For a single entity, start with the formalization and legal-structure context from SUACE and DRFS. Check whether there is relevant document consultation evidence, then enrich with DNCP supplier or award data, DNIT tax context, DINAPI IP records, INE market context and GLEIF identifiers where applicable. Keep every layer separate until matching confidence is clear.

API and structured-data workflow

DNCP Datos Abiertos and GLEIF are the strongest structured routes in this map. They are appropriate for API-style ingestion where terms and rate limits are respected. Abogacia and datos.gov.py resources can support structured review, but beneficial-owner and legal-structure fields need field-level privacy classification before production use.

Bulk-data workflow

This cycle did not verify a complete free official commercial-register bulk API. A safe bulk workflow therefore depends on official reusable datasets with clear terms, licensed access, or CompaniesData normalization with provenance and QA controls. Bulk outputs should separate identity records, beneficial-ownership records, procurement events, tax identifiers, IP records and LEI matches.

Contact-data workflow

For international audiences, the owned route for normalized company-data work is CompaniesData.cloud. For Spanish-speaking or Hispanic contact-data workflows, the owned route is CentraldeComunicacion.es. Beneficial-owner, socio, director, supplier, RUC, email or phone data requires a separate lawful basis and suppression process. Paraguay official data is not sales-prospecting permission.

Held Source-Risk Findings

Current result: the BCP supervised-entity route is source-mapped but not linked as clean evidence in this article because automated QA received access-control/challenge behavior. If browser QA later clears it, it can be added as a financial-regulator layer.

• Banco Central del Paraguay supervised entities: held after live-check result 403. Reason: Bot/access challenge marker detected in response body..

Source Matrix

Source	Owner / authority	Access model	Reuse note	Main limitation
SUACE	Sistema Unificado de Apertura y Cierre de Empresas, Paraguay	official services portal	official portal terms and service rules	Service portal, not a complete reusable company-register bulk dataset.
Direccion General de Personas y Estructuras Juridicas y Beneficiarios Finales	Abogacia del Tesoro / Direccion General de Personas y Estructuras Juridicas y Beneficiarios Finales	portal / login workflow	official portal terms, privacy and beneficial-ownership rules	Login/account workflow; natural-person fields require privacy and lawful-use controls.
DRFS document consultation	Abogacia del Tesoro / DRFS	public consultation form	official portal terms and privacy rules	Document workflow, not an unrestricted company master API.
Datos Abiertos Abogacia del Tesoro	Abogacia del Tesoro / MEF	open-data portal	Paraguay public information open-data licence and dataset terms	High privacy sensitivity; not marketing-contact permission.
Datos.gov.py DRFS beneficial ownership dataset page	Datos.gov.py / MEF / DRFS	DKAN metadata and resource page	Licencia de Uso de la Informacion Publica del Gobierno Paraguayo	Metadata page; dataset fields involving people need minimization and lawful-use review.
Datos.gov.py	Government of Paraguay	DKAN open-data catalogue	dataset-specific Paraguay open-data licence	Dataset-by-dataset licence and freshness review required.
Datos.gov.py DNCP open-data page	Datos.gov.py / DNCP	open-data portal metadata	Paraguay public information open-data licence and DNCP terms	Procurement participants are a subset, not the whole company universe.
DNCP public procurement portal	Direccion Nacional de Contrataciones Publicas	public procurement portal	DNCP portal and procurement publication rules	Public-sector supplier universe only.
DNCP Datos Abiertos	Direccion Nacional de Contrataciones Publicas	open data / API / downloads	DNCP open-data and reuse terms	Procurement subset; not an economy-wide company register.
DNIT portal	Direccion Nacional de Ingresos Tributarios	official tax portal	tax privacy and service rules	Tax identifiers and taxpayer data are not marketing-contact permission.
DINAPI	Direccion Nacional de Propiedad Intelectual	IP portal	DINAPI website and IP-service terms	IP coverage is partial and does not represent all companies.
DINAPI marcas	Direccion Nacional de Propiedad Intelectual	trademark services and guidance	DINAPI website and IP-service terms	Guidance/services layer; not a bulk company source.
Joaju DINAPI	Direccion Nacional de Propiedad Intelectual	electronic IP services	DINAPI service terms	Service workflow, not complete company-data coverage.
Instituto Nacional de Estadistica Paraguay	Instituto Nacional de Estadistica	statistics / publications	INE website terms	Aggregate/statistical layer, not legal-entity master data.
GLEIF LEI records for Paraguay	Global Legal Entity Identifier Foundation	public API	GLEIF open data licence with attribution and no-endorsement conditions	Partial coverage, skewed toward financial and cross-border entities.

Missing-Data Gaps

• No complete commercial-register bulk confirmed: strong service and open-data routes exist, but no complete free register master API was verified.
• BCP held: the supervised-entity regulator route remains held until browser/crawl QA clears the challenge behavior.
• Beneficial-ownership sensitivity: field-level review is required before using owner, socio, directivo or representative fields in products.
• Sector and activity bias: procurement, IP and LEI data cover subsets and can underrepresent small, informal or non-procurement companies.
• Court/insolvency gap: no court or insolvency source was cleared as a reusable company-data layer in this cycle.

Recommended Data Model

A practical Paraguay model should use a layered schema. The entity table should hold CompaniesData ID, normalized legal name, country, source confidence, source owner, access date and core identifiers where lawfully reusable. A legal-structure table should hold DRFS observations, document references and beneficial-ownership workflow metadata. A privacy table should classify natural-person fields and permitted uses.

Separate enrichment tables should store DNCP procurement events, DNIT/RUC context, DINAPI IP records, INE context and GLEIF matches. Each row needs source URL, dataset or query route, event date, collection date, reuse note, privacy flag and match confidence. This structure lets users use Paraguay data for KYB, market research and supplier intelligence without turning official data into unsupported contact lists.

CompaniesData Normalization and Enrichment Value

CompaniesData.cloud adds value because Paraguay’s sources are strong but fragmented. A user can find official portals, but still has to normalize names, separate ownership from procurement, handle privacy restrictions, reconcile supplier records, interpret IP filings, preserve open-data licences and avoid overclaiming bulk register availability.

CompaniesData can turn this source map into an auditable dataset by deduplicating names, preserving provenance, separating identity from beneficial ownership, tagging natural-person fields, linking procurement events, normalizing identifiers, flagging held routes and delivering analysis-ready exports. That matters for KYB triage, supplier intelligence, CRM enrichment, market sizing and cross-border entity matching.

The highest-value Paraguay enrichment comes from combining SUACE/DRFS context, Abogacia open data, DNCP procurement records, DNIT tax context, DINAPI IP evidence, INE statistics and GLEIF LEIs. The highest-risk layer is beneficial-ownership and contact-adjacent information, which must stay behind lawful-use controls.

Request a CompaniesData sample for Paraguay if you need normalized records rather than a manual list of portals.

FAQ

What is the best starting point for Paraguay company data?

Start with SUACE for formalization context and DRFS for legal-structure and beneficial-ownership context.

Does Paraguay have useful open company data?

Yes, Paraguay has strong open-data and procurement routes, especially around Abogacia open data, datos.gov.py and DNCP.

Does Paraguay provide a complete free commercial-register bulk API?

This cycle did not verify a complete free official commercial-register master API.

What does DRFS add?

DRFS adds legal-structure, document-consultation and beneficial-ownership workflow context.

Can beneficial-owner data be used for marketing?

No. Beneficial owners, socios, directivos and representatives require lawful-use controls and are not contact-list permission.

What does datos.abogacia.gov.py add?

It adds official open-data context for legal structures and beneficial ownership, subject to privacy and field-level review.

What does DNCP add?

DNCP adds procurement, supplier and award data. It is useful supplier intelligence, not a full company universe.

Is DNCP API-style data useful?

Yes. DNCP Datos Abiertos is one of the strongest structured routes, but it remains procurement-specific.

What does DNIT add?

DNIT adds tax and RUC context. Tax identifiers need lawful-use controls and should not be treated as marketing permission.

What does DINAPI add?

DINAPI adds trademark, patent and IP workflow context. It helps brand matching but covers only entities with IP activity.

Why is BCP held?

The supervised-entity route returned challenge behavior in automated QA. It should be browser-verified before clean publication use.

What does INE add?

INE adds aggregate statistics and market context, not individual company status.

What does GLEIF add?

GLEIF adds structured LEI records for Paraguayan entities that have Legal Entity Identifiers.

Can public Paraguay company data be reused commercially?

Potentially, within source-specific terms, privacy rules and field restrictions. Public access is not unrestricted bulk reuse.

Why use CompaniesData instead of manual collection?

CompaniesData adds normalization, provenance, deduplication, privacy flags, confidence scoring and delivery formats.

Official Sources

• SUACE – Sistema Unificado de Apertura y Cierre de Empresas, Paraguay
• Direccion General de Personas y Estructuras Juridicas y Beneficiarios Finales – Abogacia del Tesoro / Direccion General de Personas y Estructuras Juridicas y Beneficiarios Finales
• DRFS document consultation – Abogacia del Tesoro / DRFS
• Datos Abiertos Abogacia del Tesoro – Abogacia del Tesoro / MEF
• Datos.gov.py DRFS beneficial ownership dataset page – Datos.gov.py / MEF / DRFS
• Datos.gov.py – Government of Paraguay
• Datos.gov.py DNCP open-data page – Datos.gov.py / DNCP
• DNCP public procurement portal – Direccion Nacional de Contrataciones Publicas
• DNCP Datos Abiertos – Direccion Nacional de Contrataciones Publicas
• DNIT portal – Direccion Nacional de Ingresos Tributarios
• DINAPI – Direccion Nacional de Propiedad Intelectual
• DINAPI marcas – Direccion Nacional de Propiedad Intelectual
• Joaju DINAPI – Direccion Nacional de Propiedad Intelectual
• Instituto Nacional de Estadistica Paraguay – Instituto Nacional de Estadistica
• GLEIF LEI records for Paraguay – Global Legal Entity Identifier Foundation