Machine-readable access

Insurance data API and MCP server for AI agents

Boleron EU publishes structured insurance data for 27 European markets — 1339 offers across 3 product lines, drawn from 699 insurer records, one per carrier per market. Served in 22 languages. You do not have to scrape it. There is a REST API, a hosted MCP server, and machine-readable manifests for both.

Sources last read: 2026-10-06 for the most recent record. Every offer carries its own date.

GET/api/v1/discover/en/austria/casco200
{  "meta": {    "locale": "en",    "detailLevel": "standard",    …  },  "markets": [    {      "country": "austria",      "insurerCount": …,      …    }  ],  "comparisons": [    {      "country": "austria",      "product": "casco",      "offers": [ … ]    }  ]}
JSONCORS-openCDN-cached

MCP server

Streamable HTTP, JSON-RPC 2.0. Read-only, no key, no account. It speaks MCP 2026-07-28 statelessly, including server/discover, and answers initialize for clients on 2025-11-25, 2025-06-18, 2025-03-26, 2024-11-05. Tool schemas are also listed in /.well-known/mcp.json, Boleron's own descriptor rather than a file the MCP specification defines.

https://boleron.eu/api/mcp/

Claude Desktop and other MCP clients take it as a remote server:

{
  "mcpServers": {
    "boleron": {
      "url": "https://boleron.eu/api/mcp/"
    }
  }
}

REST discovery API

Three levels of detail, widening as you narrow the subject. JSON, CORS-open, CDN-cached. The schema is OpenAPI 3.1.

/api/v1/discover/{locale}/

Every market, in one language

/api/v1/discover/{locale}/{country}

One market and its comparisons

/api/v1/discover/{locale}/{country}/{product}

One product's offers, with their sources

curl -s https://boleron.eu/api/v1/discover/en/austria/casco

locale is one of 22 language codes, country a market slug such as austria, and product one of mtpl, casco or travel.

Manifests

/llms.txt

What this platform is, in the form an LLM reads first

/llms-full.txt

The same, expanded: markets, products, endpoints, tools

/.well-known/mcp.json

MCP tool schemas

/.well-known/mcp-quote.json

Quote MCP tool schemas (indicative quotes)

/.well-known/openapi.json

OpenAPI 3.1 for the discovery API

What this data is, and is not

Every coverage figure, condition and price is compiled from insurer documents by an automated pipeline. Each coverage entry carries the URL it was read from; most key conditions do not yet. That is the whole of what the catalog asserts.

Not insurer-confirmed.

No carrier has signed off on any record. Where a record is still awaiting internal review, the page and the API say so rather than implying it was checked.

Prices are indicative.

None of them is a quote. A price without stated assumptions cannot be one, and the field says which it is.

An absence is not an exclusion.

A cover the documents do not establish reads as unknown, never as excluded. An exclusion is published only where a source states one.

A comparison site cannot establish cover.

Where a claim rests on a third-party source rather than the insurer’s own document, the API and the page both say so and the claim is not presented as established.

Sources can go stale.

Cited documents are hashed and re-checked; one that no longer resolves is marked rather than quietly left as a working link.

Questions

Do I need an API key to use the Boleron EU insurance API?
No. The REST discovery API and the MCP server are both public and read-only, and neither requires a key or an account.
What is the difference between the REST API and the MCP server?
The same data, reached two ways. The REST API returns JSON over HTTP and suits anything that can make a request. The MCP server exposes the same reads as tools an AI client can call directly, over streamable HTTP and JSON-RPC 2.0.
Which markets and insurance products does Boleron EU cover?
27 European markets and 3 product lines — motor third-party liability, motor casco and travel — across 1339 offers drawn from 699 insurer records. A record is one carrier in one market, so a group present in ten countries counts ten times. Served in 22 languages.
Is the insurance data confirmed by the insurers themselves?
No. Every figure is compiled from insurer documents by an automated pipeline and cites the document it was read from. No carrier has signed off on any record, and a record still awaiting internal review says so.
Can I use Boleron EU prices as insurance quotes?
No. Published prices are indicative and carry no stated assumptions, so none of them is a quote. Treat them as a starting figure to compare, never as a price offered to a customer.
How current is the data?
The most recent date on which a record's sources were read is 2026-10-06. Each offer carries the date its own sources were last read, and cited documents are hashed so a source that changes or disappears is marked rather than left looking live.

See the data

Using it

No key and no registration. Responses are cacheable and cached, so prefer a conditional request to a tight loop, and identify your client in a User-Agent so a problem can be raised with you rather than blocked. Access limits may be applied where use threatens the service.

If you cite us, cite the claim’s own source where one is given. The value here is that each fact names the document it came from, and a citation that points at Boleron instead of at the insurer’s wording throws that away.

Something wrong, missing, or a market you need? Boleron EU is built in the open and corrections are welcome.