LabHub

Blog

Embedded Insurance & API-first Insurance 2026 — Cover Genius, Sure, Trov, bolttech, Qover, Wakam, Tinubu, Vouch Deep Dive

한국어English日本語

Prologue — The end of "would you like to add insurance before paying?"

May 2026, Tokyo. I am about to confirm a Booking.com hotel reservation. A card appears: "Add trip cancellation cover for JPY 1,800?". One click, <5min purchase, the receipt and the policy PDF land in my inbox. No insurer brand was visible anywhere. In reality, Cover Genius wrote the policy, a Japan-licensed fronting carrier underwrote it, Booking.com supplied the UI, and any claim will route through Cover Genius and settle in seven days. The customer remembers "insurance I bought on Booking".

That is embedded insurance in 2026. Insurance is no longer a product; it is a by-product of another transaction. Buy a Tesla and cover travels with it. Become an Airbnb host and host liability attaches. Open the Uber driver app and time-on-app cover activates. Customers do not visit insurance landing pages. That is why Munich Re projects global embedded GWP at $1T market by 2030.

Two unlocks made it possible. First, API-first insurance infrastructure: Cover Genius, Sure, bolttech, Qover and others expose quote-bind-issue-claim as REST APIs. Second, licence sharing: Wakam, Tinubu, Accelerant operate as fronting carriers who rent regulatory capacity, while MGAs (Managing General Agents) design products without holding their own licence.

This guide draws the map: value chain, leading platforms, real API calls, and cases from Korea, Japan, Europe, and the US.


Chapter 1 · Definitions — distribution vs embedded vs MGA

ModelDescriptionExample
Traditional distributionCarrier to agency to consumer, dedicated pageGEICO, Samsung Fire Direct
BancassuranceSold over a bank counterKB Bank + KB Insurance
EmbeddedAuto-surface inside another transactionBooking trip cover, Tesla auto
Native embeddedConsumer buys without explicit awarenessAirbnb host liability
MGA (Managing General Agent)Designs, underwrites, settles claims, no licenceHippo, early Lemonade
MGA-as-a-ServiceMGA ops delivered as SaaSSure, bolttech
Fronting carrierRents its licence to MGAsWakam, Accelerant

Key 2026 trend: embedded is not a new distribution channel — it is a recombination of MGA-as-a-Service and fronting into a new value chain. Cover Genius and Sure are full-stack platforms, not pure distributors.


Chapter 2 · Four-layer value chain — Risk Capital, Carrier, MGA, Distribution

The embedded insurance value chain decomposes into four layers.

  1. Risk capital: balance sheet that pays claims — reinsurers (Munich Re, Swiss Re, Lloyd's syndicates) and primary insurers.
  2. Carrier: licence holder that issues policies — fronting carriers like Wakam, Tinubu, Accelerant, or traditional insurers.
  3. MGA (product and tech): product design, pricing, underwriting rules, claims orchestration — Cover Genius, Sure, bolttech.
  4. Distribution: customer touchpoint — Booking.com, Tesla, Zigbang, Toss.
LayerMargin takeCapital requiredRegulation
Risk capital0.5–3% (reinsurance fee)Very high (Solvency II etc.)Very high
Carrier (fronting)2–7% (fronting fee)HighHigh
MGA15–30% (commission + tech fee)LowMedium
Distribution10–25% (partner commission)Very lowLow

2026 reading: MGA-as-a-Service captures the largest margin, which is why Cover Genius and Sure are repeatedly named as IPO candidates.


Chapter 3 · Cover Genius — The engine behind Booking.com

Cover Genius started in Australia in 2014. In 2026 it powers insurance for Booking.com, Skyscanner, Shopee, Wayfair, and eBay Australia. The flagship product is XCover, a global policy administration platform.

Highlights:

Quote API example:

curl -X POST https://api.covergenius.com/v3/quotes \
  -H "Authorization: Bearer $XCOVER_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{
    "currency": "JPY",
    "country": "JP",
    "policy_type": "travel.cancellation",
    "policy_start_date": "2026-06-10",
    "policy_end_date":   "2026-06-17",
    "insured": [{ "first_name": "Taro", "last_name": "Yamada", "dob": "1988-04-12" }],
    "trip": {
      "destination": ["JP"],
      "value":   { "amount": "180000", "currency": "JPY" },
      "deposit": { "amount": "30000",  "currency": "JPY" }
    }
  }'

The response includes a quote ID, premium, coverage limits, and a wording PDF URL. Binding the policy is a single POST to /policies.


Chapter 4 · Sure — The MGA-as-a-Service champion in the US

