Extraction estimate · prices checked 2026-11-03
Claude Opus 5.5 vs Levanto Sage 2 for field extraction
List prices
| Model | $ per M input | $ per M output | Source |
|---|---|---|---|
| Claude Opus 5.5 | $4 | $20 | Anthropic pricing |
| Claude Haiku 5.5 | $0.1 | $0.5 | Anthropic pricing |
| Levanto Sage 2 | $0.05 | $1 | Levanto list price |
Checked 2026-11-03. Same table the public prices endpoint serves.
What we measured and what we assumed
- Measured: Levanto Sage 2 used 329 input and 607 output tokens per document on average, over 36 synthetic lead, ticket and invoice documents (228 field values), in our bench run on 2026-11-03. Its output includes per-field probabilities, which is why it is larger than the JSON alone.
- Assumed for Claude Opus 5.5: 700 input tokens (a ~300-token document plus the audit’s default 400-token prompt with field definitions) and 120 visible output tokens for the JSON.
- Our estimate: 300 reasoning tokens at Claude Opus 5.5’s API default effort (
medium), billed as output. Extraction gets 2.5× our yes/no estimate.
That gives an estimated $11.20 per 1,000 documents on Claude Opus 5.5, against $0.624 on Levanto Sage 2.
How accurate was Levanto Sage 2 on our bench?
| Set | Documents | Field values right | Lead / ticket / invoice |
|---|---|---|---|
| Clean templates | 36 | 96.9% of 228 | 98.8% / 90% / 100% |
| Messier wording | 15 | 88.4% of 95 | 82.9% / 88% / 94.3% |
Weakest fields: ticket.amount_paid (58% on clean documents) and lead.budget (20% on the messier set). Money amounts and free-form budgets are where a fallback to Claude Opus 5.5 matters. Levanto Sage 2 left fields empty correctly 84.1% of the time when they were absent. This is a small synthetic bench, not a benchmark of your data.
Effort level changes the bill
Estimated Claude Opus 5.5 cost per 1,000 documents by effort level, with reasoning billed as output:
| Effort | Est. reasoning tokens | Per 1,000 documents |
|---|---|---|
| low | 100 | $7.20 |
| medium (API default) | 300 | $11.20 |
| high | 800 | $21.20 |
| xhigh | 2000 | $45.20 |
| max | 4000 | $85.20 |
If the fields are copied straight from the text, a lower effort may give the same JSON; test it on your documents. When lowering effort beats switching models.
Monthly estimate by volume
“Share kept” is a scenario: the share of documents where Levanto Sage 2 is confident on every field. The rest also go to Claude Opus 5.5.
| Documents / month | All on Claude Opus 5.5 | Hybrid, 50% kept | 70% kept | 90% kept |
|---|---|---|---|---|
| 10,000 | $112 | $62.24 | $39.84 | $17.44 |
| 100,000 | $1,120 | $622 | $398 | $174 |
| 1,000,000 | $11,200 | $6,224 | $3,984 | $1,744 |
Estimates at the assumptions above. The 30% bar needs Levanto Sage 2 to keep at least 36% of documents. For yes/no calls on Claude Opus 5.5, see Claude Opus 5.5 vs Levanto Sage 2 for classification.
Check it on your own documents
Paste 5 to 25 documents with the JSON Claude Opus 5.5 returned and your field definitions into the free cutover audit. It reports agreement per field, picks the confidence threshold and projects cost with your token counts. How it works · Other models · Is my task too simple for a big model?