Max
The hardest and highest-stakes work where capability is the first requirement.
Add credits, use any of Tokaroo's five models, and draw down one balance as requests complete. Keep a card on file; turn threshold-based auto-reload on only when you want it.
There is no seat price attached to a mode. Tokaroo calculates each charge from the completed workload, measured usage, modality, and optimized routing outcome.
The hardest and highest-stakes work where capability is the first requirement.
Serious daily technical, business, production, and customer-facing work.
The default for applications that want Tokaroo to make the whole routing decision.
Rapid answers, edits, extraction, and interactive back-and-forth.
Everyday questions and routine tasks where you need an answer, not a project.
API access uses prepaid credits. Tokaroo does not require a monthly subscription or take a fixed monthly payment.
Add $10, $25, $50, or a custom amount. Completed requests deduct the Tokaroo charge from that balance.
Choose a balance threshold, reload amount, and rolling 30-day charge cap. Nothing reloads unless you enable it.
Stripe emails a receipt for every manual purchase and automatic reload.
Use workspace budgets, scoped keys, rate limits, the auto-reload cap, and dashboard reporting.
Threshold-based auto-reload means Tokaroo charges the saved card only when the remaining balance reaches the level you selected, rather than on an arbitrary monthly date.
Make an initial credit purchase, save a card, accept the API terms, and create a Tokaroo key.
Successful requests record the Tokaroo mode, input and output tokens, latency, and Tokaroo charge.
If enabled, auto-reload adds your chosen amount after the balance reaches your chosen threshold, subject to the rolling 30-day cap.
At a zero balance, paid API access stops with 402 billing_required until credits are added.
The dashboard shows balance, aggregate charges, tokens, requested modes, and defensible aggregate benchmark savings.
Start with Auto unless the workload has a clear cost, latency, or quality requirement.
Use all five Tokaroo models from the same balance.
Use the same key across supported compatible API formats.
Keep a saved card for account continuity; auto-reload remains optional.
Review balance, usage, aggregate savings, and receipts in the dashboard.
Runtime headers provide an opaque trace ID, requested Tokaroo mode, token counts, latency, and Tokaroo charge. Internal provider routes and upstream economics stay private.
Tokaroo publishes aggregate evaluation freshness and basket coverage. Concrete model membership remains internal because it changes by task, compatibility, health, and availability.
Quality is measured separately for reasoning, code, math, reading, writing, tools, multilingual, and spatial work.
The best fresh measured output in that task family becomes the 100% quality ceiling.
Only compatible candidates clearing the requested mode's quality checks enter its decision basket.
Tokaroo then weighs speed, price, reliability, context, tools, and availability inside that basket.
Awaiting fresh evidence | Conservative fallback floors
Awaiting fresh evidence | Conservative fallback floors
Awaiting fresh evidence | Conservative fallback floors
Awaiting fresh evidence | Conservative fallback floors
Awaiting fresh evidence | Conservative fallback floors
Awaiting fresh evidence | Conservative fallback floors
Awaiting fresh evidence | Conservative fallback floors
Awaiting fresh evidence | Conservative fallback floors
Evaluation evidence is limited to successful Tokaroo tests in the latest 30-day window; imported zero-sample signals are excluded. Basket membership, the concrete serving model, the serving provider, and private settlement cost remain internal.
Create a key, choose Auto, and move to a more specific mode only when the workload calls for it.