What a turn costs
In short
Every agent turn reports what it cost in points and why, so cost is something you read after each turn rather than discover at the end of the month.
A turn is one round of agent work: your request, everything the agent does to fulfil it, and the result. Turns are the unit that costs points.
Reading the cost
Each turn reports what it drew. Over a few days that history is the most useful cost tool you have — it shows which kinds of request are expensive in your project, which is not the same answer for every project.
Why a turn came out expensive
- It searched a lot. Requests phrased without a location (“fix the bug in the checkout”) make the agent hunt. Naming the file or the flow is cheaper.
- It retried. A failed verification rolls the change back and tries again. Rolled-back work is still work.
- The conversation was long. Carrying a large history costs on every turn. New subject, new conversation.
- It was genuinely hard. Harder problems get more capable models — a deliberate trade of points for a result that is right the first time.
An undone turn is not refunded
Undo restores the code; it does not un-spend the points, because the work was performed. This is the practical reason to review a diff before piling three more requests on top of it.
If a cost looks wrong
If a turn’s cost does not match what happened, report it. Billing questions are free to ask, and a mis-metered turn is our defect to fix.
Next: Points · Your first Ask