# Company Registry Lookup – European Business Register API (`wsystem/european-company-registry`) Actor

Company registry lookup in official European business registers (France SIRENE, Norway Brønnøysund, Finland PRH, Czech ARES, Poland KRS, Estonia) + GLEIF LEI for any country. Name, ID, status, address, VAT ID.

- **URL**: https://apify.com/wsystem/european-company-registry.md
- **Developed by:** [W System](https://apify.com/wsystem) (community)
- **Categories:** Business, Lead generation, Developer tools
- **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

Pay per event

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?

An Actor is a serverless cloud program that runs on the Apify platform. It has two run modes.
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.

Apify vocabulary and the platform model are defined once, in the agent quickstart at https://apify.com/agents.md.

## 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.

Do not guess an integration path. Every one of them is in the agent quickstart at https://apify.com/agents.md: the Apify MCP server, Agent Skills with the Apify CLI, the JavaScript and Python clients, the REST API, and the account-free path for an agent with no human to sign in. It also carries the rule on stating cost before the first paid run.

For examples already wired to this Actor's own input schema, see the [API](#api) section below.

Each client library has reference documentation the quickstart does not restate: [JavaScript/TypeScript](https://docs.apify.com/api/client/js/docs.md) (`npm install apify-client`) and [Python](https://docs.apify.com/api/client/python/docs.md) (`pip install apify-client`).

# README

## Company Registry Lookup – European Business Register API

**Company registry lookup** – **look up and verify companies in official European business registers** with one API call: France (SIRENE / RNE), Norway (Brønnøysund Enhetsregisteret), Finland (PRH / YTJ), Czech Republic (ARES), Poland (KRS), Estonia (e-Business Register / Äriregister) — plus the **GLEIF Global LEI Index** for Germany, the UK, the Netherlands, Italy, Spain and every other country.

Get a clean, **normalised JSON record**: legal name, registry number, legal form, active/dissolved status, registered address, registration date, **VAT ID**, NACE activity code, website, employees, LEI and a link back to the official register entry.

Built for **KYB (Know Your Business), supplier and customer onboarding, invoice and AP automation, CRM enrichment, due diligence, and AI agents** that need to confirm "does this company exist and is it active?".

### Why this Actor

- ✅ **Official government sources only** – open data APIs published by the registers themselves. No scraping of paid portals, no login, no proxies.
- ✅ **One schema for all countries** – stop writing six integrations with six languages (SIREN, organisasjonsnummer, Y-tunnus, IČO, KRS, registrikood).
- ✅ **Search by name or by number** – registry IDs return an exact match; names return the best matches.
- ✅ **Batch** – up to 1,000 lookups per run, mixed countries (`FR:…`, `NO:…`, `CZ:…`).
- ✅ **AI-agent / MCP ready** – small, predictable output, works through the Apify MCP server and the Apify API.
- ✅ **Fair pricing** – pay per lookup, failed lookups (register down) are not charged.

### Supported registers

| Prefix | Country | Register | Search by |
|---|---|---|---|
| `FR` | France | INSEE SIRENE / RNE (recherche-entreprises.api.gouv.fr) | name, SIREN, SIRET |
| `NO` | Norway | Brønnøysund Register Centre | name, organisasjonsnummer |
| `FI` | Finland | PRH / YTJ open data | name, Y-tunnus (business ID) |
| `CZ` | Czech Republic | ARES (Ministry of Finance) | name, IČO |
| `PL` | Poland | KRS – National Court Register | KRS number |
| `EE` | Estonia | e-Business Register | name, registry code |
| `LEI` or any other ISO code (`DE`, `GB`, `NL`, `IT`, `ES`, `AT`, `BE`, `SE`, `HU`, …) | Worldwide | GLEIF LEI index | name, LEI |

### Input example

```json
{
  "queries": ["FR:552032534", "NO:equinor", "FI:0112038-9", "CZ:skoda auto", "PL:0000019193", "EE:bolt", "DE:siemens"],
  "maxResultsPerQuery": 3
}
```

### Output example

```json
{
  "query": "0112038-9", "lookup_status": "found",
  "country": "FI", "registry_id": "0112038-9", "name": "Nokia Oyj",
  "legal_form": "Public limited company", "status": "registered", "active": true,
  "status_normalized": "active",
  "status_raw": {"companySituations": [], "open_situations": [], "reorganisation": false, "endDate": null, "tradeRegisterStatus": "1", "businessIdStatus": "2"},
  "address": "Karakaari 7", "postal_code": "02610", "city": "ESBO",
  "registration_date": "1978-03-15", "vat_id": "FI01120389",
  "activity_code": "70100", "activity": "Activities of head offices",
  "website": "www.nokia.com", "source": "Finnish Patent and Registration Office (PRH/YTJ)",
  "source_url": "https://tietopalvelu.ytj.fi/yritys/0112038-9"
}
```

`lookup_status` is `found`, `not_found` or `error` (register temporarily unavailable – not charged).

#### Normalized status (`status_normalized`)

One value across all registries: `active` | `in_liquidation` | `bankrupt` | `dissolved` | `unknown`.
`status` and `active` are unchanged (backward compatible); `status_raw` holds the registry's raw code/flags used for the mapping.

| Source | Mapping |
|---|---|
| FR Sirene | `etat_administratif` A → active, C → dissolved |
| NO Brønnøysund | `slettedato` → dissolved; `konkurs` → bankrupt; `underAvvikling` / `underTvangsavviklingEllerTvangsopplosning` → in_liquidation; else active |
| FI PRH | `endDate` → dissolved; open `companySituations` KONK → bankrupt, SELTILA → in_liquidation; SANE (re-organisation) → active with `status_raw.reorganisation: true` |
| CZ ARES | `datumZaniku` or commercial-register source state `ZANIKLY` → dissolved; listed in insolvency register (`stavZdrojeIr: AKTIVNI`) → bankrupt (insolvency proceedings); name “v likvidaci” → in_liquidation |
| PL KRS | open bankruptcy in section 6 (`postepowanieUpadlosciowe` declared and not closed) or name “W UPADŁOŚCI” → bankrupt; liquidation section or name “W LIKWIDACJI” → in_liquidation; deletion date → dissolved; else active |
| EE e-Business Register | R → active, L → in_liquidation, N → bankrupt, K → dissolved |
| GLEIF | entity status ACTIVE → active, INACTIVE → dissolved (`status_raw` also has LEI registration status, e.g. ISSUED/LAPSED/RETIRED) |

Precedence when several flags apply: dissolved > bankrupt > in_liquidation > active.

### Pricing

Pay per event: **$0.008 per company lookup** (one query, up to 25 matches returned). No subscription. 1,000 lookups ≈ $8.

### Use with AI agents (MCP)

Add the Apify MCP server (`https://mcp.apify.com`) to Claude, Cursor or any MCP client and enable this Actor. Example prompts:

- "Is the French company with SIREN 552032534 still active? Give me its VAT number."
- "Find the Norwegian organisation number for Equinor and its registered address."
- "Verify these suppliers exist in their national registers: CZ 00177041, FI 0112038-9, PL KRS 0000019193."

### FAQ

**Is this legal?** Yes. All sources are official open-data APIs published for reuse (France Etalab Licence Ouverte, Norway NLOD, Finland CC BY 4.0, Czech ARES public API, Polish KRS open API, GLEIF CC0). Attribution is included in every record (`source`).
**Germany / UK / Netherlands?** Those national registers have no free open API without registration or paid access, so they are covered via GLEIF (companies with an LEI). Native connectors are on the roadmap.
**Does it check EU VAT numbers?** It returns the VAT ID where the register provides it. To validate a VAT number live against VIES, use our **EU VAT Number Checker** Actor.
**Personal data?** Only company-level records are returned; we do not return officers or shareholders.

Keywords: company registry API, business register lookup, company search API Europe, KYB API, SIREN lookup, SIRET API, Brønnøysund API, organisasjonsnummer, Y-tunnus, IČO ARES, KRS API, Äriregister, LEI lookup, GLEIF API, company verification, supplier verification, MCP company lookup.

# Actor input Schema

## `queries` (type: `array`):

Company name or registry number. Prefix with a country code to mix countries: 'FR:552032534', 'NO:equinor', 'FI:0112038-9', 'CZ:00177041', 'PL:0000019193' (KRS), 'EE:bolt', 'DE:siemens' (GLEIF), 'LEI:529900D6BF99LW9R2E68'.

## `country` (type: `string`):

Used for queries without a prefix. Countries without a native connector are searched in the GLEIF LEI index.

## `maxResultsPerQuery` (type: `integer`):

Name searches can match several companies. Price is per query, not per result.

## Actor input object example

```json
{
  "queries": [
    "FR:552032534",
    "NO:equinor",
    "CZ:skoda auto"
  ],
  "country": "",
  "maxResultsPerQuery": 3
}
```

# Actor output Schema

## `results` (type: `string`):

No description

## `resultsJson` (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 = {
    "queries": [
        "FR:552032534",
        "NO:equinor",
        "CZ:skoda auto"
    ]
};

// Run the Actor and wait for it to finish
const run = await client.actor("wsystem/european-company-registry").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 = { "queries": [
        "FR:552032534",
        "NO:equinor",
        "CZ:skoda auto",
    ] }

# Run the Actor and wait for it to finish
run = client.actor("wsystem/european-company-registry").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 '{
  "queries": [
    "FR:552032534",
    "NO:equinor",
    "CZ:skoda auto"
  ]
}' |
apify call wsystem/european-company-registry --silent --output-dataset

```

## MCP server setup

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

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/i7ydgmT173CqyDRd6/builds/0P5ZhgZqw8pbISbLh/openapi.json