# European Company Search: Multi-Country Register Lookup (`smoked_drift/european-company-search`) Actor

Look up one company name across the official French, Norwegian and Czech company registers in a single run, returned in one common shape: id, name, legal form, status, address, industry and registry. No scraping, no API keys.

- **URL**: https://apify.com/smoked\_drift/european-company-search.md
- **Developed by:** [Titouan MARTY](https://apify.com/smoked_drift) (community)
- **Categories:** Business, Lead generation
- **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

$2.00 / 1,000 company matches

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

## European Company Search: Multi-Country Register Lookup

Search one company name across the **official French, Norwegian and Czech company registers in a single run**, and get every match back in one common shape. Built for cross-border due diligence, KYC onboarding and supplier screening, where the first problem is always the same: the company exists, but you do not know which register holds it.

**No scraping, no API keys.** Every register used here is a documented public API licensed for commercial reuse.

| Register | Country | ID | Licence |
| --- | --- | --- | --- |
| Annuaire des Entreprises (DINUM) | France | SIREN | Licence Ouverte 2.0 |
| Enhetsregisteret (Brreg) | Norway | Org. nr | NLOD |
| ARES (Ministry of Finance) | Czechia | ICO | CC BY 4.0 |

***

### What you get

One row per match, in a single normalised shape regardless of the register:

| Field | Notes |
| --- | --- |
| `countryCode`, `countryName` | Which register the match came from |
| `id`, `idType` | `SIREN`, `ORGNR` or `ICO` — the local identifier, so you can join to the national register |
| `name` | Registered name |
| `legalFormCode`, `legalFormName` | Local legal form code |
| `status` | Normalised where possible: `active`, `dissolved`, `bankrupt`, `under liquidation` |
| `establishedDate`, `dissolvedDate` | ISO-8601 |
| `address`, `postalCode`, `city`, `country` | Registered address |
| `industryCode`, `industryName` | Local activity code (NAF, NACE, CZ-NACE) |
| `employees` | Where the register reports it |
| `vatId` | Where available |
| `extra` | Register-specific extras: directors and accounts for France, website and previous names for Norway, per-register status for Czechia |
| `source` | Registry, licence and attribution |

***

### Sample output

A real run for `Equinor`, trimmed:

```json
[
  {
    "countryCode": "FR", "countryName": "France",
    "id": "450324215", "idType": "SIREN",
    "name": "EQUINOX (EQUINOX - LES SAVEURS OCEANES)",
    "legalFormCode": "5499", "status": "A",
    "city": "SAINT-PIERRE-D'OLERON"
  },
  {
    "countryCode": "NO", "countryName": "Norway",
    "id": "923609016", "idType": "ORGNR",
    "name": "EQUINOR ASA",
    "legalFormCode": "ASA", "legalFormName": "Allmennaksjeselskap",
    "status": "active", "city": "STAVANGER",
    "extra": { "website": "http://www.equinor.com", "vatRegistered": true }
  }
]
```

Notice the value of the aggregation: the French name search returns a similarly-spelled company, the Norwegian one returns the entity you meant. Seeing both side by side is the point.

***

### Usage

#### Find a supplier across the three registers

```json
{ "name": "Asseco", "countries": ["FR", "NO", "CZ"], "maxPerCountry": 25 }
```

#### One country only

```json
{ "name": "Equinor", "countries": ["NO"], "maxPerCountry": 10 }
```

#### Pre-screen before onboarding

```json
{ "name": "Novak", "countries": ["CZ"], "maxPerCountry": 100 }
```

Check `status` on the results: a dissolved or bankrupt entity is a different conversation.

***

### Notes and limits

- **Name matching is per-register and literal.** Each register runs its own search algorithm; there is no fuzzy cross-register entity resolution here. Use this to **find** the entity and its local ID, then use the country-specific Actor for the full record.
- **Different registers know different things.** France publishes directors and filed accounts; Norway publishes website, previous names and bankruptcy state; Czechia publishes per-register status. Missing fields mean the register does not hold them, not that they are absent.
- **Czechia caps a query at 1,000 results** and returns a 400 beyond that; the Actor treats it as "no results" rather than failing the run.
- **Register coverage is deliberately small.** Only registers with an explicit commercial licence and a keyless API are included. Adding a country means verifying its licence first.
- **Attribution is required** by each licence and is included on every row.

***

### Related Actors

For the full record in one country:

- [Companies House Data API](https://apify.com/smoked_drift/uk-companies-house-data) — 5M+ UK companies, Open Government Licence v3.0
- [French Company Data API](https://apify.com/smoked_drift/french-company-data) — 26M French companies with 25 filters, SIRENE and RNE
- [Norway Company Data API](https://apify.com/smoked_drift/norway-company-data) — 1.17M Norwegian entities, 10,000 per request
- [Czech Company Data API](https://apify.com/smoked_drift/czech-company-data) — ARES register search

***

### Support

Want another register added? Open an issue naming the country, and check that its data is published under a licence permitting commercial reuse — that is the gate.

# Actor input Schema

## `name` (type: `string`):

The name to search for, in any language. Each register is queried with it as-is, so try the local spelling if the English one returns nothing.

## `countries` (type: `array`):

Country codes. FR queries the Annuaire des Entreprises, NO the Enhetsregisteret, CZ the ARES register. Leave empty to search all of them.

## `maxPerCountry` (type: `integer`):

Cap on results pulled from each register. Keep it modest: you are usually looking for the right entity, not everything sharing the name.

## Actor input object example

```json
{
  "name": "Equinor",
  "countries": [
    "FR",
    "NO",
    "CZ"
  ],
  "maxPerCountry": 25
}
```

# Actor output Schema

## `matches` (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 = {
    "name": "Equinor",
    "countries": [
        "FR",
        "NO",
        "CZ"
    ]
};

// Run the Actor and wait for it to finish
const run = await client.actor("smoked_drift/european-company-search").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 = {
    "name": "Equinor",
    "countries": [
        "FR",
        "NO",
        "CZ",
    ],
}

# Run the Actor and wait for it to finish
run = client.actor("smoked_drift/european-company-search").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 '{
  "name": "Equinor",
  "countries": [
    "FR",
    "NO",
    "CZ"
  ]
}' |
apify call smoked_drift/european-company-search --silent --output-dataset

```

## MCP server setup

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

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/6YH4RLdmPLZCw44Is/builds/tHlIkfrDhiEx29wTH/openapi.json