Extraction estimate · prices checked 2026-11-03

Claude Fable 5.1 vs Levanto Sage 2 for field extraction

List prices

Model$ per M input$ per M outputSource
Claude Fable 5.1$10$50Anthropic pricing
Claude Haiku 5.5$0.1$0.5Anthropic pricing
Levanto Sage 2$0.05$1Levanto 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 Fable 5.1: 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: 800 reasoning tokens at Claude Fable 5.1’s API default effort (high), billed as output. Extraction gets 2.5× our yes/no estimate.

That gives an estimated $53.00 per 1,000 documents on Claude Fable 5.1, against $0.624 on Levanto Sage 2.

How accurate was Levanto Sage 2 on our bench?

SetDocumentsField values rightLead / ticket / invoice
Clean templates3696.9% of 22898.8% / 90% / 100%
Messier wording1588.4% of 9582.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 Fable 5.1 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 Fable 5.1 cost per 1,000 documents by effort level, with reasoning billed as output:

EffortEst. reasoning tokensPer 1,000 documents
low100$18.00
medium300$28.00
high (API default)800$53.00
xhigh2000$113
max4000$213

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 Fable 5.1.

Documents / monthAll on Claude Fable 5.1Hybrid, 50% kept70% kept90% kept
10,000$530$271$165$59.24
100,000$5,300$2,712$1,652$592
1,000,000$53,000$27,124$16,524$5,924

Estimates at the assumptions above. The 30% bar needs Levanto Sage 2 to keep at least 31% of documents. For yes/no calls on Claude Fable 5.1, see Claude Fable 5.1 vs Levanto Sage 2 for classification.

Check it on your own documents

Paste 5 to 25 documents with the JSON Claude Fable 5.1 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?

Run the free extraction audit

Questions

Can Levanto Sage 2 extract fields as well as Claude Fable 5.1?

On our small synthetic bench it got 96.9% of 228 field values right on clean documents and 88.4% on messier ones. That says nothing certain about your documents and fields, which is why the audit compares it with Claude Fable 5.1’s own output on your samples.

Which numbers here are measured and which are estimates?

Measured: Levanto Sage 2’s tokens per document and its field accuracy, from our bench run on 2026-11-03. Estimated: Claude Fable 5.1’s tokens per call (700 input, 120 output, 800 reasoning). Prices are list prices checked 2026-11-03, without batch or cached-input discounts.

Should I just write a regex?

If your documents follow a fixed template, yes, try that first. On our templated bench documents hand-written regexes got 100% of fields. A model earns its cost when wording and layout vary.

What happens to fields the small model is unsure about?

In a hybrid you keep confident fields and ask Claude Fable 5.1 only for the rest. These estimates charge a full Claude Fable 5.1 call for every document not kept, so they are on the conservative side.