Sure is based in Los Angeles, founded in 2015, with a 2023 Series E of $100M. Strengths are product breadth and a 50-state US licence footprint. Carriers like Chubb, Munich Re, and Markel are pre-contracted, so partners do not negotiate paper themselves.

Notable partners:

The differentiator is a no-code studio: partners model product lines, wording, and pricing in a GUI, and ship the storefront via a one-line web component such as <SurePolicy />. The average go-live timeline is six weeks.


Chapter 5 · Trov — Pioneer of personal on-demand and B2B pivot

Trov launched in 2012 with an on-demand consumer app that let users toggle cover on cameras, bikes, and laptops. The B2C unit economics never closed. In 2020 it pivoted to B2B.

Trov in 2026:

Lesson: B2C embedded insurance suffers from price sensitivity and low purchase frequency; B2B2C economics are dramatically better.


Chapter 6 · bolttech — Asia-born super-app for asset insurance

bolttech spun out of Pacific Century Group (PCCW) in Singapore in 2020. Valuation reached $2.1B in 2024. The wedge is licence coverage across 22 Asian markets and a strong device-insurance line that competes with Samsung Care+ and AppleCare.

Use cases:

bolttech also runs Exchange, an insurer and reinsurer matching marketplace. When an MGA needs capacity, it can request bids and pick the carrier with the best terms.


Chapter 7 · Qover — Europe's embedded insurance specialist

Qover is based in Brussels, founded in 2016. By 2026 it operates across 32 EU/UK jurisdictions. Notable partners:

API characteristics:

A typical integration is short:

import { QoverSDK } from '@qover/embedded-sdk'

const qover = new QoverSDK({
  partnerId: process.env.QOVER_PARTNER_ID,
  apiKey:    process.env.QOVER_API_KEY,
  locale:    'fr-BE',
})

const quote = await qover.quotes.create({
  product:    'gig-economy.rider-accident',
  insured:    { firstName: 'Marie', lastName: 'Dupont', dob: '1995-07-21' },
  coverage:   { start: '2026-06-01', end: '2026-12-31' },
  attributes: { country: 'BE', avgHoursPerWeek: 22 }
})

const policy = await qover.policies.bind({ quoteId: quote.id })
console.log(policy.documents.certificate) // PDF URL

Chapter 8 · Branch Insurance — The carrier that imports your existing policy

Branch is a US carrier headquartered in Ohio, founded in 2018. It sells bundled auto and home, but the onboarding UX is unusual. Upload a photo of an existing declarations page and an AI parser reads coverage limits, exclusions, and deductibles, then offers to migrate the policy in under five seconds.

2026 facts:

This is embedded by import: not creating a transaction, but lifting an existing policy into a new channel.


Chapter 9 · Hippo — The embedded home-insurance benchmark

Hippo was founded in 2015 in California and went public via SPAC in 2021. The thesis combines smart-home sensors with insurance: customers receive Kangaroo or Notion devices for free, and early detection of leaks and fires reduces claims.

Embedded strategy in 2026:

The insight: people are most receptive to insurance at the exact moment they recognise the new risk — "I am buying a home" is the highest-converting moment.


Chapter 10 · Wakam — The European licence-sharing champion

Wakam is a French carrier, founded in 1829, that pivoted entirely into a white-label fronting business in 2017. In 2026 it is one of the most important infrastructure providers in embedded.

What Wakam does:

A fronting flow expressed in YAML:

fronting_carrier: Wakam SA
licence_jurisdictions: [FR, DE, IT, ES, NL, BE, PL, ...]
ceding_party:
  mga: Cover Genius EU Ltd
  product: travel.cancellation.v3
  fee_structure:
    fronting_fee_pct: 4.5
    ceded_premium_pct: 92.0   # passed onwards to reinsurers
    mga_commission_pct: 18.0  # what the MGA earns
reinsurers:
  - name: Munich Re
    share_pct: 60
  - name: Swiss Re
    share_pct: 40
regulatory:
  solvency_ii: true
  idd: true
  reporting_frequency: monthly

The point: an MGA can sell insurance without becoming a carrier. Licence sharing is arguably the single biggest enabler of embedded.


Chapter 11 · Tinubu — APIfying B2B trade credit insurance

Tinubu is Paris-based, founded in 2000. Its core product is a SaaS platform for trade credit insurance. Carriers such as Allianz Trade (formerly Euler Hermes), Coface, and Atradius use Tinubu for policy management and underwriting.

2026 embedded play:

A reminder that embedded is not only B2C. B2B embedded has equally large potential.


Chapter 12 · Vouch Insurance — Embedded for tech startups

