If you onboard, pay or sell to businesses in France and Spain, you need to know that each company exists, what it's called, what state it's in, and where that answer came from. The official registers have the answers, but in two different systems, two languages and two very different formats. Fuentio is a company verification API that reads both and returns one format, with the official source and the check date on every answer. This page explains what it does, what it returns, what it costs, and what it doesn't do.
Product facts as of 10 October 2026. Fuentio's API is opening soon; examples are real recorded answers.
Short answer: Fuentio is a REST API and MCP server for verifying French and Spanish companies from official registers. Look up a French company by SIREN, SIRET or VAT number, or a Spanish company by registry sheet, or search either by name. Each answer gives the legal name, legal form, status, registered office, activity and officers (names and roles) in one schema, with the register's original wording, normalised codes, the source, its licence and the check time. A lookup costs 1 unit; the free key gives 100 units a month.
What you'll learn
- What Fuentio checks, and against which official sources
- What a verification answer contains
- How identifiers and name searches work
- What it costs, and how to start
- What it doesn't do
What does Fuentio verify, and against which sources?
| Country | Official source | Look up by | Coverage |
|---|---|---|---|
| France | The State's company search API (INSEE Sirene, INPI RNE) | SIREN, SIRET, VAT number | The public register |
| Spain | The BORME, section A, published by the BOE | Registro Mercantil sheet | Companies with a registered act since 6 October 2025 |
Both: search by company name, with postcode or town to narrow it down. Details: how we read French data and how we read the BORME.
What does a verification answer contain?
Every answer has three parts: data (the record), meta (source, check times, stale, a request ID) and error (null when all went well). A trimmed real answer for a French company:
{
"data": {
"id": "FR-SIREN-441639465",
"name": {"original": "RENAULT"},
"legal_form": {"original_label": "SA nationale à conseil d'administration", "elf_code": "1NF1", "category": "public_limited_company"},
"status": {"value": "active", "original_label": "Active", "as_of": "2025-12-06"},
"registered_address": {"postal_code": "92100", "locality": "BOULOGNE-BILLANCOURT", "country": "FR"},
"activity": {"original_code": "64.20Z", "nace_rev2": "64.20", "label_en": "Activities of holding companies"},
"provenance": {"source": "fr_recherche_entreprises", "last_verified_at": "2026-10-05T14:02:11Z"}
},
"meta": {"source": "fr_recherche_entreprises", "stale": false},
"error": null
}The same fields, in the same places, for a Spanish company, plus its dated BORME acts with links to the official documents. Why that matters: your code reads one schema, your compliance team reads the register's own words, and your auditor sees where each fact came from. See provenance on every answer.
How do identifiers and searches work?
- Identifiers are checked first. A SIREN with a wrong check digit gets
invalid_identifier, free, without calling any source. - Lookups match exactly. A lookup only returns a company whose identifier matches the one you asked for.
- Searches return candidates. A name search returns records with their identifiers and addresses; you choose. We never pick one silently.
- Errors say what to do next:
not_found,id_scheme_not_supported(for example a Spanish NIF),rate_limited,quota_exceeded,upstream_unavailable.
See how we identify a company.
Two ways to use it: REST or MCP
- REST for your backend: onboarding forms, CRM enrichment, supplier checks.
- MCP for AI agents: connect Claude, Cursor, VS Code or ChatGPT to the same data, with the same source and check date in every answer. See connecting an AI agent to the registers.
What does it cost?
Units, priced per call: a lookup is 1 unit, a search 2 units, the coverage list is free, and errors are free except not_found on a well-formed number (1 unit, because it's a real answer).
| Plan | Price per month | Units per month |
|---|---|---|
| Free | €0 | 100 |
| Starter | €49 | 5,000 |
| Growth | €149 | 20,000 |
| Founding Partner (first 10 customers, price locked 12 months) | €99 | 20,000 |
| Business | €499 | 100,000 |
Prices are in euros; VAT may apply. Details and the FAQ are on the pricing page, and the full explanation in pricing explained.
Who uses a company verification API?
- Fintechs and payment providers verifying merchants at onboarding, then re-checking them before payouts.
- Marketplaces checking sellers at sign-up, so a ceased company can't open a shop.
- B2B SaaS pre-filling and checking company details in a sign-up form from a SIREN.
- KYB and RegTech teams automating the registry step of their checks. See the registry step of KYB.
- Finance and procurement teams cleaning customer and supplier files before invoicing.
- AI agents answering company questions with a source they can cite.
In every case the pattern is the same: an identifier goes in, an official record comes out with its source and date, and a person handles the unclear cases.
Why one format matters
Without one format, a team serving both countries writes two integrations, two sets of status rules and two sets of field names, and its compliance file has two shapes. With one schema, a French SAS and a Spanish S.L. arrive in the same fields, with their original wording kept and normalised codes next to it. See normalising company data.
How to evaluate it in an afternoon
- Pick 20 real companies from your own customer or supplier file: some French, some Spanish, a few you know have ceased.
- Look each one up and compare the answers with what your team knows.
- Check the hard cases: a ceased French company, a Spanish company in liquidation, a sole trader who may not be public, a typo in a SIREN.
- Read the provenance on each answer and ask your compliance team whether it's enough for your file.
- Estimate your units from your real volume. See pricing explained.
If the hard cases come back honest (ceased, in liquidation, not found, invalid) rather than optimistic, you've learned most of what matters.
What doesn't it do?
Being clear about this is part of verifying properly:
- Register facts only. No annual accounts, no ownership chains, no ratings or scores of any kind.
- No look-ups by Spanish tax number (NIF): the BORME doesn't publish it.
- No guessed statuses: a Spanish company without a status-defining act is
unknown, never "active". - France and Spain only today. See what we cover.
How do you start?
Fuentio's API is opening soon. Become an early tester: free early access before launch, and direct input on the roadmap. Use the form below.
Limits. Product facts and prices as of 10 October 2026; check the pricing page for the current terms. Spanish coverage is event-based, from 6 October 2025. Fuentio returns what official registers publish, with its source; it doesn't assess a company's solvency or replace your own compliance judgement.
Frequently asked questions
Is there a company verification API for France and Spain?
Yes. Fuentio verifies French companies from INSEE Sirene and INPI RNE data, and Spanish companies from the BORME, in one format with the source and check date on every answer.
Can I verify a company by SIREN with an API?
Yes. A lookup by SIREN, SIRET or French VAT number costs 1 unit and returns the legal name, form, status, address, activity and officers.
Does Fuentio work with AI agents?
Yes, through its MCP server, with the same data and provenance as the REST API.
How much does a company verification API call cost?
With Fuentio, a lookup is 1 unit; plans run from a free key (100 units a month) to Business (€499 for 100,000 units).
Sources
- API Recherche d'entreprises, documentation: recherche-entreprises.api.gouv.fr
- BOE, BORME daily gazette: boe.es
- INSEE, definition of the SIREN number: insee.fr