Existence and status
- Active / dissolved
- Bankruptcy
- Liquidation
- Restructuring
- Insolvency (CZ)
- Auctions, and auction warnings
Platform 01 · Entity data
Public data is fragmented.
Public data is fragmented.
The answer you build on should not be.
Entyrix consolidates public-sector company records from across Europe into one API under a single entity key — registry identity, officers and ownership, annual accounts, credit scoring, sanctions and debarment, public contracts, and NIS2 classification. We built it, we operate it, and our own products run on it. This page describes what is actually in it, where each part comes from, and how to check that for yourself.
- 53.6M
- Entities
- 68
- Public data sources
- 25
- Jurisdictions in the catalogue
- 370+
- Public API endpoints
Snapshot 2 September 2026 · 35.8M entities currently active, 46.3M people in the officer and ownership graph, 18.9M annual accounts, 5.8M public contracts, 2.6M credit-scored entities. Nothing here is a brochure figure: the totals are served live and without an API key from /api/v1/public/stats, the source catalogue from /api/v1/public/data-sources.json, and the endpoint count from the platform's own OpenAPI document. If this page and those endpoints ever disagree, the endpoints are right.
Pipeline
From a registry dump
From a registry dump
to an answer you can defend.
Public registers arrive in inconsistent formats, with undocumented schema changes and no notice when something moves. Most of the engineering is in absorbing that instability so it never reaches the system asking the question.
01
Acquire
Scheduled per-source imports from registers, gazettes, tax authorities and sanctions lists. Each source has its own cadence and its own importer.
scheduled · per-source
02
Validate
Conformance and data-quality rules run at ingest, so a malformed upstream file is rejected at the door rather than silently landing in the entity table.
conformance · DQ rules
03
Reconcile
Divergent schemas mapped to one model. Country codes, legal forms, addresses and national identifiers normalised so the same company from four sources becomes one record.
canonical schema
04
Derive
Composite credit scoring, risk indicators and NIS2 scoping computed on top of the reconciled record — and published in the catalogue as derived, not as source data.
credit · risk · NIS2
05
Serve
REST with per-key rate limiting, a search index kept in sync with the store, and public aggregate endpoints that need no key at all.
PostgreSQL · Meilisearch
Provenance
A value without a source is not evidence.
Most people consuming company data are doing it under an obligation — a KYB file, a sanctions check, a credit decision, a NIS2 scoping exercise. In that setting an answer that cannot say where it came from is not usable, however correct it happens to be.
So the catalogue is part of the product, not documentation about it. Every integrated source is published with its jurisdiction, its category and its licence, at a public URL, under CC-BY 4.0 — including the four entries that are marked derived, because a score we computed is not a fact a register told us, and conflating the two is how a dataset stops being defensible.
- GET/api/v1/public/*216 paths
- GET/api/v1/companies/*80 paths
- GET/api/v1/monitoring/cases9 in group
- GET/api/v1/vat/validateVIES
- POST/api/v1/compliance/nis2-sweepscoping
- POST/api/v1/enrich/jobs3 in group
- GET/api/v1/reconcileentity match
Path counts are the groups reported by the platform's published OpenAPI document on 20 August 2026. The routes shown are real and documented there; they are a sample chosen to span the surface, not the whole of it.
Coverage
What is actually integrated
Fifty-eight sources across eighteen jurisdictions. The company registers are the backbone and are listed here in full; the rest of the catalogue is summarised by category below and published in full at the link underneath.
Company registers · 26 sources
- Firmenbuch Österreich AT
- KBO / BCE BE
- Zefix / LINDAS CH
- DRCOR CY
- ARES CZ
- Äriregister EE
- BORME ES
- PRH YTJ FI
- INSEE SIRENE FR
- Companies House GB
- ΓΕΜΗ / GEMI GR
- Sudski registar HR
- GLEIF + NAV HU
- Companies Registration Office IE
- GLEIF IT
- Registrų centras LT
- Uzņēmumu reģistrs LV
- GLEIF NL
- Brønnøysundregistrene NO
- KRS PL
- GLEIF + BASE PT
- ONRC RO
- AJPES Poslovni register SI
- Register právnických osôb SK
- Register účtovných jednotiek SK
- ЄДР MinJust UA
The remaining 42 sources, by catalogue category
- Web & infrastructure enrichment 8
- Regulatory & supervisory registers 6
- Derived scores and scoping 4
- Financial statements 4
- Identifiers, incl. LEI and IBAN 4
- Public funding and tenders 4
- Beneficial ownership 2
- Debtor registers 2
- Sanctions and leaks 2
- Tax 2
- Bankruptcy 1
- Public contracts 1
- Regulatory monitoring 1
- Search index sync 1
Categories and counts are the platform's own, read from /api/v1/public/data-sources.json on 2 September 2026, where each source is published with its jurisdiction and licence. Depth is not uniform: Slovakia carries 28 of the 68 sources and has by far the richest enrichment; Belgium, Czechia and the United Kingdom hold two each, and every other jurisdiction is a single source - principally registry identity. Four of the 26 registry entries (HU, IT, NL, PT) reach us through GLEIF rather than a direct national register, which is worth knowing before you rely on them for coverage. We would rather say that here than have you discover it after signing something.
Monitoring
Forty signals, watched on a book you already have
A one-off check tells you about the day you ran it. Monitoring compares a stored digest of each company against the current one and reports what moved, with a severity — which is the part that makes it something an operations team can act on rather than another dashboard.
Debt and enforcement
- Tax debt, and its amount
- Tax reliability rating
- Social insurance debt
- Health insurance debt
- Enforcement proceedings
- Pledges
Credit and finances
- Credit score and grade
- Revenue, current and prior
- Profit, current and prior
- Filed statements count
- Share capital
- Capital reductions
Sanctions and ownership
- Sanctions flag and hit count
- Beneficial owners, current and historic
- Statutory body size
- Bank accounts on file
- LEI
- VAT payer status
Identity and profile
- Registered name
- Registered address
- NACE classification
- Website
Public money and exposure
- Public contracts, count and value
- EU projects, count and value
- Critical CVEs on known infrastructure
These are the fields the monitoring digest actually compares — forty of them — not a list of things it could in principle watch. Financial movements are reported with a materiality floor and a change threshold rather than on every cent, so a rounding difference does not wake anyone up.
In use
Three shapes this usually takes
01 · At the point of registration
Company lookup and B2B autofill
A business customer types a company number and the registered name, address, VAT status and legal form arrive filled in and correct. It removes the most common reason a B2B order cannot be invoiced later: the company details were never captured, or were captured as free text nobody can match to a register.
This one runs against public registers, so there is no per-lookup data cost to pass on.
Measured on one B2B shop in July 2026: of 285 active business customers, 148 — 52% — had no company name and registration number on any address. Invoice-on-terms silently never appeared for them at checkout, including one account with over 1,800 orders. Nobody had reported it, because from the outside it looks like a customer who simply pays by card.
02 · Before you extend terms
Credit assessment on invoice
Composite credit score and grade, filed accounts, tax and insurance debt, enforcement and bankruptcy state — assembled for the specific company about to be given payment terms, at the moment the decision is made rather than in a quarterly review.
2.6M entities currently carry a credit score.
03 · Continuously, afterwards
Counterparty monitoring
The forty signals above, watched across an existing customer or supplier book, delivered as a digest or a webhook. The value is not the alert; it is that the alert arrives before the invoice does, on a company you had already decided was fine.
What we sell here is the integration, not a data subscription: Entyrix is our platform, and we connect it to the system you already run — checkout, onboarding, ERP, CRM, or the compliance file. Scope and pricing depend on which of the three you need and what it has to talk to, so those are a conversation rather than a table on a web page.
Next step
Tell us what you need to be true
Tell us what you need to be true
before the invoice goes out.
If you can describe the decision — who you are onboarding, what you have to know about them, and who carries the loss when it is wrong — we can tell you whether this is a week of integration work or a quarter, and where the data genuinely stops.