Insurance documents in. Verified data out.
Two models read every field and a judgement model settles where they disagree. Every value comes back with the quote and page it was read from; anything we aren't sure of is flagged for review, never guessed.
try
Try a document
No setup. Drop a policy, dec page or application and see everything we extract with our standard schema.
+ new
New workflow
An endpoint for your output: add one or more targets (your JSON, schema or form), test on sample documents, publish.
Workflows
each one is an API endpoint: POST /v1/jobs -F workflow=<id>// loading…
Admin
Needs you
what waits on us, worst first// loading…
Health
Money
Accounts
Support
tickets from customers · they get our replies by email; private notes stay hereDocument cuts
files cut into several documents in the last 30 days, requests to charge one as a single document, and files read as one that may hold severalOur changes
every change an admin made to an account, newest firstAccount
General
Delete this account
ownersAt once: its keys stop working, everyone is signed out of it, and any credit left is lost. Its data is erased after 7 days; until then, write to hello@extractinsurance.dev to undo it. Export first if you need anything.
Team
owners invite and remove people and change the account's settings · members do everything else: workflows, documents, API keys.
Billing
Credit
what's left of each payment, and every changeUsage
download CSVAPI keys
personal: each acts as the person who made itA key can do what its person can do here, for scripts, the terminal and AI agents: workflows, their keys, documents, usage. Not the team or other keys. It stops working when its person leaves the account. For production, use a workflow's key (its Connect step): it runs that workflow only. live: published versions · test: also a workflow's draft (
-F version=draft).show example
curl
Webhook signing
x-extract-signature: sha256=HMAC(secret, body)Every result we POST to your webhooks is signed with this account's secret. Check the signature before you trust the body.
whsec_…show example
verify (Node)
Data and privacy
We read a small share of your documents in the background to test new models and tune how fields are read. They're deleted on your normal schedule. This is how we lower your token cost and pick up more fields over time.
Account data
ownersThe settings, team, workflows with every version, key names, the results still kept, usage, billing and activity. Not the documents themselves.
Activity
who did what in the account · owners see thisYour sign-in
yours, in every account you're inYour first endpoint, in five steps.
Read a document, pick the shape you want back, check your fields, say what you receive, then name it and call it.
or set up a workflow by hand →Drop a document
pdf · png · jpg · docx · xlsx · csv · synthetic/anonymized documents only until provider retention is confirmed
Or Run Against Our Test Docs
Nothing to settle yet: you'll check the fields you receive in step 3.
Choose your output
the shape every document comes back inCheck your fields
every value with the quote and page it was read from · fix anything that's offWhat do you want to receive?
which values come back, and what a disputed field becomesName your workflow
creates it, publishes v1, gives you a live keyTargets
the output shapes you need from each document · read once, delivered in every shapeSample documents
2–5 documents from different carriers or layouts · each read once with this workflow · ~$0.70 eachReview
per target: where each field comes from, checked against your samples · changes save to the drafttrusted values only (accepted); everything else is null until reviewed
Connect
call the endpoint · results arrive per target in result.targetsAPI keys
A key only runs this workflow and reads its own results. live: published versions · test: also
version=draft.Webhook
Every finished run is POSTed here, signed with your account's secret (account page):
x-extract-signature: sha256=HMAC(secret, body). A webhook_url part on a job overrides it.Runs
production jobs through this endpoint · disputed fields wait in reviewSettings
decision policy is versioned (publish to apply) · retention applies to new runsDocument gatecheck what each document is before reading it. A refused document is charged only what the check cost (fractions of a cent) and is not an extraction. A filter for documents that don't belong, not a security control.
Per field: mark required or always review in the output table of step 03 (columns on the right).