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

Moldova has a serious official company-data ecosystem, but it should not be reduced to a simple list of companies. The right way to evaluate Moldova is to start with the official register, then add open-data, statistics, procurement, intellectual-property and regulator layers.

The strongest route is Public Services Agency legal-entity services, RSUD extract and e-services routes, the Moldova open-data portal, taxpayer lookup, tender portal, statistics, AGEPI and National Bank sources as separate official layers. That makes Moldova a ASP and RSUD-led official source guide with authorized-access, beneficial-owner, Romanian-language and no-complete-bulk caveats, but it does not remove the usual reuse checks: dataset terms, attribution, no-endorsement language, privacy, marketing-law boundaries and source freshness.

This guide maps the main official sources for company data in Moldova, explains what each source can and cannot do, and shows where a normalized CompaniesData-style dataset adds value.

The deeper question is not whether a source exists. The useful question is which source can be trusted for identity, which one proves events or filings, which one is usable at scale, which one is only a manual service, and which fields become legally sensitive once the data is reused commercially.

Quick Answer

Moldova is publishable as a deep refresh because the Public Services Agency is the official legal-entity registration route, RSUD services and e-services support public verification, and date.gov.md, tax, procurement, statistics, IP and central-bank sources provide useful enrichment. The safe claim is not that Moldova exposes a complete free company-register bulk file. The safe claim is that Moldova has a strong official source stack where public search, RSUD extracts, authorized data exchange, open-data catalogues and privacy-sensitive fields must be separated.

For practical work, the most useful source stack is: Public Services Agency legal entities, Moldova public-services ASP page, ASP electronic bulletin, Moldova open-data portal, Moldova taxpayer lookup, Moldova tender portal.

The safe editorial answer is this: Moldova has strong public and official business-data sources, but public data is not automatically bulk-downloadable, marketing-ready or free of personal-data constraints.

A serious Moldova dataset normally needs at least four layers: the legal register for entity identity, official publications or filings for change events, public procurement/regulator/IP/statistical sources for enrichment, and a separate compliance layer for privacy, contact-data use, suppression and lawful outreach.

Key Takeaways

• Best starting point: Public Services Agency legal-entity services, RSUD extract and e-services routes, the Moldova open-data portal, taxpayer lookup, tender portal, statistics, AGEPI and National Bank sources as separate official layers.
• Core source stack: Public Services Agency legal entities, Moldova public-services ASP page, ASP electronic bulletin, Moldova open-data portal, Moldova taxpayer lookup, Moldova tender portal.
• Reuse rule: public visibility is not the same as bulk reuse, resale permission or marketing-contact permission.
• Buyer value: the useful dataset is the normalized, deduplicated and source-auditable version, not a raw list of portal links.
• Commercial separation: official company records, enriched company profiles and business contact data should remain separate layers with separate compliance notes.

Editorial Methodology

This article uses an official-source-first method. Sources are included when they help verify legal existence, public filings, procurement activity, taxpayer or identifier context, IP ownership, regulated status, statistics or lawful compliance context. Commercial providers and contact-data products are not used as authority for official reuse rights.

• Prefer the national registry, company house, gazette or official business-registration authority before any secondary source.
• Classify access as search, API, bulk download, paid extract, subscription, document workflow, data catalogue or unclear/manual access.
• Separate legal-entity data from establishment statistics, procurement suppliers, listed-company disclosures, tax identifiers and private contact data.
• Treat beneficial owners, officers, addresses, signatures, insolvency notices and sole-trader records as privacy-sensitive unless the source and law clearly support reuse.
• Hold or omit unstable source links when live QA shows 403, 429, 5xx, DNS, TLS or timeout behaviour that would create broken-link noise.

What Counts as Company Data in Moldova?

In Moldova, these layers should not be collapsed into one undifferentiated database. A registry result may prove legal existence, a procurement notice may prove public-sector activity, an IP record may prove brand or invention ownership, and a regulator list may prove supervision. Those are different facts with different update cycles, identifiers and reuse boundaries.

Reuse Rights and Compliance

Across jurisdictions, public-sector-information and open-data policies can support reuse of public-sector data, and high-value dataset rules increasingly treat company and company-ownership data as important public information. In practice, Moldova's actual reuse position still depends on each source, endpoint, licence and access method.

• Cite official sources and preserve update dates where the source provides them.
• Do not imply that a derived dataset is endorsed by the registry or public authority.
• Do not mix public register data with marketing-contact permission.
• Check whether API, bulk download, paid extract and web-search access have different terms.
• Treat officers, beneficial owners and natural-person data as GDPR-sensitive where applicable.

