Companies

What PolDex Is

The extraction layer behind insurance companies.

Companies should not rebuild parsers for every product line. PolDex gives teams one callable rail for insurance documents: classify, extract, defend with evidence, and deliver structured records to the system that already owns the workflow.

01

Input

Files, URLs, pasted text, email intake, signed links, processor uploads, and agent calls.

02

Contract

Schema selection, classifier routing, evidence rules, truth states, conflicts, and abstention.

03

Output

JSON, CSV, XLSX, ZIP artifacts, signed result links, webhook payloads, and connector events.

04

Expansion

The same interface expands from commercial P&C into consumer, claims, benefits, specialty, and global variants.

Fit

Built for companies that cannot treat insurance documents as loose files.

PolDex sits behind the workflow: documents enter from files, URLs, text, agents, email, or signed intake, then leave as structured records and downloadable artifacts. Commercial P&C is live first; the architecture is meant to expand across the insurance stack.

01

Submissions

Extract structured fields from broker packets, supplemental forms, and policy PDFs.

02

Compliance

Verify limits, named insureds, dates, exclusions, evidence, and missing fields at scale.

03

Procurement

Turn vendor certificates and insurance requirements into machine-checkable records.

04

Claims

Prepare FNOL packets and claim attachments for structured intake as claims schemas come online.

05

Agent workflows

Let agents estimate cost, choose schemas, process files, and export JSON, CSV, XLSX, or ZIP artifacts.

Surfaces

Use the same extraction rail through the surface your company needs.

API

POST /v1/extract for production document pipelines.

Processor

Batch processing surface for teams that need operational review.

Live Proof

Public proof surface for quick evaluation against backend configuration.

Credits

Prepaid usage model that keeps pilots and production spend bounded.

01

Self-serve evaluation

Teams can run live proof, use the playground, initialize access, and load credits before a procurement process starts.

02

Production integration

Engineering teams call the API directly, poll job state, receive connector events, and store signed artifacts downstream.

03

Operational processing

Ops teams can use Processor for batches while engineering keeps the same backend contracts and exports.

04

Agent-native usage

Agent companies can expose PolDex through MCP, CLI, OpenAPI, llms.txt, and schema discovery without building another parser.

Start with proof. Move into production when the workflow is ready.

Evaluate extraction quality publicly, initialize access, load credits, and wire PolDex into the company surface you already own.