Public-document and live-surface stories, not invented customers.
Case Studies
Proof Stories
Public-document case studies without fake customer claims.
These are not logo-wall customer stories. They show how PolDex behaves across live product surfaces: raw-document extraction, parser-output import, processor review, agent workflows, evidence grounding, schema scope, and FastScript guardrails.
Callable schemas behind the proof stories.
Still gated before the global 99% claim can activate.
No fake revenue, fake pilots, fake SOC, or fake customer deployment claims.
Start Here
Public Document ProofThe core extraction proof.
The first story shows the most important product behavior: schema-scoped insurance data with evidence, unresolved fields, conflicts, guardrail metadata, and export-ready outputs.
Commercial GL declarations to schema-scoped JSON
A Commercial General Liability declaration page is turned into policy identifiers, dates, carrier and insured identity, limits, evidence, unresolved fields, guardrail metadata, and export-ready artifacts.
Public-document proof case ->All Stories
How the same infrastructure appears to each user type.
Developers see API contracts. Operators see a review cockpit. Parser customers see an adjudication layer. Agents see MCP, CLI, OpenAPI, and discovery files.
Line-Specific Proof
Commercial auto evidence packet to limit and schedule data
Commercial auto packets contain symbols, combined single limits, hired/non-owned auto posture, vehicle schedules, drivers, and supporting evidence. PolDex keeps those facts separate from personal auto output.
Public-document proof case ->Operator WorkflowPolicy packet review without a custom dashboard
The processor turns PolDex from a pure API into a narrow operator cockpit: estimate, upload, process, inspect facts, review evidence, mark decisions, save notes, and download artifacts.
Live product surface case ->CompatibilityKeep the parser, add insurance truth
PolDex can operate underneath an existing parser. Customers send parsed markdown, text, JSON, tables, or parser events into FastScript for insurance-specific schema enforcement, evidence grounding, conflicts, and exports.
Integration proof case ->Agent WorkflowAgent-ready policy review with MCP, CLI, and OpenAPI
PolDex exposes schema discovery, classification, estimates, extraction, polling, artifacts, parser-output import, Reducto import, and benchmark status through agent-readable interfaces.
Agent interface case ->Method
What a PolDex case study is allowed to claim.
A case study can describe product behavior, public proof, schema boundaries, and benchmark posture. It cannot imply customer adoption, production volume, or universal accuracy until that evidence exists.