publishable as an ASP/RSUD-led official source map with actelocale held, authorized-access, beneficial-owner, language and no-complete-bulk caveats

Coverage, Access and Update Risk

The most common mistake in Moldova company-data work is to confuse visibility with completeness. A public search screen can be authoritative for one entity lookup without being suitable for bulk ingestion. A downloadable dataset can be reusable for a defined snapshot while still excluding filings, documents, directors, inactive entities or historical changes.

• Coverage: identify whether the source covers companies, business names, branches, non-profits, sole traders, listed issuers, regulated entities or only a sector subset.
• Freshness: preserve the source update date and avoid mixing live portal results with old downloaded files without version labels.
• Identifiers: map registration numbers, tax identifiers, procurement supplier IDs, LEI records and exchange tickers as separate keys until verified.
• Language and formats: normalize local-language names, legal forms, transliteration, accents, abbreviations and address formats carefully.
• Operational access: document whether the workflow is public search, API, bulk file, paid extract, login-only service, PDF, CKAN/OData/SPARQL or manual request.

Reuse Checklist for Moldova

Controlled Access, RSUD Extracts and Privacy Clearance

Moldova passes the refresh bar after holding the unstable legal-publication route from the public source matrix. The article can rely on ASP, RSUD, e-services, date.gov.md, tax, procurement, statistics, AGEPI and BNM sources, but it must distinguish public verification from authorized data exchange, extracts, beneficial-owner updates and contact-data use.

Claims allowed in this article

• The Public Services Agency is the core official source for Moldova legal-entity registration services.
• Moldova has useful open-data, tax, procurement, statistics, IP and central-bank enrichment layers.
• RSUD extracts and beneficial-owner updates should be discussed with privacy and paid/service workflow caveats.

Claims blocked from this article

• Do not claim a complete free official bulk company register for Moldova.
• Do not treat beneficial-owner, director, tax or public-service fields as marketing-contact permission.
• Do not rely on private Moldova company databases as authority for official reuse rights.

Historical source-risk note

• Moldova local acts register: actelocale.gov.md remains held as text-only source-risk context; it is not linked and is not required for this company-data guide.

Source-risk notes

• RSUD boundary: RSUD extract and legal-unit verification workflows are not the same as a complete free bulk register.
• Authorized-access boundary: authentic exchange between state systems can require role approval or legal basis.
• Beneficial-owner boundary: BO updates and natural-person-adjacent data belong in compliance context, not outreach lists.
• Language boundary: Romanian, Russian/Cyrillic variants, transliteration and legal forms need normalization.

Held Source-Risk Findings

The following routes are useful research context but are not clean linked evidence in this article cycle:

• Moldova tender portal: held and de-linked after the latest quality gate recorded HTTP 403 for the Bingbot profile. Browser and Googlebot access were previously clean, but the route can return to the linked source stack only after browser, Googlebot and Bingbot profiles all retrieve real procurement content without 403, challenge or soft-block semantics.
• Moldova local acts register: actelocale.gov.md remains historical source-risk context only. It is not linked and is not required for the Moldova company-data article.
• Complete free registry bulk claim: blocked. The source map verifies official ASP/RSUD authority and controlled workflows, not a complete free reusable all-company file.
• Beneficial-owner, director, tax and IDNO claims: blocked unless a current official route proves field scope, lawful use and privacy clearance.
• Marketing-contact claim: blocked. ASP, RSUD, tax, procurement, statistics, IP and central-bank sources do not create consent for cold outreach, phone extraction or lead resale.

Resource Pack

Use this resource pack as a working map for verification, ingestion planning and source-risk review. The small source logos are decorative credibility cues only; the authority still comes from the official URL, owner, access model and reuse note.

Source-by-Source Deep Dives

1. Public Services Agency legal entities

Owner: official registry. Access: https://www.asp.gov.md/en/servicii/persoane-juridice.

• What it gives: Core legal-entity registration and RSUD extract route.
• Reuse value: ASP terms; service fees may apply
• Main limitation: Service page, not proof of complete free bulk.

Public Services Agency legal entities is a official registry source for Moldova. Its main practical value is Core legal-entity registration and RSUD extract route. Access is through https://www.asp.gov.md/en/servicii/persoane-juridice, so the source should be treated according to that access model rather than assumed to be an unrestricted bulk feed.