Vouch is based in San Francisco, founded in 2018, targeting tech startups. It packages the policies a venture-backed company needs (D&O, E&O, EPL, Cyber, Tech E&O, Crime) and prices them dynamically.

Embedded channels are unusual:

The TAM is narrow but unit economics are strong: average annual contract value $10K~$50K with renewal above 90%.


Chapter 13 · Lemonade Car — Tesla integration and IoT insurance

Lemonade launched in 2015 as a P2P insurance brand and announced a deeper Tesla partnership in 2025. In 2026:

This is the future of AI- and IoT-driven embedded insurance. Pricing, claims, and underwriting all operate on telemetry. Privacy concerns persist; California and EU jurisdictions have settled on opt-in regimes.


Chapter 14 · Open Insurance API — Standardisation in motion

EIOPA (the European Insurance and Occupational Pensions Authority) published the Open Insurance framework in 2024. As of May 2026, v1.1 is GA — think of it as the insurance equivalent of PSD2.

Key endpoints:

# Open Insurance API v1.1 — core endpoints
openapi: 3.0.0
info:
  title: Open Insurance API
  version: 1.1.0
servers:
  - url: https://openinsurance.eiopa.example/v1
paths:
  /quotes:
    post: { summary: Create quote (multi-line) }
  /policies:
    post: { summary: Bind policy from quote }
    get:  { summary: List policies for consumer }
  /policies/{id}/claims:
    post: { summary: First Notice of Loss (FNOL) }
  /consumers/{id}/coverage:
    get:  { summary: Consent-based coverage summary across carriers }
  /carriers:
    get:  { summary: Registered carriers and supported lines }
security:
  - oauth2_pkce: [openid, policies.read, claims.write]

The FCA in the UK and MAS in Singapore are working on parallel standards. By 2027–2028 embedded insurance APIs are likely to converge on a single open spec.


Chapter 15 · Korea — Zigbang lease bonds, Toss mini-insurance, KakaoPay

Korean embedded insurance grew dramatically between 2023 and 2026.

CompanyEmbedded productChannel
ZigbangLease deposit bond (Jeonse refund cover)Listing page
TossPet, riding, and health mini-insuranceCheckout and lifestyle tab
KakaoPayEveryday mini-insurance (travel, mobility, sport)KakaoTalk transfer flow
11st and CoupangAppliance warranty, lost-package coverCheckout
Uber and Delivery HeroRider accident coverRider app

Zigbang's lease deposit bond is a particularly interesting case. After the Jeonse fraud wave, the company partnered with SGI Seoul Guarantee to surface a "bond available" badge on listings, where renters can apply with a single click.

Toss mini-insurance shines with a day-by-day activation model. Toggling cover on a hiking morning binds protection just for that day — a textbook lifestyle insurance pattern.


Chapter 16 · Japan — LINE Insurance, Lifenet, Rakuten Insurance

Japan has a large but historically slow-moving insurance market. The 2026 wave is finally accelerating.

Cultural note: Japanese consumers read policy wording carefully, so embedded surfaces must surface 重要事項説明 (important matters explanation) clearly. Transparency, not pure simplification, is the operating principle.


Chapter 17 · Embedded vs distribution vs MGA comparison

AttributeTraditional distributionMGAEmbedded
Purchase momentDedicated search and consultationDedicated pageBy-product of another transaction
User awareness"I bought insurance""I bought insurance"Often "I do not remember"
Revenue modelAgency commission 25–40%MGA commission 15–30%Partner commission 10–25%
Pricing powerHeld by primary carrierPartly with MGADriven by partner UX
Claims NPSLow (30–40)MediumHigh (60+)
New-product launch6–18 months6–12 weeks2–6 weeks
Unit economicsDecent (margin over volume)DecentStrong (rides partner traffic)

Chapter 18 · Partner verticals and embedded products

Partner categoryEmbedded productExamples
Travel and OTACancellation, baggage, medicalBooking, Expedia, Skyscanner
AirlinesDisruption, lost-luggageANA, Lufthansa, KLM
Auto and mobilityCrash, warranty, subscription coverTesla, Carvana, Lyft
Delivery and gig economyRider injury and liabilityUber Eats, Deliveroo, Baemin
Property and rentalHost liability, lease bondAirbnb, Vrbo, Zigbang
E-commerceAppliance warranty, lost-packageAmazon, Shopify, Coupang
Fintech cardsPurchase protection, travelRevolut, N26, Toss
Health and wellnessSports injury, gym accidentStrava, Peloton
EducationTuition refund coverCoursera, Udemy

