Ordin

What a finished run really costs

Per-token pricing hides the cost of retries, dead ends and abandoned jobs. We switched to pricing per finished run, and here is the maths behind it.

Maya OkaforHead of Platform / 1 min read

A job that takes four attempts costs four times as much under token pricing, even though you only got one result. We think that is backwards.

Tokens hide the waste

Token bills measure effort, not outcome. Retries, abandoned plans and long dead ends all count the same as the work that shipped. Teams end up optimising prompts for cost instead of for results.

2.7xaverage attempts per finished job
38%lower spend after the switch
0charges for failed runs

Pricing per finished run

A run is one instruction carried through to a finished result, however many agents and attempts it takes. If it fails, you are not charged. That puts the cost of reliability on us, which is where it belongs.

  • Starter: free up to 10,000 runs a month
  • Scale: USD 49 a seat, plus 0.09 cents a run
  • Enterprise: a volume rate above 500,000 runs

Budgets you set before the run

Every job can carry a budget. The runtime checks it before each step, so a run that is about to overspend stops and asks instead of finishing on your card.

  • Pricing
  • Cost control

Hand it the job. Keep the rules.

Free for the first 10,000 runs. Bring your own model, keep your own data, ship your first agent this afternoon.