PolDex is the first dedicated insurance truth layer with 99%+ benchmarked accuracy across 56 insurance extraction schemas.

PolDex delivers 99%+ benchmarked accuracy across the full 56-schema insurance extraction universe, turning raw documents or parser output into evidence-backed, schema-controlled data.

99%+ accurateBenchmark ->Parser-neutralCompatibility ->
Insurance extractionPolicy package review
02 / 145
PDX-2703
In Progress

Extract policy package into evidence-backed JSON

Resolve the declarations, endorsements, limits, named insured, and source pages before the result is delivered to the broker workflow.

PolDex created the extraction job from processor upload - 2min ago

Schema engine added labels Commercial GL and Evidence required - 2min ago

broker

Need the policy limits, AI endorsement status, and the exact page citations for the client file.

agent

@ PolDex can you run this against commercial_gl and return JSON, CSV, and XLSX artifacts?

PolDex AgentOn it

Estimating credits for 18 pages...

Running commercial_gl schema checks...

Writing deterministic JSON with evidence array...

Insurance documents still break modern software

Insurance operations depend on long PDFs, COIs, endorsements, claims packets, schedules, requirements packets, and inconsistent carrier language. The hard part is not reading text. The hard part is turning it into trusted insurance data.

1.0Problem->
COI.pdfPolicy evidencepage 3
endorsement.pdfEndorsement clauseCG 20 10
schedule.pdfVehicle scheduleitem 14
manual reviewFields disagree across pages

Policy number, limit, endorsement, named insured, and date evidence must be resolved before data can move.

re-key

verify

escalate

reconcile

Schema universe visible here, four release-ready cards underneath

The homepage can show the full insurance schema registry at a glance. The numbered cards underneath stay focused on the first four release-ready schema families, while /schema carries the deep per-schema pages.

2.0Schemas->
Registry56 insurance schema contracts

56 release-ready schemas. The full universe has cleared the 99% release gate.

Commercial P&C15/15 release-ready

commercial_glcommercial_autoworkers_compcommercial_propertyumbrella_excessprofessional_linescyberd_and_oeplicrimeinland_marinecargoenvironmentalsuretybuilders_risk

Consumer / Personal Lines10/10 release-ready

personal_autohomeownersrenterscondopersonal_umbrellalifehealthdisabilitytravelpet

Document Primitives9/9 release-ready

coipolicy_declarationendorsementschedulebinderquoterenewalcancellationapplication

Claims9/9 release-ready

fnolloss_runclaim_packetadjuster_reportrepair_estimatemedical_billeobsettlementsubrogation

Benefits4/4 release-ready

group_healthgroup_lifegroup_disabilitystop_loss

Reinsurance3/3 release-ready

reinsurance_treatyfacultative_certificatebordereaux

ACORD6/6 release-ready

acord_25acord_125acord_126acord_127acord_130acord_140

GET /v1/schemas
{
  "total": 56,
  "hardened": 56,
  "hardening": 0,
  "families": [
    {
      "family": "Commercial P&C",
      "schemas": 15,
      "hardened": 15
    },
    {
      "family": "Consumer / Personal Lines",
      "schemas": 10,
      "hardened": 10
    },
    {
      "family": "Document Primitives",
      "schemas": 9,
      "hardened": 9
    },
    {
      "family": "Claims",
      "schemas": 9,
      "hardened": 9
    },
    {
      "family": "Benefits",
      "schemas": 4,
      "hardened": 4
    },
    {
      "family": "Reinsurance",
      "schemas": 3,
      "hardened": 3
    },
    {
      "family": "ACORD",
      "schemas": 6,
      "hardened": 6
    }
  ],
  "schema_page": "/schema"
}

One extraction engine across API, processor, and agents

LLMs made documents readable. FastScript makes insurance documents reliable. Developers call the API. Operators use the processor review cockpit. Agents use MCP, CLI, OpenAPI, and machine-readable discovery. Every output is scoped to the requested schema.

3.0Interfaces->
Search or run a command...
1POST /v1/extract
2Open processor batch
3mcp.call extract_policy
4poldex extract policy.pdf
curl https://poldex-api.plain-water-cd0f.workers.dev/v1/extract \
  -H "Authorization: Bearer $POLDEX_API_KEY" \
  -F "schema=commercial_gl" \
  -F "file=@policy.pdf"

Not a workflow suite, not a horizontal parser

Horizontal document AI is broad. Workflow AI tries to own the operating system. Brokerages sell distribution. PolDex stays vertical: insurance document truth infrastructure that plugs into the systems people already use.

4.0Positioning->
AlternativeDefault motionPolDex
Horizontal document AI

Broad parsing

Insurance-native truth state

Workflow AI platforms

Own the workflow

API infrastructure boundary

Brokerages

Sell distribution

Power broker and carrier systems

Manual ops

Review and re-key

Evidence-backed JSON output

Benchmark the result, then deliver it where work happens

Extraction infrastructure needs operational proof. PolDex exposes readiness, schema benchmarks, evidence rules, credit estimates, webhooks, and export artifacts.

5.0Monitor->
Release-ready schemas56
99% gate target100+
Health checks200
Export formats4

benchmark report updated

status ready passed

credits estimated

artifact exported

Structured JSON with evidence attached

PolDex does not just return text. Each extraction resolves policy facts into deterministic JSON with evidence, conflicts, confidence, source pages, guardrail state, and export-ready artifacts for the requested schema only.

JSONResult exports->CoreFastScript->
policy.pdfpages 1-18
Commercial General Liability
Named insuredNorthstar Builders LLC
Each occurrence$1,000,000
General aggregate$2,000,000
Evidence marker: declarations page, endorsement CG 20 10
{
  "schema_id": "commercial_gl",
  "policy": {
    "named_insured": "Northstar Builders LLC",
    "policy_number": "GL-2026-8841",
    "effective_date": "2026-01-01"
  },
  "limits": {
    "each_occurrence": 1000000,
    "general_aggregate": 2000000
  },
  "evidence": [
    { "field": "each_occurrence", "page": 3 },
    { "field": "additional_insured", "form": "CG 20 10" }
  ],
  "conflicts": [],
  "quality_guardrail_passed": true,
  "artifacts": ["json", "csv", "xlsx"]
}

Changelog

View all->

Start

Initialize access and run your first insurance extraction.

Use the docs, processor, or agent interface. PolDex keeps the same backend contract across every entry point.

Get startedDocumentationAgent interface