Clean a customer file by SIRET number

Cleaning a customer file by SIRET means tying each row to its company: its SIREN (the SIRET's first nine digits), head-office SIRET, status and VAT number. Ceased companies, duplicates and any SIREN with a wrong check digit are flagged. Without code: our Google Sheets template or the upload screen.

See a real response (free) Get the quote for /v1/identite/lot

Without code: the Google Sheets template or the upload screen

Two ways to complete your file without writing code, through the same route, /v1/identite/lot. Each reads from your columns the SIREN, the SIRET, the French VAT number, or the name and postcode of each row, sends only that, and adds its own columns on the right, all prefixed sirenic_: the resolution, the SIREN, the head-office SIRET, the status, the VAT number and its VIES status, duplicates over the whole file and rows to review. Each call sends at most the rows a free call admits; beyond the month's free quota, it is paid from your credits. A completed row is never sent again when completing, unless its input changes.

• The Google Sheets template. Open your file in Google Sheets, then Extensions, Apps Script: replace the content of Code.gs with the template's code, save and reload the spreadsheet. In the Sirenic menu: “Enter my key” (the key is kept out of the cells), then “Complete the file”. The instructions give every column and every error. No key yet: create an account.
• The upload screen. In your account, the Customer file tab reads a CSV or an .xlsx workbook in your browser: only the SIREN, SIRET, VAT number, or name and postcode of each row leave it. The plan gives the calls and the cost before the first call, nothing is sent without your click, and the completed file comes back as CSV; the screen itself states the maximum size of a file, in rows and megabytes. No account yet: create one.
• Both then offer “What has changed since my last pass”: resolved rows are sent again with the date of their last read (section “What changed since your last pass” below).

What Claude calls, and what it reads

“Enrich and clean my CRM: SIREN, VAT, address, ceased companies and duplicates.” A CRM base ages quietly: companies cease trading, others move, and the same company ends up entered twice. Which records point to a ceased company, or to the same company twice? And for the others, what are the SIREN, the head-office address and the VAT number? Before a campaign, paste the accounts export in Claude and ask: every record comes back at its rank, ceased companies and duplicates flagged, and an ambiguous name comes back with its candidates rather than with a choice made for you.

Claude reads the export and takes one line per record: the SIREN, the SIRET, the French VAT number, or the name and postcode when the line has no identifier. It calls the get_french_company_identity_batch tool, which serves the /v1/identite/lot route, 2 to 150 lines per tool call (the route takes 300: a full batch takes 2 tool calls). For each line, the answer gives:

• ceased companies: the status in the Sirene register, actif or cesse, and for a ceased company the cessation date when it is published; its VAT number is not sent to VIES (non_verifie, entreprise_cessee);
• duplicates: a line that points to a company already seen above, by its SIREN, the SIRET of one of its sites, its VAT number or its name, carries doublon_de, the rank of the first one; the batch head counts duplicates;
• for a resolved line: the SIREN, the head-office SIRET, the legal name, the head-office address, the VAT number and its VIES status (valide, invalide, indisponible, non_verifie);
• the resolution, from a closed list (resolu, a_confirmer, introuvable, siren_invalide, siren_inconnu, non_diffusible); an ambiguous name comes back a_confirmer with up to 5 candidates ranked by score;
• the line's rank and what was read; the typed name is never echoed.

The route says which line duplicates which and which company has ceased; it does not touch your CRM. Merging and archiving remain yours.

A five-line export

Five neutral lines, one per input form, taken from our reference set of companies: the second duplicates the first (another site of the same company), the third points to a ceased company, the last is an invented name. No customer data.

What comes back was read on 2026-10-09 with our test key, in Claude, on the Sirene stock of 2026-10-01; the VIES status is the one at the time of the call, or of a check less than an hour old kept in cache. These five lines fit in the 100 free lines a month of a verified account; outside them, they cost $0.015.

Limits, measured

• VAT is checked live on VIES, line by line, one at a time: in French business hours, VIES serves one verdict every 4 to 5 s and refuses concurrency; before pipelined checks, a full batch had 15 of 262 resolved lines checked; with them, outside business hours (23:51 UTC), 105 of 265; measured 2026-10-08. A line whose check could not start in time says so (non_verifie, budget_vies_epuise): run those lines again in a smaller batch, or outside business hours.
• A batch has 60 s, 40 s of which to find names. A name line whose index stage could not be served (time budget exceeded, or no index to serve it) says so (etages_abandonnes) and is never resolu; the batch head counts them. On the full batch of 300 names of 2026-10-08 (23:51 UTC), 9 lines of 300 said so.
• The cessation date is read live, for ceased lines only; when it is missing, the line says why: non_publiee, source_indisponible or budget_lot_epuise.
• 2 to 300 lines per call; the request line is capped at 11,000 bytes, that is 300 SIRENs or about 148 names of 63 characters; beyond that, a requete_trop_large refusal; beyond about 16 KB, an empty 431; neither is billed.

What changed since your last pass

“What has changed at these customers since my last pass?” With depuis (a past day or today), each resolu line also carries changements: what changed for its company since that day, read by the changes engine in BODACC and the local stocks (commercial-court decisions, French public contracts, establishments, cessation, licences, sanctions lists, RGE certifications, lobbying register). The line gives the verdict (nouveautes, rien_de_nouveau or lecture_incomplete), the totals per type, the three latest facts, the window actually read and lecture_complete; an unresolved or non-diffusible line says why it carries none (motif_sans_changements).

• Price: $0.01 per line with depuis instead of $0.003, every line at the call's price; the free quota of verified accounts applies with or without depuis.
• The get_french_company_identity_batch tool reads 20 lines per call with depuis (the route takes 300); the batch then has 90 s.
• A BODACC outage on a line is stated there (lecture_complete false, the block named in blocs_incomplets); a batch where no line could read BODACC is refused, never billed.
• European public contracts and industrial property are not read in the batch: the /v1/entreprise/{siren}/nouveautes route reads them, one company at a time. Officers are never served.

What the route does not do

It adds no contact: no e-mail address, no phone number, no named contact; that data is not in the official registers. It changes nothing in your CRM. It does not check the site a SIRET names: it reads its SIREN, the first nine digits, and returns the company's status and its head-office SIRET. It never chooses between two namesakes. A sole trader is never served as a candidate, and their SIREN line comes back without name or address.

What a cleanup costs

A verified account has 100 free lines a month on the batch, outside its 150 free calls, no credit debited: the five example lines cost nothing there. A batch over what is left of the month is paid in full. Beyond, or outside the free tier, the batch is billed $0.003 per line, duplicates included: $0.015 for the five example lines, $0.90 for a full batch of 300 lines, with prepaid credits (card top-up is not open yet), or over x402 for the same amount in USDC or EURC. A refused or unavailable batch is never billed.

The same batch, without an assistant

The five example lines, encoded the way the MCP tool encodes them; the API key is read from the SIRENIC_KEY variable.

# The five example lines, 2 to 300 per call
curl "https://api.sirenic.eu/v1/identite/lot?lignes=552032534%3B55203253400711%3BFR48056200454%3BAIR+LIQUIDE+CO2+EUROPE%7C75007%3BQXZJW+VKPRT%7C33000" \
  -H "X-Api-Key: $SIRENIC_KEY"

# Over MCP, on the connector https://api.sirenic.eu/mcp/connecteur (tools/call method),
# the key in an Authorization: Bearer $SIRENIC_KEY header, or Claude's OAuth connection
{"name": "get_french_company_identity_batch", "arguments": {"lignes": ["552032534", "55203253400711", "FR48056200454", "AIR LIQUIDE CO2 EUROPE|75007", "QXZJW VKPRT|33000"]}}

How you pay

Every route is paid per call, two ways, with no subscription: over x402, in USDC or EURC on the Base network, with no account and no API key; or with the API key of an account, which opens the free quota; /v1/identite/lot has 100 free lines a month, beyond that on its credits. Over x402, the first call returns a 402 quote your client settles, then replays the call. A failed call is never billed.

Open today: 150 free calls a month with an account, up to EUR 2 of value, on 122 of 129 routes (the price list says which), with 100 more free lines a month on batch identity, and pay-per-call over x402 (USDC or EURC), with no account except registry filings. Prepaid credits: card top-up is not open yet.

Paid responses are Ed25519-signed: you can later prove what was served to you, and when. The whole catalogue is free to read in the OpenAPI document and in llms.txt.

One call, end to end

# x402 client (npm): the 402 quote is settled and the call replayed automatically
npx x402-fetch https://api.sirenic.eu/v1/entreprise/552032534

# Or over MCP, in Claude Code / Cursor
claude mcp add --transport http sirenic https://api.sirenic.eu/mcp

# Or as a local server (stdio), with your key or an x402 wallet
claude mcp add sirenic -e SIRENIC_API_KEY=srn_live_... -- npx -y sirenic-mcp

Routes used and pricing

Frequently asked questions

My records only have a name and a town: does it work?

The head-office postcode is needed: name resolution runs at that postcode. Without it, go through the name search first ($0.002, within the monthly free calls), which returns a confidence score, then send the SIRENs found to the batch.

How is a duplicate spotted?

Two lines that point to the same company, whatever their form (SIREN, a site's SIRET, VAT number, name): the second carries doublon_de, and only the first carries the detail. Two sites of one company are therefore a duplicate for the route: you decide whether they are two accounts.

Is my base also used for invoicing?

The same route answers it with the same answer: the page “Prepare your customer base for French e-invoicing” starts from the question asked before the first e-invoice.

Take it further

The first step is free and shows you exactly what you would be buying, with no account or key; an account, with its API key, then opens the free quota; /v1/identite/lot has 100 free lines a month, beyond that on its credits.

See a real response (free) Get the quote for /v1/identite/lot Read the route reference Create an account: 150 free calls a month up to EUR 2 of value

Read next

• Prepare your customer base for French e-invoicing
• Building a B2B prospecting list
• Monitoring a portfolio of customers or suppliers

OpenAPI · llms.txt · Full route catalogue and pricing