Priced workload · Documents
Document extraction
Pull fields out of invoices, forms and agreements into structured data, and price each document.
Why the bill is hard to read
A document is many pages and pages are many tokens. The bill depends on how long the documents are and on how often the same instructions are sent again.
How AVELIN is used
Keep the field list and the instructions identical on every call. A repeated prompt prefix is billed at the cache read rate after the first call, so only the document itself pays the full input price. Start on the fast tier and send documents with missing fields to the pro tier.
Define
Write the field list and the output format once, and use them as the start of every request.
Extract
Send the document text, or page images, to avelin-fast. The fast tier accepts image input.
Check
Validate the output against your own rules. Missing or doubtful fields go to avelin-pro.
Store
Save the structured result together with the token counts for the document.
Tiers and list prices
USD per 1M tokens unless stated, list price as of 3 October 2026.
| Model or endpoint | Used for | List price |
|---|---|---|
avelin-fast | First pass on every document | $0.30 in, $1.20 out. Cache read $0.03. |
avelin-pro | Documents with missing or doubtful fields | $1.40 in, $4.40 out. Cache read $0.26. |
What to count
Cost per task = the sum, over every call in the task, of (input tokens × input price + output tokens × output price) ÷ 1,000,000. Add cache write and cache read tokens at their own rates, and add any web requests at their per-request price.
- Pages per document and tokens per page, from a sample of your own documents.
- Tokens in the repeated prefix compared with tokens in the document.
- How many documents need the second pass.
Count this workload on your own runs, or request a POC and we price one workload at list price beside your current bill.
Questions about this use case
What is "Document extraction"?
Pull fields out of invoices, forms and agreements into structured data, and price each document.
Which tiers does it use?
It uses avelin-fast, avelin-pro. Prices are in US dollars per 1M tokens, list price as of 3 October 2026.
How do I test it on my own workload?
A POC is a proof of concept on one of your workloads. It runs beside your current setup, with nothing in your production path, and ends in a cost-per-task report.
Bring one workload. See its cost per task.
Start with a POC on one of your workloads.