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

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

{"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

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

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.

❓ 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
• 📧 Email: info@foxlabs.com.tr
• 🐛 Issues: open a ticket in the Actor’s Issues tab
• 🧰 More clean B2B data actors: Fox Labs on Apify

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.