Code generation: a model at 1/271st the price of the best scorer, at 97.8% of its quality.

inkling-small vs mistral-nemo for extraction

the measured answer

As of September 7, 2026, inkling-small measures 0.977 on information extraction vs 0.917 for mistral-nemo (+0.060), at 22.4× the price ($0.5466 vs $0.0244 per 1K requests).

same suite, same items, same scoring — frontier v5, measured 2026-09-07 · method

modelvendormeasured quality$ / 1K requestsp95 latency
inkling-smallthinkingmachines0.977$0.54664649 ms
mistral-nemomistralai0.917$0.02443848 ms

Extraction — pulling fields out of documents, emails, and records into structured JSON — is scored field-by-field against known references, so the numbers below are deterministic, not judged. It is also the workload where reference-free LLM judging fails measurably (judges cannot see omissions), which is why extraction claims anywhere should be treated with suspicion unless the scoring method is stated.

These two are part of a larger measured frontier — what is the best model for data extraction shows every measured option for this workload, and other workloads rank these models differently: a model that wins here can lose on another kind of work, which is the whole argument for routing per workload rather than picking one model for everything.

the routed alternative

Potion routes each request to the cheapest option measured at your quality bar — including picks this public page does not name. Get an API key or read the docs.

inkling-small vs mistral-nemo for extraction — measured · Frontier Notes