sirenic

Anticipating public-contract expiries

Answering a tender on the day it is published means arriving after those who prepared long before. Yet the end date of a running contract is public data: 205,534 contracts have an estimated end date within the next 18 months, 86,992 of them within the next 6. /v1/marches/expirations serves them, filterable.

See a real response (free) Get the quote for /v1/marches/expirations

A window, a segment, a department

The window is set from 1 to 24 months (fenetre_mois), the segment by CPV prefix (cpv=45 for works, for instance) and the area by department. The response returns the buyer, the incumbent holders, the amounts and a framework-agreement flag, sorted by end date, 50 per page.

The framework-agreement flag deserves attention: an expiring framework agreement is not re-tendered like an ordinary contract, and its expiry often opens a wider window.

End dates are estimates: they are computed from the notification date and the declared duration in the French public-procurement open data. This is not an official re-tendering calendar, and some upstream rows are incomplete. Read it as commercial prioritisation, not as a binding deadline.

The measured foundation, and the part it misses

1,438,513 contract rows are in the database, 1,434,656 of them linked to a holder identified by company number, across 27,563 distinct public buyers. The most recent notification ingested is dated 2026-09-29.

One trap in this source, measured and worth knowing: the contract identifier is unique per buyer only, and tens of thousands of identifiers are shared between different buyers. Any deduplication on the identifier alone merges distinct contracts. Our routes account for this; if you reprocess the raw data yourself, key on buyer + identifier.

The three other routes of the same job

Know the buyer before the meeting

/v1/acheteur/{siret}/profil returns their buying habits: contract counts and amounts, activity by year, top CPV segments, ranked incumbent suppliers with their contracts expiring within 18 months, framework-agreement share, average number of bids received (competitive intensity) and median data-publication delay.

Know who wins on your segments

/v1/entreprise/{siren}/concurrents-marches starts from a company number, derives its top 5 CPV segments over the last 5 years, and returns the rivals that won on those same segments over the last 3 years, with contract counts, amounts and shared segments.

Read a company's track record

/v1/entreprise/{siren}/marches-publics returns contracts already awarded to a company: buyers, amounts, dates, procedures, aggregates and recent contracts with their estimated end date. It is also a supplier-due-diligence angle: a provider whose whole revenue comes from a single buyer carries concentration risk.

A method that fits in four calls

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. 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

RoutePriceSampleWhat it returns
/v1/marches/expirations$0.05free sampleUpcoming French public-contract EXPIRATIONS, the predictive layer over DECP open data: contracts whose estimated end date falls inside your window (fenetre_mois, 1-24 months), filterable by CPV prefix (cpv=45) and department, with buyer, incumbent holders, lot number, declared subcontracting, and amounts flagged firm price or ENVELOPE (call-offs, subsequent contracts, tranches, framework ceiling). Anticipation BEFORE publication. 50 per page.
/v1/acheteur/{siret}/profil$0.02free sampleProcurement profile of a French public buyer (SIRET): contract counts and amounts, activity by year, top CPV segments, incumbent suppliers ranked with their contracts expiring within 18 months, framework-agreement share, average bids received per tender (competitive intensity) and median data-publication delay: the buying habits a bidder wants before a sourcing meeting. From DECP open data.
/v1/entreprise/{siren}/concurrents-marches$0.02free sampleWho wins French public contracts on the SAME CPV segments as a given company (SIREN): top rival contractors over the last 3 years, with contract counts, total amounts and shared segments. Competitive intelligence for public-procurement bidding, from DECP open data. The company's own top-5 CPV segments (last 5 years) define the comparison scope.
/v1/entreprise/{siren}/marches-publics$0.01free sampleGovernment contracts won by a French company, from the official DECP open data: buyers, dates, procedures, estimated end date, lot number, joint holders, CCAG, price type, advance, amendments, declared subcontracting. Each amount is per contract or LOT, excl. VAT, over its full duration, flagged firm price or ENVELOPE (call-offs, framework ceiling: 43% of rows). Totals as two bounds: raw, and deduplicated when one award is published twice. Awarded contracts, not open calls.
/v1/entreprise/{siren}/marches-publics-ue$0.02free sampleEuropean public procurement awards won by a French company, from TED (Tenders Electronic Daily, EU Publications Office), government contracts and tenders: buyer, country, subject, notice-level amount, CPV codes, official notice link, co-winners proven legal persons (others counted, unnamed). Matching by SIREN/SIRET only, spaced variants included. Coverage: eForms award notices since 2023-10-25, above EU thresholds; ~57% carry a usable national identifier: an empty list is not proof of absence.

Contract end dates are estimates, computed from the notification date and the declared duration. This is not an official re-tendering calendar.

Frequently asked questions

Is this an alert on published notices?

No, quite the opposite. Alerts on published notices tell you when everyone else is told. Here you start from running contracts and their estimated end, to position yourself before publication.

Are EU contracts covered?

Yes, through a dedicated route: /v1/entreprise/{siren}/marches-publics-ue, on the European perimeter. It is not the same source as the French data and the two do not overlap exactly.

Why an estimated date rather than the real end date?

Because the source publishes a notification date and a duration, not an end date. Reconstructing it is a computation, and we say so rather than presenting the result as official data.

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.

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

Read next

Volume figures on this page were measured in our database on 2026-10-18. They are dated snapshots, not live counters. · OpenAPI · llms.txt · Full route catalogue and pricing