For reuse, the working rule is: ASP terms; service fees may apply. The main limitation is Service page, not proof of complete free bulk. In a normalized company-data workflow this source should be captured with provenance, retrieval date, field-level caveats and a clear distinction between legal-entity facts, compliance signals and any later marketing/contact enrichment.

2. Moldova public-services ASP page

Owner: official government service portal. Access: https://servicii.gov.md/en/organization/ASP.

• What it gives: Service-route discovery for ASP legal-entity services.
• Reuse value: service-portal terms
• Main limitation: Redirects to EVO platform; service catalogue, not registry bulk.

Moldova public-services ASP page is a official government service portal source for Moldova. Its main practical value is Service-route discovery for ASP legal-entity services. Access is through https://servicii.gov.md/en/organization/ASP, so the source should be treated according to that access model rather than assumed to be an unrestricted bulk feed.

For reuse, the working rule is: service-portal terms. The main limitation is Redirects to EVO platform; service catalogue, not registry bulk. In a normalized company-data workflow this source should be captured with provenance, retrieval date, field-level caveats and a clear distinction between legal-entity facts, compliance signals and any later marketing/contact enrichment.

3. ASP electronic bulletin

Owner: official registry. Access: https://www.asp.gov.md/en/date-deschise/date-statistice/buletinului-electronic.

• What it gives: Electronic bulletin/statistics about legal-entity registration.
• Reuse value: ASP terms
• Main limitation: Statistics/publication layer, not every company field.

ASP electronic bulletin is a official registry source for Moldova. Its main practical value is Electronic bulletin/statistics about legal-entity registration. Access is through https://www.asp.gov.md/en/date-deschise/date-statistice/buletinului-electronic, so the source should be treated according to that access model rather than assumed to be an unrestricted bulk feed.

For reuse, the working rule is: ASP terms. The main limitation is Statistics/publication layer, not every company field. In a normalized company-data workflow this source should be captured with provenance, retrieval date, field-level caveats and a clear distinction between legal-entity facts, compliance signals and any later marketing/contact enrichment.

4. Moldova open-data portal

Owner: official open data. Access: https://date.gov.md/.

• What it gives: Dataset discovery and possible API/bulk access.
• Reuse value: dataset-specific terms
• Main limitation: Dataset provenance must be checked individually.

Moldova open-data portal is a official open data source for Moldova. Its main practical value is Dataset discovery and possible API/bulk access. Access is through https://date.gov.md/, so the source should be treated according to that access model rather than assumed to be an unrestricted bulk feed.

For reuse, the working rule is: dataset-specific terms. The main limitation is Dataset provenance must be checked individually. In a normalized company-data workflow this source should be captured with provenance, retrieval date, field-level caveats and a clear distinction between legal-entity facts, compliance signals and any later marketing/contact enrichment.

5. Moldova taxpayer lookup

Owner: official tax authority. Access: https://servicii.fisc.md/contribuabil.aspx.

• What it gives: Taxpayer and fiscal identifier context.
• Reuse value: tax authority terms
• Main limitation: Tax layer and privacy limits apply.

Moldova taxpayer lookup is a official tax authority source for Moldova. Its main practical value is Taxpayer and fiscal identifier context. Access is through https://servicii.fisc.md/contribuabil.aspx, so the source should be treated according to that access model rather than assumed to be an unrestricted bulk feed.

For reuse, the working rule is: tax authority terms. The main limitation is Tax layer and privacy limits apply. In a normalized company-data workflow this source should be captured with provenance, retrieval date, field-level caveats and a clear distinction between legal-entity facts, compliance signals and any later marketing/contact enrichment.

6. Moldova tender portal

Owner: official procurement. Access: held as procurement context after the latest source QA returned HTTP 403 for the Bingbot profile.

• What it gives: Supplier and award context.
• Reuse value: procurement portal terms
• Main limitation: Procurement subset only.

Moldova tender portal is a official procurement source for Moldova. Its main practical value is Supplier and award context. The public route is currently held and de-linked because the latest source QA returned HTTP 403 for the Bingbot profile, so it should be treated as source-mapped procurement context rather than clean linked evidence.

For reuse, the working rule is: procurement portal terms. The main limitation is Procurement subset only. In a normalized company-data workflow this source should be captured with provenance, retrieval date, field-level caveats and a clear distinction between legal-entity facts, compliance signals and any later marketing/contact enrichment.

7. National Bureau of Statistics Moldova

Owner: official statistics. Access: https://statistica.gov.md/en.

