Qover

Qover is a Brussels-based insurtech providing an API-first embedded insurance orchestration platform used across 32 European countries. Its modular platform lets brands, fintechs and insurers configure and distribute insurance products (travel, mobility, bike, purchase protection, accident, property) and run the full lifecycle from policy configuration and issuance through AI-assisted claims and multilingual customer care. Qover exposes REST APIs - a Claims API, a Policy API and a Document Asset Management API - secured with API keys, with a sandbox environment, configurable webhooks for claim status changes, and per-partner product configuration. Founded in 2016, Qover reports serving 440+ brands and insurers covering millions of people, and is an ISO-certified company with a Vanta-hosted trust center.

Qover is listed with 1 API on the APIs.io network: Embedded Insurance API. Tagged areas include Company, Insurtech, Insurance, Embedded Insurance, and Claims.

The Qover catalog on APIs.io includes 1 event-driven AsyncAPI specification.

Qover’s developer surface includes documentation, API reference, getting-started guide, engineering blog, pricing, signup flow, support, and 14 more developer resources.

🌐 Visit website 📡 Profile data on GitHub

49.0/100 developing ▬ flat Agent 21/100 agent aware Front door AI 4/6 moderate saas Full breakdown ↓
scored 2026-11-06 · rubric v0.27.0 · Show this score on your site →

AccessEnterprise

1 API 1 Agent Skills

Company Insurtech Insurance Embedded Insurance Claims Policy Fintech Belgium

Kin Score

Kin Score How this is scored →
scored 2026-11-06 · rubric v0.27.0

Composite quality — 49.0/100 · developing

Contract Quality 8.3 / 21

Developer Ergonomics 12.0 / 17

Access Clarity 10.3 / 17

Operational Transparency 1.7 / 11

Contract Governance 1.9 / 10

Discoverability 6.2 / 9

Regulatory Posture 3.9 / 15

Agent readiness — 21/100 · agent aware

Machine-Readable Contract 18 / 18

Agentic Access Contract 0 / 10

Documented Reversibility 0 / 6

MCP Server 0 / 12

Machine-Readable Auth 10 / 10

Idempotency 0 / 9

Stable Error Semantics 0 / 8

Request/Response Examples 0 / 7

Rate-Limit Signaling 0 / 7

Typed Event Surface 6 / 6

Agent Skills 5 / 5

Well-Known Catalog 0 / 4

Consent & Bot Identity 0 / 3

A2A Agent Card 0 / 8

Dry-Run / Simulate Mode 0 / 4

Delegated User Identity 0 / 6

Protected Resource Metadata 0 / 5

Registration Without a Human 0 / 6

Agentic Commerce Well-Known Document 0 / 5

Pagination 5 / 5

Distinct Operations 3 / 3

MCP Tool Quality 6 / 6

Regulatory Posture applies to this provider. Its tags matched the Insurance regime, so Regulatory Posture carries 15 points of the composite. If this regime is wrong for your business, say so on your provider repo — the applicability map is public and we will correct it.

Create-or-Update Ergonomics could not be measured. We hold no machine-readable contract for this provider to read, so there is nothing to measure a write surface against. Excluded rather than scored zero: never-measured and measured-empty are different facts. Publishing an OpenAPI is what makes this facet — and several others — scorable at all.

The six quality facets above are damped to 85 points between them, because the conditional facet above carries the other 15. That is why each facet's contribution is shown against a damped maximum: raising a quality facet moves the composite by 85% of its nominal weight, not 100%. The full arithmetic is at apis.io/rating/.

Show this score on your site.

It updates itself when the score changes. Paste this where you link to your API docs:

<a href="https://apis.io/providers/qover/"><img src="https://apis.io/badge/qover/card.svg" alt="Qover on APIs.io — Kin Score by API Evangelist"></a>

Other styles, a README pill and a shields.io endpoint are on the badge page.

Raise your score.

Agent readiness — checks not met, largest first (exact, from this profile):

