Rank your customers by risk and be alerted the day one enters insolvency proceedings

“Rank my customers by risk and monitor the 30 most exposed.” You have a customer file and two questions: which ones may not pay you, and how to be alerted if one of them enters insolvency proceedings. Give Claude the list, by SIREN: Sirenic computes each one's default-risk score, the same as for a single company, sorts the lines into baskets and returns, for the exposed basket, the quote for its monitoring. Monitoring checks the official notices every day: a proceeding is reported to you at the latest on the working day after its publication in the BODACC, never in real time.

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

What the response says

Claude calls Sirenic's get_french_company_default_risk_batch tool, on the connector (https://api.sirenic.eu/mcp/connecteur) or on the public MCP server (https://api.sirenic.eu/mcp), which serves the /v1/score/defaillance/lot route. The response gives one line per SIREN, and the batch summary in the head:

• the score, class, confidence and model version of /v1/score/defaillance/{siren} for the same company: one scorecard, never a second one;
• a basket, from a closed list, derived from the class: expose (risque_eleve, risque_tres_eleve, defaut_avere and procedure_en_cours), a_surveiller (vigilance), sain (sain), non_evaluable (indetermine), cessee (cessee); a ceased company goes to the cessee basket whatever its class, and is never proposed for monitoring;
• the at most three scorecard axes that weigh most (motifs_principaux) and the set of axes read: two scores computed on different axes are not ranked against each other, the response puts them in separate groups;
• for a non_evaluable line, its cause (aucun_exercice, ratios_absents, siren_inconnu, identite_incomplete), counted per cause in the head in non_evaluable_par_cause;
• qualite_exercice_reference, when the accounts the score rests on need checking (a year copied onto the next one, for instance): read it before the score;
• in the head, the size of each basket and chainage.surveillance: the whole expose basket, in served order, with the quote for its monitoring over 30 days.

No officer is served, and a sole trader comes back without a name. The batch line returns the class, the drivers and the number of axes read; each company's full scorecard is read through /v1/score/defaillance/{siren}.

Being alerted: what monitoring does and does not do

The chaining names the /v1/surveillance/creer route (create_surveillance_watch tool) and the list of exposed companies. To monitor only the first ones, pass the first SIRENs of chainage.surveillance.parametres.cibles: the quote becomes their number times $0.05. Monitoring is a separate route, paid separately. It checks the official sources every day, including the BODACC insolvency notices, and reports a change by signed webhook, by e-mail digest, or when you poll the watch with its token.

This is not real time. Sirenic only sees a proceeding once the judgment is published in the BODACC, a few days after it was handed down, and monitoring reports it at the latest on the working day after that publication. Nothing from before the watch was created is reported. Webhook delivery is not yet proven in live conditions: the watch can always be polled, free of charge, with its token.

What an arbitrary file gives

Measured on 2026-10-03 on a copy of the database, two samples of 5,000: on active legal entities picked at random, 86.46% of the lines would come back non_evaluable, for lack of published accounts; among commercial companies, 71.5% have no published accounts in our database. On companies that file their accounts, 63.4% of the lines go to the sain basket, 16.88% to a_surveiller and 19.72% to expose. The measurement did not read the BODACC: ongoing proceedings are not counted in it.

A file of business customers that file their accounts gets ranked; a file of associations or very small entities stays largely non-assessable, and the response says so line by line, with the cause.

A purchased example

Bought on 2026-10-08 on the production service, over x402, for $0.14: a batch of two SIRENs. A company that files its accounts comes back in the sain basket, its score computed on eight axes; a legal entity with no published accounts at all comes back in the non_evaluable basket, cause aucun_exercice, checked against the BODACC like the other one. No line is exposed: the chaining to monitoring is empty, with its reason, aucune_cible_exposee. This page does not name these companies: the call, with its SIRENs, and the extract of the response are on the route's reference page.

Limits

• 2 to 100 SIRENs per call, comma-separated, duplicates removed; a malformed SIREN gets the batch refused, never billed.
• The BODACC is read for every line, live or from a reading less than 24 hours old kept in cache: if it does not answer, the whole batch is cancelled, never billed.
• No line scored (every SIREN unknown or incomplete in the register): refusal, never billed, each SIREN with its cause.

Price

$0.07 per requested SIREN, 2 to 100 SIRENs per call: $7 for a full batch. A non_evaluable line, unknown SIREN included, is billed with its cause. This route is not part of an account's 150 free calls a month: it is paid with prepaid credits (card top-up is not open yet), or over x402 for the same amount in USDC or EURC. Beyond 14 SIRENs, a batch goes over the $1 single-payment cap that x402 clients apply by default: raise it in your client. Monitoring is paid separately, $0.05 per company for 30 days. A refused or cancelled batch is never billed.

How you pay

Every route is paid per call, in USDC or EURC on the Base network, over the x402 protocol: no account to create, no API key, no subscription. 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, on 109 of 125 routes (the price list says which), 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

The default-risk score is a decision-support indicator. It is neither a solvency opinion nor a credit rating in the regulatory sense, and it guarantees no payment.

Frequently asked questions

Most of my customers are small entities: what is the point?

A line with no published accounts comes back in the non_evaluable basket with its cause, but keeps its BODACC check: an open proceeding still puts it in expose, and it enters the chaining to monitoring. The count per cause, in the head, tells you at once which share of the file gets ranked.

Do two companies with the same score carry the same risk?

Not necessarily: a silent axis does not penalise, and a score computed on fewer axes may understate the risk. The response groups the lines by set of axes before ranking them by score; read each line's number of axes before comparing two scores.

How do I monitor only the most exposed?

Keep the first SIRENs of chainage.surveillance.parametres.cibles, already ranked, and pass them to the create_surveillance_watch tool: $0.05 per company for 30 days, paid separately.

Take it further

No account to create, no key to request: the first step is free and shows you exactly what you would be buying.

See a real response (free) Get the quote for /v1/score/defaillance/lot Read the route reference Create an account: 150 free calls a month

Read next

• Monitoring a portfolio of customers or suppliers
• Assessing a customer's default risk
• Detecting insolvency proceedings

OpenAPI · llms.txt · Full route catalogue and pricing