# EU Company Registry Search: France SIREN & Norway Brreg (`ai_solution/eu-company-registry-search`) Actor

Search official open European company registers with one schema: France (Sirene, 26M companies) and Norway (Brreg). Filter by name, NAF/NACE code, postcode, legal form, size and date. Organisations only, no API keys, no scraping.

- **URL**: https://apify.com/ai_solution/eu-company-registry-search.md
- **Developed by:** [MB AISolution](https://apify.com/ai_solution) (community)
- **Security:** Limited permissions
- **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

from $4.00 / 1,000 company records

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

## EU Company Registry Search: France SIREN & Norway Brreg (One Schema, Open Data)

**Search official company registers of France (INSEE Sirene, about 26 million companies) and Norway (Brreg Enhetsregisteret) and get the same JSON schema for both.** The Actor uses the **open government APIs** of the two registries: no scraping, no proxies, no API keys. Each result is one organisation with registry ID, name, legal form, status, creation date, activity code (NAF / NACE), address, size (employees or band), VAT status and, for France, the latest published revenue and net result. Built for B2B lead generation, KYB / supplier checks, market analysis and AI agents. **Organisations only: sole traders, directors and owners are never returned.**

More registers on the same schema (Czech Republic, Poland) are planned once their terms of use are verified.

### What you can do

- **Industry lead lists**: `activityCodes = ["62.01Z"]` + `departments = ["75"]` returns active French software companies in Paris (with revenue where published).
- **New Norwegian companies**: `incorporatedFrom = 2026-09-01` + `activityCodes = ["62.1"]` returns newly registered IT companies, newest first.
- **KYB / supplier check**: look up a company by name or by SIREN / organisasjonsnummer and read its legal form, status, address and VAT status.
- **Cross-border comparison**: `countries = ["FR","NO"]` and one name returns matches from both registers in one dataset.
- **Feed AI agents / RAG**: one schema, stable field names, official record link on every result.

### Input

```json
{
  "countries": ["FR", "NO"],
  "nameQueries": ["ovh"],
  "activityCodes": [],
  "postalCodes": [],
  "onlyActive": true,
  "maxItems": 50,
  "maxItemsPerCountry": 25
}
```

| Field | Description |
|---|---|
| `countries` | `FR`, `NO`. Default `["FR"]`. |
| `nameQueries`, `nameMatch` | Company names (any matches). FR: all words must appear in the company name / trade name / acronym. NO: `startsWith` (default) or `contains`. |
| `registryIds` | SIREN (FR) or organisasjonsnummer (NO). |
| `activityCodes` | FR: full NAF rev.2 code with letter (`62.01Z`). NO: NACE code or prefix (`62`, `62.1`, `62.100`). |
| `postalCodes` | FR 5 digits, NO 4 digits. |
| `departments` (FR), `municipalities` (NO) | Department codes (`75`, `2A`) or kommunenummer (`0301`). |
| `legalForms` | FR: INSEE legal-category codes (`5710` SAS, `5499` SARL, `9220` association). NO: form codes (`AS`, `ASA`, `NUF`, `STI`). |
| `companySizes`, `onlyAssociations` | FR: `PME`, `ETI`, `GE`; associations only. |
| `minEmployees` | NO: minimum number of employees (0, 1 or more than 4). |
| `onlyActive` | Default `true`: skips ceased (FR) and bankrupt / dissolving (NO) companies. |
| `incorporatedFrom`, `incorporatedTo` | `YYYY-MM-DD`. NO: registration date, newest first. FR: creation date, applied to the up to 10,000 results returned for your other filters. |
| `maxItems`, `maxItemsPerCountry` | Hard caps on billed results. |

Each country needs at least one filter (a name, ID, activity code, postal code, ...) - the Actor will not dump a whole register.

### Output

```json
{
  "recordType": "company",
  "country": "FR",
  "registryId": "424761419",
  "registryIdType": "SIREN",
  "name": "OVH",
  "tradeName": "OVHCLOUD",
  "legalFormCode": "5710",
  "legalForm": "SAS",
  "status": "active",
  "incorporationDate": "1999-10-15",
  "activityCode": "63.11Z",
  "activityCodes": ["63.11Z", "63.10Y"],
  "employeesBand": "1,000-1,999",
  "companyCategory": "ETI",
  "addressLine1": "2 RUE KELLERMANN",
  "postalCode": "59100",
  "city": "ROUBAIX",
  "region": "59",
  "countryCode": "FR",
  "latitude": 50.691629331,
  "longitude": 3.202261085,
  "vatNumber": "FR22424761419",
  "vatRegistered": true,
  "establishmentCount": 33,
  "headquartersId": "42476141900045",
  "financialYear": 2025,
  "revenue": 976044000,
  "netResult": 23558000,
  "currency": "EUR",
  "url": "https://annuaire-entreprises.data.gouv.fr/entreprise/424761419",
  "source": "INSEE Sirene via recherche-entreprises.api.gouv.fr (DINUM)",
  "license": "Licence Ouverte / Open Licence 2.0 (Etalab). Source: INSEE Sirene via API Recherche d'entreprises (DINUM)",
  "scrapedAt": "2026-10-02T12:00:34.701Z"
}
```

Fields a register does not publish are `null` (for example `employees`, `website`, `shareCapital` are Norwegian fields; `employeesBand`, `revenue`, `latitude` are French). Dataset views *Companies* and *Errors* are available in Apify Console. Problems (a register is down, missing filter) are written as free `error` records.

### How much does it cost?

Pay per event: **0.004 USD per company** (4.00 USD per 1,000) plus a start fee of 0.00005 USD per run. Error records are free. Platform usage is included in the event price.

| Scenario | Results | Approx. cost |
|---|---|---|
| Test run (`maxItems` 5) | 5 | 0.02 USD |
| Name check of one company in both registers | about 5 | 0.02 USD |
| Weekly list of new Norwegian IT companies; if 40 per week | 40 per run | 0.16 USD/run, about 0.70 USD/month |
| Industry list: French companies with NAF 62.01Z in 2 departments | 500 | 2.00 USD |
| Large export | 10,000 | 40.00 USD |
| One run with default settings (`maxItems` 25) | max 25 | max 0.10 USD |

**Cost control:** `maxItems` is a hard cap on billed results per run; the Actor also stops at your run's *maximum cost per run* setting. Records withheld for privacy (sole traders) and error records are never billed.

### Why this Actor (vs. alternatives)

Other Store Actors cover single registers (for example `dltik/pappers-sirene-scraper`, `seemuapps/pappers-sirene-scraper`, `studio-amba/recherche-entreprises-scraper` for France). This one puts **France and Norway on one schema** (and more registers are planned), uses the **official open-data APIs** (no scraping, no proxies), adds **filters that matter for sales and KYB** (activity code, postcode, size, legal form, creation date), includes **French revenue and net result where published**, and is deliberately **privacy-first**: sole traders, directors and role holders are not returned. It does not offer director data, financial statements or filings - use a paid Actor or the registers' own services for that. Check each Actor's Store page for its current price and fields. (Based on public Store listings, 2026-10-02.)

### Use it from n8n, Make, code and AI agents

- **n8n / Make**: schedule "Run Actor" weekly with `incorporatedFrom` set dynamically, then send each item to Google Sheets, Slack or your CRM.
- **API**:

```bash
curl -X POST "https://api.apify.com/v2/acts/ai_solution~eu-company-registry-search/run-sync-get-dataset-items?token=$APIFY_TOKEN" \
  -H 'Content-Type: application/json' \
  -d '{"countries":["NO"],"activityCodes":["62.1"],"incorporatedFrom":"2026-09-01","maxItems":20}'
```

- **MCP / AI agents**: available through the Apify MCP server (`https://mcp.apify.com`, tool `ai_solution/eu-company-registry-search`). The fully described input schema lets an agent answer "which IT companies were registered in Norway this month?" in one call.

### Scheduling and webhooks

1. In Apify Console open *Schedules*, create e.g. `0 7 * * 1` (Mondays 07:00 UTC) and add this Actor with your filters.
2. Add a **webhook** for `ACTOR.RUN.SUCCEEDED` (Actor *Integrations* tab) to your endpoint or an n8n/Make *Webhook* node; the payload contains `resource.defaultDatasetId`.
3. Read `GET https://api.apify.com/v2/datasets/<defaultDatasetId>/items?token=...` and forward new `registryId`s. A schedule uses a fixed input, so set `incorporatedFrom` dynamically (n8n expression or API) for "since last week".

### Changelog

- **1.0.0** - First release: France (Sirene) and Norway (Brreg).
- **1.0.3** - Fix: starting the Actor with the default input (no filter) no longer ends as FAILED; it finishes with a clear message and no charge. Console prefill now searches "ovh".

### Support / Issues

Found a bug or want another register? Open a ticket in this Actor's **Issues** tab in Apify Console.

### Data sources, licences and attribution

| Country | Source | Licence / terms |
|---|---|---|
| FR | INSEE Sirene database via *API Recherche d'entreprises* (recherche-entreprises.api.gouv.fr, DINUM) | Open access; data under Licence Ouverte / Open Licence 2.0 (Etalab). Please cite the source: **INSEE (Sirene)**. The API allows at most 7 requests per second per IP. |
| NO | Bronnoysundregistrene, Enhetsregisteret open data API (data.brreg.no) | Norsk lisens for offentlige data (NLOD) 2.0. Please cite the source: **Bronnoysundregistrene**. |

Each record carries `source` and `license`. The Actor identifies itself in the `User-Agent` with a contact address and keeps to about 2.5 requests per second. It is not affiliated with or endorsed by INSEE, DINUM or the Bronnoysund Register Centre. Registers are provided "as is"; use the official services for legal certificates. You are responsible for complying with data-protection and marketing law (GDPR, e-privacy) when you use company data.

### Limitations and privacy

- Two countries today. Czech ARES and Polish KRS are not included yet (terms of use / lookup-only API still to be verified).
- **Organisation-level data only.** France: sole traders (legal category 1xxx), indivision and de-facto partnerships (21xx, 22xx), entities flagged as sole proprietorships and units that are not fully publicly diffusible are withheld; the `dirigeants` (directors) data of the API is never read. Norway: sole proprietorships (ENK) and single-person registrations (PERS) are excluded; roles (board members, managers) and founders are never requested. A company's own name can still contain a person's name (for example "Dupont Conseil SARL").
- Both APIs return at most 10,000 results per query. Narrow the filters (postal code, department, activity code, date) to get the rest. French sole traders are removed after the query, so a French query can scan more API results than it returns.
- French `activityCodes` must be exact NAF codes with the letter; Norwegian codes follow the current Brreg classification (for example 62.100).
- Data freshness is that of the registers (France: Sirene daily updates with some delay; Norway: daily).

# Actor input Schema

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

Which registries to query: FR (France), NO (Norway). Queried in the order given.

## `nameQueries` (type: `array`):

Company names to look for (any term matches). France: every word must appear in the company name, trade name or acronym (director names are not searched). Norway: see Name match mode.

## `nameMatch` (type: `string`):

Norway only. startsWith = the name begins with the text (fast type-ahead search, default); contains = free-text search of all words.

## `registryIds` (type: `array`):

Look up companies by number: SIREN (9 digits) for France, organisasjonsnummer (9 digits) for Norway.

## `activityCodes` (type: `array`):

France: full NAF rev. 2 codes such as 62.01Z (computer programming) - the French API needs the exact code with letter. Norway: NACE codes or prefixes as used by Brreg, e.g. 62 or 62.1 or 62.100 (the letter suffix is ignored).

## `postalCodes` (type: `array`):

Business postal codes of the registered address: 5 digits for France (75001), 4 digits for Norway (0150).

## `departments` (type: `array`):

France only: department codes such as 75, 69, 2A.

## `municipalities` (type: `array`):

Norway only: 4-digit kommunenummer, e.g. 0301 (Oslo), 4601 (Bergen).

## `legalForms` (type: `array`):

France: INSEE legal-category codes such as 5710 (SAS), 5499 (SARL), 9220 (association). Norway: organisation form codes such as AS, ASA, NUF, STI. Sole proprietorships are always excluded.

## `companySizes` (type: `array`):

France only: PME (small/medium), ETI (mid-cap), GE (large).

## `onlyAssociations` (type: `boolean`):

France only: return only associations.

## `onlyActive` (type: `boolean`):

true = skip ceased (France) and bankrupt / dissolving (Norway) companies.

## `incorporatedFrom` (type: `string`):

Norway: filters on the registration date in Enhetsregisteret, newest first (best for new-company lists). France: filters on the company creation date, but only among the (max 10,000) results the French API returns for your other filters, so combine with NAF code, department or postal code.

## `incorporatedTo` (type: `string`):

Upper date bound, same rules as above.

## `minEmployees` (type: `integer`):

Norway only: minimum number of employees (must be 0, 1 or more than 4).

## `maxItems` (type: `integer`):

Maximum number of company records returned in total (each is one billed result).

## `maxItemsPerCountry` (type: `integer`):

Optional cap per country so that one country does not use the whole budget.

## Actor input object example

```json
{
  "countries": [
    "FR",
    "NO"
  ],
  "nameQueries": [
    "ovh",
    "equinor"
  ],
  "nameMatch": "startsWith",
  "registryIds": [
    "424761419",
    "923609016"
  ],
  "activityCodes": [
    "62.01Z",
    "47.91B"
  ],
  "postalCodes": [
    "75001",
    "0150"
  ],
  "departments": [
    "75",
    "69"
  ],
  "municipalities": [
    "0301"
  ],
  "legalForms": [
    "5710",
    "AS"
  ],
  "companySizes": [
    "ETI",
    "GE"
  ],
  "onlyAssociations": false,
  "onlyActive": true,
  "incorporatedFrom": "2026-09-01",
  "incorporatedTo": "2026-09-30",
  "minEmployees": 10,
  "maxItems": 100,
  "maxItemsPerCountry": 50
}
```

# Actor output Schema

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

All records in the default dataset.

## `companies` (type: `string`):

Companies view of the default dataset.

## `errors` (type: `string`):

Errors view of the default dataset.

# 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 = {
    "countries": [
        "FR"
    ],
    "nameQueries": [
        "ovh"
    ]
};

// Run the Actor and wait for it to finish
const run = await client.actor("ai_solution/eu-company-registry-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 = {
    "countries": ["FR"],
    "nameQueries": ["ovh"],
}

# Run the Actor and wait for it to finish
run = client.actor("ai_solution/eu-company-registry-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 '{
  "countries": [
    "FR"
  ],
  "nameQueries": [
    "ovh"
  ]
}' |
apify call ai_solution/eu-company-registry-search --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,ai_solution/eu-company-registry-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/rIUguTtfl2zJNcVwv/builds/VndmUNWq17ntLVlrO/openapi.json