Prepare French invoice file
prepare_french_invoice_fileUse when you are about to invoice or pay a FRENCH company and must verify the supplier before payment: onboarding, first invoice, first payment, or bank details that just changed. The French e-invoicing mandate applies from 1 September 2026 (receiving obligatory for every VAT-liable company; issuing phased: large and mid-sized companies 1 September 2026, SMEs and micro-enterprises 1 September 2027), so every French counterparty has to be checked. ONE call returns the whole agent-side file: legal identity & obligation dates, the computed intra-EU VAT number verified LIVE against VIES, an IBAN FORM check (ISO 13616 structure + mod-97 key) with the bank identified from official registries when iban is supplied, and a deterministic verdict pret_a_facturer (true/false) whose reasons come from a CLOSED list, each tagged blocking or informational and traced to its source. A VIES outage yields an honest informational reason, never a false invalid. Not a payee verification, and the verdict says so where the decision is read: with an iban supplied, verdict.non_verifie sits NEXT TO pret_a_facturer and names what is never checked — the account's existence and the holder's name. An IBAN on a published list of known documentation samples is flagged by the informational reason iban_exemple_documentation, whose absence is not proof of the contrary (the verdict stays green: such an IBAN is well-formed; the account's existence is not tested). The response is Ed25519-signed and carries provenance[] — one entry per block served, with the official register, its licence and its as_of date — so the decision stays auditable offline months later. Paid via x402 ($0.03 in USDC or EURC).
Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| iban | No | IBAN of the account you are about to pay (spaces and dashes tolerated). Supplying it adds the structure check and the bank identification, and lets the verdict block on iban_invalide; omitting it yields the informational reason iban_non_fourni | |
| siren | Yes | 9-digit SIREN of the French counterparty being checked — the customer you will invoice or the supplier you will pay (digits only, no spaces) | |
| api_key | No | Optional Sirenic API key (srn_live_…) to pay with prepaid credits instead of x402 — no wallet needed. Get one at https://api.sirenic.eu/compte. Ignored when x_payment is provided (the signed payment wins). On insufficient balance the tool returns a credits error, not an x402 quote. | |
| x_payment | No | Optional signed x402 PAYMENT-SIGNATURE header value. Omit to receive the payment quote. |
Output Schema
| Name | Required | Description | Default |
|---|---|---|---|
| hint | No | How to settle the quote, present when payment_required is true. | |
| quote | No | The signable x402 payment requirements when payment_required is true: {x402Version, accepts[]} where each entry carries scheme, network, amount, asset and payTo (USDC and EURC options at the same numeric amount). Sign one entry and call again with `x_payment`. | |
| resultat | No | The endpoint's JSON response when payment_required is false. Paid responses carry `source`, `disclaimer` and an Ed25519 signature; KYB, batch KYB, sanctions, intelligence and the five invoicing tools (prepare_french_invoice_file, prepare_european_invoice_file, prepare_french_einvoicing_recipient, verify_iban_bank, validate_eu_vat_number) also carry a `provenance` array — one entry per block served, with the official register, licence, version, `as_of` date and `precision_as_of` (what that date means). Codes are documented at GET /v1/provenance/registres (free). | |
| payment_required | Yes | True when this response is an x402 payment quote instead of data: settle one of the quote's `accepts` options and call the tool again with `x_payment`. |