Comparison · registries.io

registries.io Alternative

A free registry lookup tool with an API in development, or a live REST API with published pricing. Different products at different stages — here's the honest read, including where registries.io is ahead of us.

TL;DR

registries.io is a company-lookup and PDF-report tool for European registries, built by the team behind TransactionLink, a KYB automation platform. You search a company and get directors, shareholders, beneficial owners with ownership percentages, and addresses. Search is free; a free account unlocks fuller reports.

The deciding difference today is that registries.io has no API yet — its site advertises a JSON API as "coming soon", with no developer documentation published. If your use case is programmatic, Prometiam is live now with a REST API, an OpenAPI spec, an MCP server and public pricing. If your use case is a person looking up a company by hand, registries.io does that free and covers four countries Prometiam doesn't.

Coverage — barely any overlap

registries.io's homepage banner states 20 countries, but its registries directory documents named registers for six: Austria, Czechia, Germany, the United Kingdom, Lithuania and Poland. We're citing the six that are documented rather than the banner figure, for the same reason we'd want you to check ours.

Prometiam covers Spain, France, the United Kingdom, Ireland, Poland, Norway, Finland, Sweden, Belgium, Denmark, Estonia, Slovakia, Switzerland, Latvia, Cyprus, Romania, Croatia, Lithuania, Canada, Australia, Japan, Israel, Singapore, Colombia, Taiwan, Czech Republic, Germany, Brazil and the United States. So the overlap is the UK, Poland, Czechia, Lithuania and, for LEI-registered entities and energy-market register companies, Germany — and in Poland they are ahead of us. Everywhere else, the two products simply serve different markets.

Where registries.io is genuinely ahead

Three things, stated plainly:

1. Poland. They link CRBR — the Polish beneficial-ownership register — and KRZ, the National Register of Debtors, alongside the KRS. Prometiam serves Polish companies from the KRS but has no Polish directors and no Polish UBO. That's a real gap on our side, it's on our roadmap, and it isn't closed today. If Poland is your primary market and you need ownership, they cover a register we don't.
2. What we don't have. Austria, and the German commercial register: our German company records are LEI-registered entities and energy-market register companies, alongside insolvency notices.
3. Live lookup instead of a warehouse. They describe querying official registries in real time rather than serving a pre-built copy. A record fetched that way is never stale. That's a legitimate architectural advantage over any daily-refreshed database, ours included.

Where Prometiam is ahead

1. There is an API, today. REST, bearer token, cursor pagination, an OpenAPI spec, and an MCP server (prometiam-risk-mcp, 36 tools) for Claude, Cursor and agent SDKs. registries.io's API is announced, not shipped.
2. Published pricing. €9.99 / €29.99 / €99.99 / custom. registries.io publishes none, so you can't budget it.
3. Sanctions and export-control screening (beta). Six sanctions lists plus 11 US export-control lists, refreshed daily, with fuzzy matching and confidence scores. Nothing equivalent appears on their site.
4. Corporate events as data. A normalized, queryable timeline of capital changes, director changes, dissolutions and mergers — not just a current-state snapshot.
5. Cross-border insolvency. Corporate insolvency across France, Finland, Germany, the UK, Austria, Norway, Switzerland, the Netherlands and the US.
6. Ongoing monitoring. Subscribe a company (Spain, Ireland or Poland) and receive signed webhooks on events, status changes and sanctions hits.

Live lookup vs daily-refreshed — the real trade-off

It's worth being fair about this rather than claiming our architecture is simply better, because it isn't simply better.

Live lookup guarantees the record is current at the moment you ask. The costs are that every query depends on the source registry being available and fast, per-call latency is bounded by the slowest registry, bulk operations are impractical, and you can't ask questions that span countries or time — "which of my 4,000 counterparties changed director this month" has no cheap answer.

A daily-refreshed normalized warehouse — Prometiam's model — makes exactly those questions cheap: fast search across every company in a register, cross-country joins, historical event timelines, portfolio monitoring, and predictable latency independent of registry uptime. The cost is being up to a day behind, which is why we publish per-country freshness on /coverage rather than asking you to take it on faith.

For a one-off check on a single company, live lookup is the better shape. For continuous monitoring of a portfolio, or any analytical question, the warehouse wins.

At a glance

Who should choose which

Choose registries.io if: your market is Germany, Czechia, Lithuania, Austria or Poland; you need Polish or German statutory beneficial ownership; your workflow is a person checking a company and downloading a report; or you specifically want live registry reads rather than a refreshed copy.

Choose Prometiam if: you need an API today; your counterparties are on a European registry Prometiam covers; you need sanctions and export-control screening (beta) in the same call; you need corporate-event history or portfolio monitoring; or you need published pricing to budget against.

Consider both if your book spans Iberia or the Nordics and the DACH/CEE markets — the coverage overlap is only the UK and Poland, so they add rather than duplicate.

Beyond the registry record

Two derived signals, neither of them a rating. Both are dated facts carrying the source they came from, so whoever reviews your file can check them.

• Companies that stopped filing. A company that quietly stops trading rarely dissolves; the register notices first. The registry_compliance flag returns that state in one shape for Spain (provisional closure of the registry sheet), the United Kingdom (a strike-off proposal, or annual accounts overdue), Ireland (the strike-off list) and Norway (compulsory liquidation). Read it on GET /companies/{id}?include=risk_flags, or list those companies with risk_flag_type=registry_compliance. It is a compliance signal, not an insolvency: read it together with status.
• Public contracts, and the buyer behind them. GET /procurement/awards returns public-contract awards from Spain, France, the UK, Ireland, Poland and Norway by supplier, buyer, identifier, CPV code and date, linked to the supplier’s registry record where the identifier resolves. GET /procurement/buyer/{id} scores the contracting body itself: the probability that its next award draws a single bid, and the probability that a supplier it awards to enters insolvency within two years.

Both are ordinary REST calls on the published price and included in the 14-day trial. Procurement awards cover Spain, France, the UK, Ireland, Poland and Norway (Ireland, Poland and Norway above the EU thresholds only), the buyer scores are Spain and France and in beta, and a score is a prompt to look, never a finding of wrongdoing.

FAQ

Does registries.io have an API?
Not as at 28 July 2026 — it's advertised as "coming soon" with no published developer docs. Verify before relying on this; announced features ship.

What does registries.io cost?
No published pricing. Search is free, and a free account unlocks fuller PDF reports.

Which is better for Poland?
registries.io, if you need ownership. They link CRBR (UBO) and KRZ (debtors); Prometiam has Polish companies from the KRS but no Polish directors or UBO.

Which is better for Spain, France or Norway?
Prometiam — registries.io documents no registers for those countries.

Does either do sanctions screening?
Prometiam does (beta): six sanctions lists plus 11 US export-control lists, refreshed daily. registries.io does not advertise sanctions.

Is Prometiam GDPR-compliant?
Yes. Data is hosted in the EU (Frankfurt). Officer data is processed under GDPR Article 6(1)(c) (legal obligation of public registries) and Article 6(1)(f) (legitimate interest in fraud prevention).

See other comparisons

• OpenRegister alternative
• HitHorizons alternative
• OpenCorporates alternative
• Kyckr alternative