Pricing
Prepaid model credits, bounded evaluations, optional BYOK, and Pro analysis.
The new prepaid plan separates model usage, payment fees, and analysis. It is available only where checkout is enabled. Existing accounts keep their recorded billing terms until they explicitly switch plans.
Starter
Basic cost analysis and recorded model comparisons have no subscription fee. Inference still requires prepaid credits or your own provider keys. Evaluations require a separate spending ceiling and available funds; there are no unlimited free model tests.
Credits: 5.5% when you purchase
Purchase at least $5 of credits. The 5.5% fee is added to the credit value, rounded to the nearest cent, and includes payment processing. For example, $100 of credits costs $105.50; $5 of credits costs $5.28.
Credits pay for measured provider usage. The new prepaid plan does not add a second monthly percentage fee. A request with uncertain usage keeps its reserved amount pending reconciliation, rather than displaying an invented zero cost.
Pro: $49 per month
Pro includes deeper analysis and a $5 noncash evaluation allowance for the active billing period. The allowance does not roll over or become withdrawable credits. Further evaluations use available credits within your spending ceiling.
The planned earned-Pro benefit uses the prior closed UTC month's settled contribution after processing, reversals, and subsidized evaluation costs. At least $98 of contribution qualifies for the next month. An unresolved payment or pending subscription adjustment is shown as pending, not as a confirmed fee waiver. This is not a fixed monthly usage threshold.
Bring your own keys
BYOK is optional. You pay your provider directly; the prepaid plan adds no percentage charge to those tokens. Falling back to ultrarouter-funded inference requires explicit permission and available credits. Pro and evaluation limits remain separate from your provider's bill.
Optimization requires evidence and permission
Manual mode presents comparisons for your review. Automatic routing requires explicit opt-in, qualifying independent evidence, and a supported application integration. Capturing call content and using knowledge each have separate permissions. A development comparison or subscription does not authorize a model change, and no plan promises that every workflow can be optimized.