MCP Server +12 pts — deployment.mode + probe verdict on the mcp/ manifest, not the pointer; an unprobed slug falls back to authorship
Agentic Access Contract +10 pts — agentic_access artifact present (x-agentic-access), graded by author
Idempotency +9 pts — OpenAPI mutating operations declare an idempotency key — a header, a request-body property, or a named de-duplication token whose own description says so (verified); else common[].type matches /idempoten/i (documented)
Stable Error Semantics +8 pts — OpenAPI $refs a shared error schema across 4xx/5xx responses (verified), else common[].type includes ErrorCatalog / ErrorCodes / DeclineCodes
A2A Agent Card +8 pts — a2a/-a2a.yml manifest, graded on conformance.grade against A2A 1.0.0
Rate-Limit Signaling +7 pts — OpenAPI responses document X-RateLimit-* / RateLimit headers (verified), else a rate_limits artifact or RateLimits link (documented)

9 more unmet checks in the Agent Readiness table above.

Kin Score — facets with the most composite points still available (weight × headroom):

Contract Quality scores 39.0 — up to +15.3 composite points
Operational Transparency scores 15.8 — up to +10.9 composite points
Contract Governance scores 18.2 — up to +9.8 composite points

Each check links to what satisfies it. Publish the artifact, or tell us where it already lives, and the score moves on the next scoring run.

Improve this rating by publishing the missing artifacts — every area above can be raised, and the full rubric is at apis.io/rating/. Every facet and dimension name above is a link: it opens that measurement's own page — what it means, the exact checks that feed it, how the whole catalog distributes on it, and the providers at the top of it. This rating is computed from the provider profile at artifacts.apis.io/qover/apis.yml: open an issue on github.com/api-evangelist/qover to ask a question or point us at an artifact you publish. Submit an artifact on GitHub — free → Manage your own listing — the Influence plan, $499/mo →

Markets this provider is in provisional

The Kin Score Market layer reads a provider inside its market: its position, and how deep its integrations go. Depth is only comparable within a position. Provisional and unweighted: not part of the Kin Score or agent readiness.

Market	Position	Depth	Registered MCP server	Declares compatibility
Insurance and Insurtech	undeclared	-	-	-

Registered MCP server and declares compatibility are report only — not weighted. Undeclared means we found nothing we can read, so there is no number: we never infer integrations.

Standards implemented 1

Standards this provider implements or carries. De facto ones are profiled and measured by the API Commons; formal ones come from the standards directory and are linked by the provider's own tags. The evidence column says how each claim was established — not that it was made.

Postman Collections

measured — observed by APIs.io (published)

APIs 1

Individual APIs this provider publishes, each with its own machine-readable definition.

Qover Embedded Insurance API

Qover's REST API for embedded insurance: a Claims API (file, retrieve, track status history, and download claim reports), a Policy API (manage policies and dynamically add/remov...

Agent Skills 1

Packaged agent skills for driving this provider's APIs from an AI assistant.

File and track a Qover insurance claim

AGENT SKILL

Qover API pricing

Pricing Plans 1

Published pricing tiers and plan structures.

Qover Plans Pricing

0 plans

PLANS

Service Levels 1

Uptime the provider promises or reports, as SLA4OAI. Read from its own pages; APIs.io runs no monitors.

Qover

SLA

FinOps 1

Cost, billing, and metering signals for API financial operations.

Qover Finops

FINOPS

Event Specifications 1

AsyncAPI definitions for this provider's event-driven and streaming APIs.

Qover Webhooks

ASYNCAPI

Security Posture 3

Authentication, domain security, vulnerability disclosure, and trust-center signals.

Qover Authentication

apiKey · 1 scheme

SECURITY

Qover Domain Security

TLSv1.3 · HSTS · DMARC

SECURITY

Qover Trust Center

ISO 27001

SECURITY

Resources

Get Started 3

Portal, sign-up, and the first successful call

DeveloperPortal

DeveloperPortal

GettingStarted

GettingStarted

SignUp

SignUp

Documentation 2

Reference material describing how the API behaves

Documentation

Documentation

APIReference

APIReference

Agent Surfaces 1

