# Estonia Company Data, Contacts & Ownership (Äriregister) (`foxlabs/estonia-company-data`) Actor

Search 358K+ Estonian companies from the official Business Register. Verified identity, address, email & phone, VAT, capital and activities (EMTAK) — plus optional ownership: board, shareholders & beneficial owners (UBO). Open data (CC BY 4.0), no key.

- **URL**: https://apify.com/foxlabs/estonia-company-data.md
- **Developed by:** [Berkan Kaplan](https://apify.com/foxlabs) (community)
- **Categories:** Lead generation
- **Stats:** 3 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

from $7.00 / 1,000 results

This Actor is paid per event. You are not charged for the Apify platform usage, but only a fixed price for specific events.

Learn more: https://docs.apify.com/actors/running/actors-in-store.md#pay-per-event

## What's an Apify Actor?

Actors are web data automations that power AI and operations. They run on the Apify platform to scrape websites, process data, connect APIs, and automate workflows.
In Batch mode, an Actor accepts a well-defined JSON input, performs an action which can take anything from a few seconds to a few hours,
and optionally produces a well-defined JSON output, datasets with results, or files in key-value store.
In Standby mode, an Actor provides a web server which can be used as a website, API, or an MCP server.
Actors are written with capital "A".

## How to integrate an Actor?

If asked about integration, you help developers integrate Actors into their projects.
You adapt to their stack and deliver integrations that are safe, well-documented, and production-ready.
The best way to integrate Actors is as follows.

- **AI agents and MCP clients** — the [Apify MCP server](https://docs.apify.com/integrations/mcp.md) at `https://mcp.apify.com` (remote, streamable HTTP, OAuth on first use).
- **Agentic workflows and local Actor development** — [Agent Skills](https://apify.com/.well-known/agent-skills/index.json) with the [Apify CLI](https://docs.apify.com/cli/docs.md): `npm install -g apify-cli`, then `apify login`.
- **JavaScript/TypeScript projects** — the official [JS/TS client](https://docs.apify.com/api/client/js/docs.md): `npm install apify-client`.
- **Python projects** — the official [Python client](https://docs.apify.com/api/client/python/docs.md): `pip install apify-client`.
- **Any other language** — the [REST API](https://docs.apify.com/api/v2.md).

For usage examples, see the [API](#api) section below.

For more details, see Apify documentation as [Markdown index](https://docs.apify.com/llms.txt) and [Markdown full-text](https://docs.apify.com/llms-full.txt).

# README

## Estonia Company Data — e-Business Register 🇪🇪

🎉 Turn the Estonian e-Business Register into clean, structured company data — no login, no API key, one row per entity, with the registry code, legal form, status, industry, address and (where published) email.
Built for B2B sales, lead generation, KYB / compliance and market-research teams.

### 🔍 What is the Estonia Company Data — and when should you use it?

Give this actor company names or Estonian registry codes and it returns matching companies from the Estonian e-Business Register (open data) — as clean, deduplicated rows you can filter, export or feed to an AI agent. Every run queries the source live, so the data is as fresh as the registry itself.

**Use it when you need:** a Estonia company list for outreach; formation / status monitoring; or a canonical registry record for KYB and due diligence.

**Use something else when:** you need revenue or headcount — the register carries identity, industry and contact fields, not financials.

### 🤖 Use with AI agents

**Already on the Apify MCP server?** Ask for this Actor by name: `foxlabs/estonia-company-data`.

**Your agent can pay for its own runs.** This Actor is pay-per-event with agentic payments, so an agent can discover it, run it and settle the bill over **x402 (USDC on Base)** or **Skyfire** — no Apify account or API token of its own. Billing is the same either way: per delivered record, never for errors.

Otherwise paste this into Claude, ChatGPT, Cursor or any MCP-enabled assistant:

```
I want to pull Estonia company records using the Apify Actor `foxlabs/estonia-company-data`.
Input: `queries` is a list of company names or Estonian registry codes. `maxResultsPerQuery` caps rows per query.
Start with: {"queries":["undefined"],"maxResultsPerQuery":50}
Ask me what to look up, run the Actor, then summarise the rows as a table.
```

The machine-readable API, MCP config and OpenAPI definition live at `apify.com/foxlabs/estonia-company-data.md`.

### 📋 Overview

Everything you need to turn the Estonian e-Business Register (open data) into clean, structured data — in one actor, with no login, cookies or API key.

**Why teams pick this actor:**

- ✅ **Whole registry, one call** — name or ID in, matching companies out.
- 🧹 **No empty-promise columns** — only fields this registry actually fills; degenerate columns are removed.
- 🔗 **Stable identifiers** — every row carries the source's own IDs, ready to join across runs and to other Fox Labs actors.
- 💰 **Pay only for results** — per-row pricing, empty/failed lookups never billed.
- 🤖 **Agent-ready** — MCP + x402 agentic payments.

### ✨ Features

- 🔍 **Name or ID lookup** — relevance-ranked name search or exact registry-ID lookup.
- 🏢 **Full entity profile** — status, legal form, formation date, address and the registry’s own contact fields.
- 🧹 **Clean schema** — deduplicated camelCase rows, ready for CSV/Excel/JSON.

### 🎬 Quick Start

```bash
curl -X POST "https://api.apify.com/v2/acts/foxlabs~estonia-company-data/runs?token=YOUR_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{"queries":["undefined"],"maxResultsPerQuery":50}'
```

### 🚀 Getting Started (3 steps)

1. **Choose your targets** — company names or Estonian registry codes.
2. **Set the cap** — `maxResultsPerQuery` limits rows per query.
3. **Run and export** — get a clean dataset as JSON, CSV or Excel.

### 📥 Input

```json
{"queries":["undefined"],"maxResultsPerQuery":50}
```

| Field | Type | Description |
|---|---|---|
| `queries` | array | Company names or Estonian registry codes. |
| `maxResultsPerQuery` | integer | Caps rows per query. |
| `maxConcurrency` | integer | How many queries to fetch at once. |
| `includeRaw` | boolean | Attach the source’s untouched record under `raw`. |

### 📤 Output

One row per company, saved to the dataset. Every row also carries `query`, `scrapedAt`, and — when a lookup fails — an `error` explaining why (never silently dropped, never billed).

| Field | Description |
|---|---|
| `name` | Name |
| `registryCode` | Registry Code |
| `legalForm` | Legal form / entity type |
| `status` | `active` / `inactive` / `dissolved` |
| `email` | Email |
| `phone` | Phone |
| `county` | County |
| `primaryActivity` | Primary Activity |
| `registryUrl` | Registry Url |

### 💼 Use cases

**1. Estonia B2B lead lists** — active Estonian companies with an email where published.
*Input:* name searches. *Output:* entities + industry + email. *Use:* a ready outreach list.

**2. Firmographic enrichment** — attach legal form and industry to a registry code.
*Input:* registry codes. *Output:* the register record. *Use:* enrich a CRM.

**3. KYB / due diligence** — verify an Estonian company by registry code.
*Input:* the code or name. *Output:* the canonical register record. *Use:* confirm existence and status.

### 🔗 Integration

**JavaScript / Node.js**

```javascript
import { ApifyClient } from 'apify-client';
const client = new ApifyClient({ token: 'YOUR_TOKEN' });
const run = await client.actor('foxlabs/estonia-company-data').call({"queries":["undefined"],"maxResultsPerQuery":50});
const { items } = await client.dataset(run.defaultDatasetId).listItems();
console.log(items[0]);
```

**Python**

```python
from apify_client import ApifyClient
client = ApifyClient('YOUR_TOKEN')
run = client.actor('foxlabs/estonia-company-data').call(run_input={"queries":["undefined"],"maxResultsPerQuery":50})
for item in client.dataset(run['defaultDatasetId']).iterate_items():
    print(item)
```

**Automation (n8n / Zapier / Make):** schedule or webhook → HTTP request to the actor API with your `queries` → handle the JSON dataset → push to a sheet, CRM or dashboard.

### 📊 Pricing

Pay-per-event: **per delivered record**. Empty or failed lookups are never billed. [View current pricing.](https://apify.com/foxlabs/estonia-company-data)

### ❓ FAQ

**Do I need an account, login or API key?** No. This reads the Estonian e-Business Register (open data).

**What do I search by?** Company names or Estonian registry codes.

**How current is the data?** Every run queries the source live, so results are as fresh as the registry.

**Does it include an email?** Where the register publishes one — Estonian entities commonly list a contact email.

**Can I export to CSV / Excel / JSON?** Yes — directly from the Apify dataset.

### 🐛 Troubleshooting

- **Fewer rows than expected** — raise `maxResultsPerQuery`, or refine the name.
- **A name returns an unexpected entity** — it matched a similar registered name; search the exact registry ID.
- **No rows for a name** — try the entity’s exact legal name or its registry ID.

### ⚖️ Is it legal to scrape this data?

This actor reads a public government business registry published as open data. Results can still contain personal data (e.g. a person’s name); personal data is protected by the GDPR and similar laws, so only process it with a legitimate basis. See Apify’s blog post on the legality of web scraping.

### 🤝 Support & contact

- 🌐 **Website:** [data.foxlabs.com.tr](https://data.foxlabs.com.tr)
- 📧 **Email:** info@foxlabs.com.tr
- 🐛 **Issues:** open a ticket in the Actor’s **Issues** tab
- 🧰 **More clean B2B data actors:** [Fox Labs on Apify](https://apify.com/foxlabs)

### Changelog

#### 0.1 — 2026-09-07

- **Enabled AI-agent payments (x402) + rebuilt the README to the full standard** (What-is / when, AI-agents + x402 agentic payments + MCP, Overview, Features, Use cases, Integration, FAQ, Troubleshooting, Support & contact).

#### 0.0

- Initial release: data from the Estonian e-Business Register (open data) by name or registry ID.

# Actor input Schema

## `searchQuery` (type: `string`):

Find companies whose name contains this text (case-insensitive). Leave empty to browse by the filters below. Example: "Bolt" or "holding".

## `registryCodes` (type: `array`):

Look up specific companies by their 8-digit Estonian registry code (ariregistri kood). Overrides the name search. Example: \["12417834" = Bolt Technology OÜ, "10006966" = CGI Eesti OÜ].

## `legalForm` (type: `string`):

Keep only companies of this legal form. "Any" returns all forms.

## `status` (type: `string`):

Which companies to include by registry status.

## `location` (type: `string`):

Keep only companies whose address contains this text — a county or city. Example: "Tallinn", "Harju", "Tartu". Leave empty for all of Estonia.

## `activityQuery` (type: `string`):

Keep only companies whose reported activity (EMTAK) matches — a numeric EMTAK code prefix (e.g. "62" for IT) or a keyword found in the activity text. Leave empty for all sectors.

## `onlyWithEmail` (type: `boolean`):

Return only companies that publish a contact email (≈96% of active companies do). Useful for lead lists.

## `includeOwnership` (type: `boolean`):

Attach board members, shareholders and beneficial owners (UBO) to each company. Adds ~106 MB of reference downloads (≈2 GB unpacked) at the start of the run, so it is slower — turn on when you need the ownership graph.

## `maxResults` (type: `integer`):

Maximum number of companies to return.

## Actor input object example

```json
{
  "registryCodes": [
    "12417834",
    "10006966"
  ],
  "legalForm": "any",
  "status": "active",
  "onlyWithEmail": false,
  "includeOwnership": true,
  "maxResults": 1000
}
```

# Actor output Schema

## `dataset` (type: `string`):

No description

# API

You can run this Actor programmatically using our API. Below are code examples in JavaScript, Python, and CLI, as well as the OpenAPI specification and MCP server setup.

## JavaScript example

```javascript
import { ApifyClient } from 'apify-client';

// Initialize the ApifyClient with your Apify API token
// Replace the '<YOUR_API_TOKEN>' with your token
const client = new ApifyClient({
    token: '<YOUR_API_TOKEN>',
});

// Prepare Actor input
const input = {
    "searchQuery": "",
    "registryCodes": [
        "12417834",
        "10006966"
    ],
    "includeOwnership": true
};

// Run the Actor and wait for it to finish
const run = await client.actor("foxlabs/estonia-company-data").call(input);

// Fetch and print Actor results from the run's dataset (if any)
console.log('Results from dataset');
console.log(`💾 Check your data here: https://console.apify.com/storage/datasets/${run.defaultDatasetId}`);
const { items } = await client.dataset(run.defaultDatasetId).listItems();
items.forEach((item) => {
    console.dir(item);
});

// 📚 Want to learn more 📖? Go to → https://docs.apify.com/api/client/js/docs

```

## Python example

```python
from apify_client import ApifyClient

# Initialize the ApifyClient with your Apify API token
# Replace '<YOUR_API_TOKEN>' with your token.
client = ApifyClient("<YOUR_API_TOKEN>")

# Prepare the Actor input
run_input = {
    "searchQuery": "",
    "registryCodes": [
        "12417834",
        "10006966",
    ],
    "includeOwnership": True,
}

# Run the Actor and wait for it to finish
run = client.actor("foxlabs/estonia-company-data").call(run_input=run_input)

# Fetch and print Actor results from the run's dataset (if there are any)
print(f"💾 Check your data here: https://console.apify.com/storage/datasets/{run.default_dataset_id}")
for item in client.dataset(run.default_dataset_id).iterate_items():
    print(item)

# 📚 Want to learn more 📖? Go to → https://docs.apify.com/api/client/python/docs/quick-start

```

## CLI example

```bash
echo '{
  "searchQuery": "",
  "registryCodes": [
    "12417834",
    "10006966"
  ],
  "includeOwnership": true
}' |
apify call foxlabs/estonia-company-data --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,foxlabs/estonia-company-data"
        }
    }
}

```

The hosted server signs you in with OAuth on first connect, so no API token belongs in this config. Clients without OAuth support can send an `Authorization: Bearer <APIFY_API_TOKEN>` header instead, using a token from API & Integrations in Apify Console (https://console.apify.com/settings/integrations).

## OpenAPI specification

Download the OpenAPI definition: https://api.apify.com/v2/actors/YvYOepIEbz5JJx55h/builds/7sXYxzhypPIgXhZSh/openapi.json