• What it gives: Business-demography and macro context.
• Reuse value: statistics terms
• Main limitation: Aggregate/statistical layer.

National Bureau of Statistics Moldova is a official statistics source for Moldova. Its main practical value is Business-demography and macro context. Access is through https://statistica.gov.md/en, so the source should be treated according to that access model rather than assumed to be an unrestricted bulk feed.

For reuse, the working rule is: statistics terms. The main limitation is Aggregate/statistical layer. In a normalized company-data workflow this source should be captured with provenance, retrieval date, field-level caveats and a clear distinction between legal-entity facts, compliance signals and any later marketing/contact enrichment.

8. AGEPI

Owner: official IP authority. Access: https://agepi.gov.md/en.

• What it gives: IP-owner and trademark enrichment.
• Reuse value: AGEPI terms
• Main limitation: IP layer only.

AGEPI is a official IP authority source for Moldova. Its main practical value is IP-owner and trademark enrichment. Access is through https://agepi.gov.md/en, so the source should be treated according to that access model rather than assumed to be an unrestricted bulk feed.

For reuse, the working rule is: AGEPI terms. The main limitation is IP layer only. In a normalized company-data workflow this source should be captured with provenance, retrieval date, field-level caveats and a clear distinction between legal-entity facts, compliance signals and any later marketing/contact enrichment.

9. National Bank of Moldova

Owner: official central bank. Access: https://www.bnm.md/en.

• What it gives: Financial-sector regulated-entity context.
• Reuse value: BNM terms
• Main limitation: Sector-specific.

National Bank of Moldova is a official central bank source for Moldova. Its main practical value is Financial-sector regulated-entity context. Access is through https://www.bnm.md/en, so the source should be treated according to that access model rather than assumed to be an unrestricted bulk feed.

For reuse, the working rule is: BNM terms. The main limitation is Sector-specific. In a normalized company-data workflow this source should be captured with provenance, retrieval date, field-level caveats and a clear distinction between legal-entity facts, compliance signals and any later marketing/contact enrichment.

10. Moldova e-services legal units record

Owner: official e-services / Public Services Agency. Access: https://e-services.md/ro/content/evidenta-unitatilor-de-drept.

• What it gives: Legal-unit verification by IDNO and RSUD-derived public fields.
• Reuse value: e-services and ASP terms
• Main limitation: Search workflow, not bulk reuse permission.

Moldova e-services legal units record is a official e-services / Public Services Agency source for Moldova. Its main practical value is Legal-unit verification by IDNO and RSUD-derived public fields. Access is through https://e-services.md/ro/content/evidenta-unitatilor-de-drept, so the source should be treated according to that access model rather than assumed to be an unrestricted bulk feed.

For reuse, the working rule is: e-services and ASP terms. The main limitation is Search workflow, not bulk reuse permission. In a normalized company-data workflow this source should be captured with provenance, retrieval date, field-level caveats and a clear distinction between legal-entity facts, compliance signals and any later marketing/contact enrichment.

How to Build a Moldova Company Dataset

A defensible Moldova dataset should use ASP/RSUD as the legal-identity anchor and preserve every official source boundary. The source stack is strong, but it is not a single open bulk download.

1. Entity seed: start with ASP legal-entity services and e-services legal-unit verification for RSUD-derived identity, IDNO, status and basic verification fields.
2. Extract and service boundary: record whether a field came from a public search, service catalogue, RSUD extract, paid workflow or authorized exchange.
3. Dataset discovery: use date.gov.md for official datasets and API/bulk candidates, but store dataset-level licence and update notes.
4. Activity enrichment: add taxpayer lookup, tender.gov.md procurement, AGEPI IP and BNM regulated-entity context only where each source supports the field.
5. Coverage benchmark: use ASP RSUD statistics and the National Bureau of Statistics for aggregate coverage checks, not company-level facts.
6. Commercial delivery: keep company facts, privacy-sensitive compliance fields and contact data in separate tables with separate lawful-use controls.

Practical Options

Official open-data or API route

Start with the Public Services Agency legal-entities page and RSUD/e-services routes for entity identity, extracts and legal-unit verification. Use date.gov.md for official dataset discovery, the tax service for taxpayer/IDNO context, Moldova tender portal only as held procurement context until Bingbot access clears, statistica.gov.md and ASP RSUD statistics for aggregate checks, AGEPI for IP ownership and the National Bank of Moldova for regulated financial-sector context.

