Apify Public Data & Leads

French Company Registry Search (SIRENE)

french_company_search

Read-only

Search France's official company register by name, activity, department, or postal code to get SIREN/SIRET, legal status, address, workforce, revenue, and officers for due diligence or leads.

Instructions

Search France's official company register (SIRENE/INSEE) by name, activity, department, or postal code, and export SIREN/SIRET identifiers, legal status, headquarters address, workforce, revenue, and officers.

Behavioral Transparency:

Execution: Network call executed synchronously in the cloud via Apify Actor 'captainhandsome/french-company-search'.
Side Effects: Reads public sources and creates a billed Actor run and dataset on your Apify account.
Authentication: Requires APIFY_TOKEN environment variable.
Latency & Limits: Typical run duration is 10-30 seconds; timeout capped at 120 seconds.

Usage Guidelines:

When to use: Use for French corporate due diligence, company/officer lookups, industry (NAF) or regional market surveys, or B2B vendor verification in France.
When NOT to use: Do not use for US environmental compliance, US campaign finance, clinical trials, or FDA drug/device data.
Named alternatives: Use 'fec_campaign_finance_search' for US political funding, 'epa_facility_search' for environmental compliance, 'clinical_trials_search' for medical studies, or 'openfda_search' for FDA drug/device data.

Input Schema

TableJSON Schema

Name	Required	Description
`query`	Yes	Company name, trade name, or keyword to search for (e.g. 'boulangerie', 'Airbus').
`naf_code`	No	French NAF/APE economic activity code to filter by, e.g. '62.01Z'.
`department`	No	French department code to filter by, e.g. '75' or '13'.
`active_only`	No	Return only companies currently marked active. Defaults to true.
`max_results`	No	Maximum number of company records to retrieve. Defaults to 10.

Output Schema

TableJSON Schema

Name	Required	Description	Default
`run`	No
`error`	No
`status`	Yes
`results`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed31 schema fields changedv1.1.0Sep 15, 2026

addedInput schema / additionalProperties
```
Added value: +false
```
addedOutput schema / properties / error
```
Added value: +{
+  "type": "object"
+}
```

removedOutput schema / properties / results / description

Removed value: -"Collection of French company records from the SIRENE register."

changedOutput schema / properties / results / items / properties / employees / description

Previous value: -"Company-wide workforce size band."New value: +"Structured employees value returned by the French public company-data API backed by the SIRENE register."

addedOutput schema / properties / results / items / properties / employees / title
```
Added value: +"Employees"
```
changedOutput schema / properties / results / items / properties / employees / type
```
Previous value: -"string"New value: +[
+  "string",
+  "null"
+]
```

changedOutput schema / properties / results / items / properties / hq_city / description

Previous value: -"Headquarters city."New value: +"Structured hq city value returned by the French public company-data API backed by the SIRENE register."

addedOutput schema / properties / results / items / properties / hq_city / title
```
Added value: +"Hq City"
```
changedOutput schema / properties / results / items / properties / hq_city / type
```
Previous value: -"string"New value: +[
+  "string",
+  "null"
+]
```

changedOutput schema / properties / results / items / properties / legal_name / description

Previous value: -"Registered legal name of the company."New value: +"Structured legal name value returned by the French public company-data API backed by the SIRENE register."

addedOutput schema / properties / results / items / properties / legal_name / title
```
Added value: +"Legal Name"
```
changedOutput schema / properties / results / items / properties / legal_name / type
```
Previous value: -"string"New value: +[
+  "string",
+  "null"
+]
```

changedOutput schema / properties / results / items / properties / naf_code / description

Previous value: -"Main NAF/APE economic activity code."New value: +"Structured naf code value returned by the French public company-data API backed by the SIRENE register."

addedOutput schema / properties / results / items / properties / naf_code / title
```
Added value: +"Naf Code"
```
changedOutput schema / properties / results / items / properties / naf_code / type
```
Previous value: -"string"New value: +[
+  "string",
+  "null"
+]
```

changedOutput schema / properties / results / items / properties / name / description

Previous value: -"Organization or company name as published by the source."New value: +"Organization, company, facility or record name as published by the source."

addedOutput schema / properties / results / items / properties / name / title
```
Added value: +"Name"
```
changedOutput schema / properties / results / items / properties / name / type
```
Previous value: -"string"New value: +[
+  "string",
+  "null"
+]
```

changedOutput schema / properties / results / items / properties / revenue / description

Previous value: -"Most recently reported annual revenue."New value: +"Turnover for financials_year in whole euros, taken from the accounts filed with the commercial court. Only companies that file publicly have it."

addedOutput schema / properties / results / items / properties / revenue / title
```
Added value: +"Revenue (EUR)"
```
changedOutput schema / properties / results / items / properties / revenue / type
```
Previous value: -"number"New value: +[
+  "integer",
+  "null"
+]
```

changedOutput schema / properties / results / items / properties / siren / description

Previous value: -"9-digit SIREN company identifier."New value: +"Structured siren value returned by the French public company-data API backed by the SIRENE register."

addedOutput schema / properties / results / items / properties / siren / title
```
Added value: +"Siren"
```
changedOutput schema / properties / results / items / properties / siren / type
```
Previous value: -"string"New value: +[
+  "string",
+  "null"
+]
```

changedOutput schema / properties / results / items / properties / status / description

Previous value: -"Current company status, e.g. 'active'."New value: +"Current source-defined status of the organization, provider or study."

addedOutput schema / properties / results / items / properties / status / title
```
Added value: +"Status"
```
changedOutput schema / properties / results / items / properties / status / type
```
Previous value: -"string"New value: +[
+  "string",
+  "null"
+]
```
removedOutput schema / properties / results / items / required
```
Removed value: -[
-  "siren",
-  "name"
-]
```
addedOutput schema / properties / run
```
Added value: +{
+  "type": "object"
+}
```

addedOutput schema / properties / status

Added value: +{
+  "enum": [
+    "success",
+    "empty_unverified",
+    "partial",
+    "error"
+  ],
+  "type": "string"
+}

changedOutput schema / required

Previous value: -[
-  "results"
-]New value: +[
+  "results",
+  "status"
+]

Addedv1.0.11Sep 13, 2026

TDQS

A4.7/5.0

Behavior5/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Beyond the annotations, the description discloses execution as a synchronous network call, the billed Apify Actor run/dataset side effect, a required APIFY_TOKEN environment variable, and latency/timeout limits. These details add real behavioral context without contradicting the read-only and non-destructive hints.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is well-structured with clear headers and front-loaded purpose, then usage, side effects, auth, and limits. Every sentence earns its place; there is no filler or redundant restatement.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given that an output schema exists, the description does not need to document return values. It covers search scope, filters, side effects, authentication, latency, and exclusions, making it fully sufficient for correct invocation.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The input schema already describes all five parameters with meaningful details and coverage is 100%, so the description does not need to repeat them. The description's mention of search dimensions maps to the schema but adds no parameter-level syntax or constraints beyond it.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states a specific verb and resource: 'Search France's official company register (SIRENE/INSEE)' and enumerates search filters and exported fields. This clearly distinguishes the tool from US-focused sibling tools like us_business_entity_search and epa_facility_search.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description includes explicit 'When to use' and 'When NOT to use' sections with named alternatives for each excluded use case. An agent can reliably route between this tool and its siblings without inferring anything.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.