The pattern: the higher the partner's transaction frequency, or the more the transaction itself carries risk, the higher the embedded conversion rate.


Chapter 19 · MGA-as-a-Service operating model — what is sold as SaaS

Cover Genius, Sure, and bolttech offer the following modules to partners:

  1. Product catalogue: 60+ pre-modelled insurance lines with wording and pricing curves
  2. Underwriting engine: rule and ML-driven auto-bind
  3. Pricing: real-time quote APIs (under 200 ms)
  4. Policy issuance: multilingual PDFs, digital signatures
  5. Claims: FNOL to evaluation to payout automation, NPS 60+
  6. Compliance: IDD, NAIC, MAS reporting baked in
  7. Carrier network: 60+ licence jurisdictions through fronting
  8. Reinsurance: Munich Re and Swiss Re capacity matching
  9. Data and BI: loss ratio, conversion, NPS dashboards

Partners only integrate the front-end widget. That is why new products go live in two weeks to three months.


Chapter 20 · Data model — Core entities for embedded insurance

-- Embedded insurance core schema (simplified)
CREATE TABLE quotes (
  id            uuid PRIMARY KEY,
  partner_id    text NOT NULL,
  product_line  text NOT NULL,           -- travel.cancellation, rider.accident ...
  insured_party jsonb NOT NULL,
  coverage      jsonb NOT NULL,
  premium_cents bigint NOT NULL,
  currency      char(3) NOT NULL,
  expires_at    timestamptz NOT NULL,
  created_at    timestamptz NOT NULL DEFAULT now()
);

CREATE TABLE policies (
  id              uuid PRIMARY KEY,
  quote_id        uuid REFERENCES quotes(id),
  carrier_id      text NOT NULL,         -- Wakam, Accelerant, ...
  fronting_fee    numeric(6,4),
  effective_date  date NOT NULL,
  expiry_date     date NOT NULL,
  status          text NOT NULL          -- ACTIVE, LAPSED, CANCELLED
);

CREATE TABLE claims (
  id           uuid PRIMARY KEY,
  policy_id    uuid REFERENCES policies(id),
  fnol_at      timestamptz NOT NULL,
  loss_amount  numeric(12,2),
  status       text NOT NULL,             -- OPEN, INVESTIGATING, PAID, DENIED
  paid_amount  numeric(12,2),
  paid_at      timestamptz
);

Loss ratio = SUM(paid_amount) / SUM(premium_cents). Embedded insurance typically targets 50–65%. Too low signals overpriced products (customer complaints); too high means losses (carrier walk-aways).


Chapter 21 · Claims automation — FNOL to settlement

Traditional claims average 14 to 28 days. Embedded insurance now targets 24 to 72 hours. The mechanics:

Cover Genius averages a seven-day claim cycle with auto-adjudication above 60%. That is what produces NPS 65+.


Chapter 22 · Regulation — IDD, NAIC, MAS, FSS, JFSA

Embedded insurance regulation varies sharply by jurisdiction.

2026 trend: DORA (EU Digital Operational Resilience Act) now covers embedded insurance infrastructure too. ICT risk management and outsourcing reports are mandatory.


Chapter 23 · Anti-patterns — Seven ways embedded insurance fails

  1. Shipping only a single tickbox: customers do not know what they bought, claims drop, NPS collapses
  2. Single-carrier dependency: a capacity withdrawal can shut the channel overnight
  3. No multilingual wording: instant compliance failure in EU and APAC
  4. Outsourcing claims UX to a separate app: NPS drops to 30s; claims must stay in the embedded channel
  5. Quarterly loss-ratio monitoring: fraud clusters slip through unnoticed
  6. Ignoring distributor licences: fines and stop-sell orders in the US and EU
  7. Inadequate reinsurance capacity: a large catastrophe sinks the carrier

Chapter 24 · 90-day embedded insurance rollout plan


Chapter 25 · 2027 outlook — Open Insurance and AI underwriting

By 2027 embedded insurance bifurcates along two axes.

  1. Open Insurance standardisation: the EU, UK, and Singapore force a PSD2-style standard. Consumers can list every policy in a single screen. The barrier for embedded entrants drops further.
  2. AI underwriting and claims: LLM-based wording parsing, single-photo claim adjudication, monthly dynamic pricing from vehicle telemetry. Lemonade and Hippo lead in the US; Toss in Korea and LINE Insurance in Japan close the gap.

Risks: AI bias against specific demographics, data privacy, and tight reinsurance capacity. How regulators and capital markets respond determines how fast the $1T market materialises.


References

Comments

No comments yet.

Sign in to leave a comment