Technical platform

An LLM that speaks insurance contract

General-purpose language models hallucinate coverage that does not exist and miss exclusions buried in endorsement schedules. Insurteam's extraction pipeline was designed around insurance contract structure from the ground up.

Architecture

How the pipeline is structured

Five components, each with a defined responsibility. Data flows from claim document through to settlement decision without human intervention for parametric cases.

INPUT FNOL payload + Policy PDF LLM Extraction clause identification coverage mapping condition parsing extracts clauses Policy Matching loss event mapping trigger verification exclusion check matches loss event Rules Engine parametric thresholds payout calculation sub-limit stacking applies rules OUTPUT Settlement Decision JSON settled
Performance data

Accuracy across the beta programme

Numbers from internal beta processing with early-access design partners. Indicative, not contractual.

94% Policy clause extraction accuracy across 150+ policy variants
~90 sec Median end-to-end settlement time for eligible parametric claims
< 2 sec Policy reading and clause extraction per document
99.8% Uptime on Growth and Enterprise plans (beta period)

Based on internal beta processing runs with early-access design partners. Numbers are indicative, not contractual guarantees.

API integration

A clean contract, no surprises

Insurteam exposes a REST API with three primary endpoints: claim submission, decision retrieval, and policy document upload. The contract is designed to fit in front of any existing claims management or policy administration system.

Webhooks notify your system when a decision is ready. The decision payload includes clause citations, confidence score, and structured payout data. Your system acts on the decision; Insurteam does not initiate payment.

  • REST API with OpenAPI spec
  • Webhook notifications on decision ready
  • Structured JSON decision with clause citations
  • Policy PDF and structured data submission
  • Full audit log accessible via API
  • Sandbox environment for integration testing
POST /v1/claims

{
  "fnol": {
    "claim_ref": "TRV-2026-04471",
    "loss_type": "flight_delay",
    "flight_id": "LX0284",
    "reported_delay_hrs": 5.2
  },
  "policy_doc_ref": "pol-doc-8823af"
}

200 OK
{
  "decision_id": "dec-9f4a2c",
  "status": "settled",
  "payout_amount": 180.00,
  "currency": "CHF",
  "clause_refs": ["§4.2.1", "§4.2.3"],
  "confidence": 0.97,
  "processing_ms": 1842
}

Get the full API documentation

Request sandbox access and the full OpenAPI specification during your demo call. We walk through integration scope and typical deployment timelines.

Book a Demo Read security details