Any image in.
Your JSON out.
Send one page and one schema. What comes back is your JSON, checked field by field, with every field it missed named.
01 · the call
Live in one call.
Write the shape, send the bytes. That is the whole integration.
- 01
Describe what you want
One JSON Schema. Its descriptions are the prompt, so there is nothing else to write.
- 02
Send the image
One bearer call. The answer holds the fields, or says the read is still running.
- 03
Read the verdict
Your JSON, checked against that schema, with every field it missed named.
02 · the middle
Three messages. Nothing hidden.
You are always on the left and we are always on the right, so a message only ever travels one way: toward whoever is waiting for it.
what one call leaves you with
- accepted
- a snap id, before anything is read
- status
- REGISTERED, EXECUTING, COMPLETED
- result
- the fields, plus any violations
- kept
- a hash and the result, never the image
03 · around the read
Everything around the read.
The read is one call. Tenants, keys, history, billing and support are already built, and each card opens the page that explains it.
One project, one schema
We open it, write version 1 and hand you the key in a single call.
readA key you copy once
Shown when it is made. This console keeps no copy, so nobody can leak one.
readSchema versions
Every save appends a version. A snap keeps the version it ran against.
readDelivery you choose
Poll on your interval, or take a signed webhook you can probe first.
readA workbench per project
Paste the key, drop an image, read the verdict. Same call your server makes.
readNumbers you can trust
Usage and history come from us, where the reads are billed. No second count.
read- call to open a project
- 1
- SDKs to install
- 0
- the window we hold
- 10 s
- requests a minute
- 100k
04 · the price
100 credits free. Then $2 per 100.
No subscription, no seats, nothing expires. Sign in, send a page, keep the JSON.
one tier per project: fastbalancedbest
Describe the page and the console drafts the schema. You edit the draft. what a credit is →
05 · the proof
Read carefully, by people who ship.
From the first partners on the free allowance. Each quote is one project's opinion of one document type, not a logo wall.
“We deleted a prompt, a retry loop and a validator. The one call that replaced them returns the fields or says which one failed.”
backend leadinvoicing · receipts and statements
“The violation list is the feature. It tells us the scan missed the total, not that the read failed.”
data engineerlogistics · proof of delivery
“Started on the hundred free credits, shipped on a top-up. No call with sales.”
founderbookkeeping · purchase orders
Your fields, on the first page.
Send a document you know the answer to. The JSON back is the one your integration gets.
Start with one image →