MCP servers, agent skills, and machine-readable catalogs

LLMsTxt

LLMsTxt

Design & Contract 2

Pagination, idempotency, versioning, errors, and events

Lifecycle

Lifecycle

Conformance

Conformance

Build 1

SDKs, sample code, and the tooling you integrate with

Postman

Postman

Access & Security 4

Authentication, authorization, and security posture

TrustCenter

DomainSecurity

Compliance

Authentication

Operate 2

Status, limits, changes, and where to get help

Support

Support

StatusPage

StatusPage

Commercial 4

Pricing, plans, and the legal terms of use

Plans

Pricing

TermsOfService

PrivacyPolicy

Company 2

The organization behind the API

Website

Website

Blog

Blog

Source (apis.yml)

aid: qover
name: Qover
description: Qover is a Brussels-based insurtech providing an API-first embedded insurance orchestration platform used across
  32 European countries. Its modular platform lets brands, fintechs and insurers configure and distribute insurance products
  (travel, mobility, bike, purchase protection, accident, property) and run the full lifecycle from policy configuration and
  issuance through AI-assisted claims and multilingual customer care. Qover exposes REST APIs - a Claims API, a Policy API
  and a Document Asset Management API - secured with API keys, with a sandbox environment, configurable webhooks for claim
  status changes, and per-partner product configuration. Founded in 2016, Qover reports serving 440+ brands and insurers covering
  millions of people, and is an ISO-certified company with a Vanta-hosted trust center.
url: https://raw.githubusercontent.com/api-evangelist/qover/refs/heads/main/apis.yml
x-type: company
x-source: vc-portfolio
x-backed-by:
- anthemis
x-tier: stub
x-tier-reason: portfolio-lead
deliveryModel:
  model: saas
  open_source: false
  commercial: true
  callable_host: false
  label: Hosted service · you call their endpoint
  confidence: medium
  source:
  - pricing
  generated: '2026-08-28'
  method: derived
accessModel:
  pricing: enterprise
  onboarding: unknown
  trial: false
  try_now: false
  public: false
  label: Enterprise
  confidence: medium
  source:
  - authentication
  - security
  - sandbox
  generated: '2026-11-06'
  method: derived
image: https://qover.com/favicon.ico
specificationVersion: '0.23'
created: '2026-07-17'
modified: '2026-07-20'
x-docs-platform: postman
x-docs-platform-confidence: high
x-docs-platform-checked: 2026-10-04
tags:
- Company
- Insurtech
- Insurance
- Embedded Insurance
- Claims
- Policy
- Fintech
- Belgium
tags_raw:
- Company
- Insurtech
- Insurance
- Embedded Insurance
- Claims
- Policy
- API
- Fintech
- Belgium
apis:
- name: Qover Embedded Insurance API
  description: 'Qover''s REST API for embedded insurance: a Claims API (file, retrieve, track status history, and download
    claim reports), a Policy API (manage policies and dynamically add/remove risk items), and a Document Asset Management
    (DAM) API for claim attachments. Authenticated with API keys in the request header, versioned in the URI path (v1), with
    configurable webhooks for claim status changes. Product/country behaviour is driven by per-partner product configuration
    (e.g. FINTECHX, BE).'
  humanURL: https://docs.qover.com/
  baseURL: https://api.sbx.qover.io
  tags:
  - Insurance
  - Claims
  - Policy
  - Embedded Insurance
  properties:
  - type: Documentation
    url: https://docs.qover.com/
  - type: APIReference
    url: https://docs.qover.com/
  - type: Postman
    url: https://docs.qover.com/
  - type: Authentication
    url: authentication/qover-authentication.yml
  - type: Sandbox
    url: sandbox/qover-sandbox.yml
  - type: Conventions
    url: conventions/qover-conventions.yml
  - type: Webhooks
    url: asyncapi/qover-webhooks.yml
  - type: X-MCPServerCandidate
    url: mcp/qover-mcp.yml
    note: 'Renamed from MCPServer 2026-09-03 (roadmap#247): the manifest self-describes as status: candidate — a tool list
      derived from the published API contracts, not an existing server. The scorer already read the manifest and reported
      mcp_server correctly; the MCPServer type was crediting the artifact-type surfaces with a server that does not exist.'
  - type: DataModel
    url: data-model/qover-data-model.yml
  - type: AgentSkill
    url: skills/_index.yml