For production use, treat this route as an ingestion plan rather than a single download. Start with the official registry or data catalogue, keep raw source snapshots, record access terms, then add enrichment sources one by one with field-level provenance.

Manual verification and document route

Some countries expose important company facts through certificates, PDF filings, gazette notices, paid extracts or login-based services. Those sources can be valuable, but they should be documented as controlled workflows. Do not describe them as open APIs or bulk datasets unless the authority clearly publishes that access model.

Contact-data and marketing-list route

For sales outreach, company identity data is only the first layer. Business emails, phone numbers, contact roles, suppression logic and segmentation require a separate compliant contact-data process. That layer should be documented separately from official registry reuse.

Private reports and risk products

Private company-report providers can be useful for manual due diligence in Moldova, but the editorial focus here is not a directory of competitors. The strategic value is understanding which official sources exist and where normalization is required.

If a user needs CRM-ready company records, the practical path is to combine official-source provenance with enrichment, deduplication, quality checks and lawful delivery controls. That is different from buying a generic lead list: the official-source layer explains what can be verified, while the commercial dataset layer explains how the records can be used operationally.

What Is Missing from Official Open Data?

• Do not claim that Moldova publishes a complete free official bulk company register.
• RSUD extracts, legal-unit verification and authorized data exchange can have different access rules.
• Beneficial-owner, director, IDNO, tax and service fields should not be treated as marketing-contact permission.
• Romanian-language names, Cyrillic/Russian variants, transliteration and legal forms require normalization.
• Open-data catalogue entries must be checked dataset by dataset before reuse.
• Procurement, tax, statistics, IP and central-bank sources are enrichment layers, not replacements for ASP/RSUD.
• The actelocale.gov.md route is held from the public article because this node returned 403 and it is not required for company-data publication.

This is why company-data products often add value even when the underlying public sources are strong: official data is frequently split across authorities, formats, languages, identifiers and access models.

Missing data should be treated explicitly in the dataset design. If an official source lacks bulk downloads, CompaniesData should not pretend that the bulk file exists; it should record the source limitation, add alternate official enrichment where lawful, and expose confidence fields so users know which attributes came from which layer.

Recommended Data Model

A practical CompaniesData-style model for Moldova should keep source evidence and commercial-use fields separate. The core table should hold legal entity identity, status, registration identifiers, legal form, jurisdiction, registered address and source dates. Separate enrichment tables can then store procurement awards, IP assets, regulator status, listed-company signals, LEI matches, sanctions/compliance hits and statistics-sector context.

• Entity identity: legal name, normalized name, registration number, jurisdiction, legal form and lifecycle status.
• Source provenance: source URL, authority, retrieval date, access method, licence/reuse note and confidence flag.
• Event history: incorporation, amendments, filings, gazette notices, insolvency or dissolution where legally public.
• Enrichment: procurement, IP, regulator, exchange, LEI and official statistics layers with their own source dates.
• Commercial delivery: CRM-ready exports, segmentation and contact-data fields only when a separate lawful basis and suppression workflow exist.

How CompaniesData Adds Value

For Moldova, CompaniesData's role is to turn fragmented source material into a usable business dataset: normalized company names, deduplicated entities, consistent country and activity fields, source provenance, update tracking and enrichment hooks.

• Normalize register identifiers and legal names.
• Match official company records with procurement, IP, LEI and regulator signals.
• Flag source provenance so every derived profile can be audited.
• Separate company identity from contact-data and marketing-permission layers.
• Package data for analysis, CRM enrichment and market research instead of forcing users to parse portals manually.

For Moldova, the editorial value of CompaniesData is not claiming that every record is open or that every field can be reused without conditions. The value is the opposite: making source boundaries visible, normalizing messy records, adding explainable enrichment and delivering a dataset that users can audit instead of a black-box scrape.

Request a CompaniesData sample for Moldova if you need a practical dataset rather than a list of source portals.

Commercial Dataset and Contact-Data Boundary

This Moldova guide supports CompaniesData’s company-database work, but official-source visibility is not marketing permission. ASP/RSUD data, IDNO checks, tax records, tenders, IP records and central-bank lists can verify company facts. They do not automatically authorize business-email lists, phone outreach or sales-prospecting resale.

