Pareto 26.10 Preview: Pricing, Context, and Vendor Benchmarks
A source-based look at Unbiased’s composite-model preview, its lower token rates, preliminary evaluations, and the implications of a changing serving stack.
Co-Founder & Lead Programmer of AcceleratedLogic AI
Pareto 26.10 Preview puts a composite model behind a large-context API route at a relatively low token price. Unbiased announced the preview on October 1, 2026. Its main appeal is a combination of broad task coverage and lower operating cost; a deployment decision still needs evidence from the tasks the application actually performs.
Verified route specifications
OpenRouter route, checked October 3, 2026
Value
Model ID
unbiased/pareto-26.10-preview
Listing date
October 1, 2026
Context
1,048,576 tokens
Inputs
text, image
Output
text
Input price
$0.8 / 1M tokens
Output price
$3.2 / 1M tokens
The route accepts text and images and returns text. These are OpenRouter’s current route specifications, rather than a guarantee about every deployment sold under the Pareto name. The OpenRouter listing links the model to its serving providers.
What Unbiased reported
Unbiased reports preliminary scores of 92.4% on GPQA-Diamond, 49.9% on text-only Humanity’s Last Exam, 69.9% on DeepSWE v1.1, and 50.8% on Terminal-Bench 4.0. The announcement pairs those figures with costs per task and describes the serving stack as still settling. These are vendor-run results, which this article has not reproduced. The vendor also states that its OpenRouter and Cloudflare traffic uses a zero-data-retention tier. Unbiased’s announcement
Why the preview status matters
An evaluation run should record the date, route, provider, settings, prompt, and response alongside each result. If the serving system changes while the preview keeps the same name, a later run can behave differently. An application can handle that by retaining a small set of representative cases and running them again before adopting a changed deployment.
Token rates also need to be separated from total task cost. At the listed base rates, a hypothetical request using 100,000 input tokens and 10,000 output tokens costs $0.112 before caching, tools, or retries. A longer sequence of calls can spend more even when each individual request is inexpensive. This arithmetic is an illustration, not a measured Pareto workflow.
Testing scope
This route was paid in the catalog checked for this article, so it was not run through the three HTML prompts in this pass. A useful follow-up would compare valid output, repair count, total tokens, and latency across repeated application tasks. This article supplies verified specifications and an evaluation plan; it does not assign an independent quality score.