common:
- type: Plans
  url: plans/qover-plans-pricing.yml
- type: Website
  url: https://www.qover.com/
- type: TrustCenter
  url: security/qover-trust-center.yml
- type: DomainSecurity
  url: security/qover-domain-security.yml
- type: DeveloperPortal
  url: https://docs.qover.com/
- type: Documentation
  url: https://docs.qover.com/
- type: APIReference
  url: https://docs.qover.com/
- type: GettingStarted
  url: https://www.qover.com/api-access
- type: Postman
  url: https://docs.qover.com/
- type: Blog
  url: https://qover.com/blog
- type: Pricing
  url: https://qover.com/pricing
- type: SignUp
  url: https://www.qover.com/api-access
- type: Support
  url: https://qover.com/get-in-touch
- type: TermsOfService
  url: https://storage.googleapis.com/qover-assets/documents/terms/Terms-of-use_EN.pdf
- type: PrivacyPolicy
  url: https://storage.googleapis.com/qover-assets/documents/policies/Privacy%20Policy_EN_v.04_2026.pdf
- type: StatusPage
  url: https://status.qover.com/
- type: Compliance
  url: https://trust.qover.com/
- type: Lifecycle
  url: lifecycle/qover-lifecycle.yml
- type: Conformance
  url: conformance/qover-conformance.yml
- type: Authentication
  url: authentication/qover-authentication.yml
- type: LLMsTxt
  url: llms/qover-llms.txt
maintainers:
- FN: Kin Lane
  email: kin@apievangelist.com
- FN: APIs.json
  email: info@apis.io
x-enrichment:
  date: '2026-07-20'
  status: enriched
  artifacts_added: 12
  pass: local-v1

Qover API — frequently asked questions

Does Qover have an API?

Yes. APIs.io lists 1 API from Qover, including Qover Embedded Insurance API.

How do I authenticate with the Qover API?

Qover uses bearer-token authentication (apiKey · 1 scheme). The details are profiled on APIs.io as Qover Authentication.

Is the Qover API ready for AI agents?

Qover has a Kin Score of 49.0 out of 100 (developing) and an Agent Readiness score of 20.7 (agent-aware), scored by API Evangelist on 2026-11-06.

Work with this as data

Every provider here is available over the APIs.io API and to AI agents over MCP.

MCP server

One button, every client — Claude, Cursor, VS Code and the rest.

https://apis.io/mcp

Tools for providers

9 MCP tools reach this

find_providersBrowse and filter every provider in the catalog.
get_provider_artifactsEvery artifact this provider publishes, grouped by type.
get_provider_operationsEvery operation across all of their OpenAPIs — one call instead of parsing every spec.
get_provider_toolsEvery MCP tool they ship, with the operation each wraps.
get_provider_evidenceHow each part of their score was established. Free — the basis for a claim should not sit behind it.
get_provider_ratingPRO — composite, band, trend and facet scores.
apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.
resolveTurn a domain, URL or GitHub org into the provider it belongs to.
find_cohortsEvery scored population of providers in the catalog.

All 92 tools →

Call it yourself

curl for this page

This provider

curl "https://apis.io/api/v1/providers/qover"

All providers

curl "https://apis.io/api/v1/providers?limit=25"

Every operation they expose

curl "https://apis.io/api/v1/providers/qover/operations?limit=25"

How their score was established

curl "https://apis.io/api/v1/providers/qover/evidence"

Calls without X-API-Key need no key. Calls with it need a paid plan — get a key.

Get an API key

Free tier, no form to fill in. Signing in shares your email address with us — we store it to create your key and to recognise you if you sign in with another provider. See our Privacy Policy and Terms.

GitHub Google LinkedIn

A second provider on the same verified email joins the account you already have.