• Company identity layer: legal name, IDNO/registration identifiers, legal form, status, jurisdiction, source URL and retrieval date.
• Official enrichment layer: procurement, tax, IP, central-bank and statistics context with field-level provenance.
• Compliance layer: beneficial-owner updates, natural-person-adjacent data, authorized-access notes and purpose limits.
• Contact-data layer: business emails, phones, contact roles, segmentation and suppression require a separate lawful workflow through CompaniesData.cloud.
• Spanish-speaking buyers: Hispanic contact-data demand should be routed to CentraldeComunicacion.es instead of third-party contact-data competitors.

Source Matrix

Source	Owner	What it gives	Reuse value	Limitations
Public Services Agency legal entities	official registry	Core legal-entity registration and RSUD extract route.	ASP terms; service fees may apply	Service page, not proof of complete free bulk.
Moldova public-services ASP page	official government service portal	Service-route discovery for ASP legal-entity services.	service-portal terms	Redirects to EVO platform; service catalogue, not registry bulk.
ASP electronic bulletin	official registry	Electronic bulletin/statistics about legal-entity registration.	ASP terms	Statistics/publication layer, not every company field.
Moldova open-data portal	official open data	Dataset discovery and possible API/bulk access.	dataset-specific terms	Dataset provenance must be checked individually.
Moldova taxpayer lookup	official tax authority	Taxpayer and fiscal identifier context.	tax authority terms	Tax layer and privacy limits apply.
Moldova tender portal	official procurement	Supplier and award context.	procurement portal terms	Procurement subset only.
National Bureau of Statistics Moldova	official statistics	Business-demography and macro context.	statistics terms	Aggregate/statistical layer.
AGEPI	official IP authority	IP-owner and trademark enrichment.	AGEPI terms	IP layer only.
National Bank of Moldova	official central bank	Financial-sector regulated-entity context.	BNM terms	Sector-specific.
Moldova e-services legal units record	official e-services / Public Services Agency	Legal-unit verification by IDNO and RSUD-derived public fields.	e-services and ASP terms	Search workflow, not bulk reuse permission.
ASP RSUD legal-form statistics	official registry	Business-register coverage by legal form.	ASP terms	Aggregate statistics, not entity-level registry records.
ASP RSUD activity statistics	official registry	Business-register coverage by declared activity.	ASP terms	Aggregate statistics, not an activity classifier for every company profile.

Moldova has a strong Public Services Agency legal-entities service page, public-services route, ASP electronic bulletin/statistics, date.gov.md, tax lookup, procurement, statistics, IP and central-bank layers. Only actelocale.gov.md returned 403 and is not required for a company-data article.

FAQ

Is there a single free official bulk company database for Moldova?

Not always. Moldova has official company-data sources, but bulk access, API access, paid extracts and web search can be separate products. Do not assume a complete free bulk file unless the specific source proves it.

What is the best first source for Moldova company data?

The best first source is Public Services Agency legal-entity services, RSUD extract and e-services routes, the Moldova open-data portal, taxpayer lookup, tender portal, statistics, AGEPI and National Bank sources as separate official layers. It should then be combined with statistics, procurement, IP and regulator sources.

Can public company data be reused commercially?

Often yes, but only under the conditions of the specific source. Attribution, update-date preservation, no-endorsement wording and GDPR controls may apply.

Can I use registry data for cold email marketing?

No automatic conclusion follows from public registry access. Marketing requires a separate lawful basis, suppression handling and contact-data compliance review.

Why use CompaniesData instead of manually collecting Moldova sources?

Manual collection is slow because identifiers, formats, languages and coverage differ by source. CompaniesData adds normalization, matching, deduplication, provenance and practical delivery formats.

How often should Moldova company data be refreshed?

Refresh cadence depends on the source. Registry searches and APIs can support frequent checks, while gazettes, procurement portals, statistical releases and paid extracts may update on different schedules. A reliable dataset should store retrieval dates and source-specific update notes.

What should be audited before publishing or selling an enriched dataset?

Audit source authority, licence terms, personal-data exposure, contact-data lawful basis, field provenance, suppression rules, update dates and whether any official source prohibits automated reuse or resale.

Official Sources

• Public Services Agency legal entities – official registry
• Moldova public-services ASP page – official government service portal
• ASP electronic bulletin – official registry
• Moldova open-data portal – official open data
• Moldova taxpayer lookup – official tax authority
• Moldova tender portal – official procurement
• National Bureau of Statistics Moldova – official statistics
• AGEPI – official IP authority
• National Bank of Moldova – official central bank
• Moldova e-services legal units record – official e-services / Public Services Agency
• ASP RSUD legal-form statistics – official registry
• ASP RSUD activity statistics – official registry