Does it really return shareholders and beneficial owners?

Estonia publishes both on the register, so yes, where the register holds them. That is unusual in Europe, and it is the main reason to look Estonian entities up directly rather than through an aggregator.

What identifier do I need?

The Estonian registry code, an eight-digit number assigned when the entity is registered.

Do I pay for lookups that come back empty?

No. You are charged per result, so a request that finds nothing costs nothing. Testing this against a messy list is free to get wrong.

What does a lookup cost?

5 points per result, which is $5 per 1,000, and only successful lookups are charged. Points come out of your monthly plan allowance, so there is no separate per-country contract.

Corporate registry

Estonian Business Register API — Company Lookup

Estonia keeps one of the most open company registers in Europe. The e-Business Register publishes not just the registration basics but the right of representation, the shareholder list and tax information — material that most countries treat as private or charge for.

Run it in the app Read the API docs

You send: An Estonian registry code
You get back: The record with representation, shareholders, beneficial owners and tax data
Coverage: Estonia — entities on the Estonian e-Business Register.
Price: 5 pts — $5 per 1,000; Charged only when the record resolves. A lookup that finds nothing is not billed.

Comparison

Ways to get this data

Three approaches teams use today, and where each one runs into trouble.

Approach	What it takes	Cost	Trade-off
the Estonian e-Business Register directly	Search the register in Estonian or English and read each tab by hand	Usually free, sometimes per-document	A different interface, language and data shape for every country you add
Collecting it yourself	Build and host a crawler per register, then keep each one alive	Infrastructure and maintenance	Registers change their pages without warning, and nobody is on the hook when yours breaks
NeuralVerge	One request, the same shape as every other source in the catalog	$5 per 1,000, misses not billed	Covers Estonia — other countries are separate sources with the same request format

Response

What you get back

Every field the response returns.

Field	Type	Description
`general_information`	object	Name, registry code, legal form, status and registered address.
`vat_information`	object	VAT number and the date of VAT registration.
`right_of_representation`	array	Who may sign for the company, with role and personal code.
`shareholders`	array	Shareholders with their identifier and stake percentage.
`beneficial_owners`	array	Ultimate beneficial owners with country of residence.
`tax_information`	object	Tax debt status and when it was last verified.
`areas_of_activity`	array	EMTAK/NACE codes, with the primary one flagged.
`annual_reports`	array	Submitted annual reports with period and document link.
`contacts`	array	Phone, email and website as registered.
`documents`	array	Other documents on file, with direct links.

One response envelope

Every source answers in the same shape: a session id, a readable human summary, a structured machine object and the points the call consumed. Learn it once and it holds across every source in the catalog.

Integration

How to run it

The same lookup works from the app, the API, or as a tool an agent can call mid-task.

A JSON schema passed as extract_schema_json pins the response shape, which is why one endpoint serves every register in the catalog — only the URL and the schema change. The Get API Code button in the app hands you the complete command with the schema already filled in.

curl -X POST https://api.neuralverge.ai/functions/v1/run-extract \
  -H "Authorization: Bearer YOUR_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "url": "https://ariregister.rik.ee/eng/company/10000000",
    "instructions": "Extract data from the Estonian e-Business Register",
    "settings": {
      "country_code": "us",
      "extract_schema_json": "{ ... }"
    }
  }'

Use cases

What teams use it for

Where this field shows up in an actual workflow.

Screening Estonian counterparties

Establish ownership and signing rights before you sign anything yourself.

Verifying VAT status

Confirm the entity is VAT-registered where the transaction requires it.

Ownership mapping

Use the shareholder list to follow a group structure back to its owners.

Baltic market research

Build a picture of a market where the underlying register is genuinely open.

Coverage & limits

Coverage, freshness and limits

What this source covers, how fresh it is, and where it stops.

Coverage

Estonia — entities on the Estonian e-Business Register.

Freshness

Read at request time, so the answer reflects the register as it stands when you ask.

Handling

the Estonian e-Business Register is a public register. Every response carries the source URL it was read from and a session id you can trace.

What it will not do

—Only entities on the Estonian register resolve here.
—Some sections are published in Estonian, and names transliterate inconsistently.
—Sections the register does not hold for an entity come back empty rather than guessed.

FAQ

Questions, answered

The e-Business Register is publicly searchable and much of the data is free to view, with some documents and detailed extracts charged. This source is about getting the same public material as structured data instead of screens.

Related sources

All corporate registries

Company registers across Europe, plus global LEI lookup.

LEI Lookup company

The global identifier for the same legal entity.

Companies House company

The UK equivalent, with beneficial owners.

Try ariregister company on your own data

One request format across every source in the catalog.

Get started