How the price is set

Before the build starts an estimate is shown, and it is checked against the balance and against the ceilings you set. When the build ends, the charge is worked out from the tokens actually reported — cached-content discount included. The estimate is never the bill.

If the code did not pass the check, no version is saved and no credit is charged, even though the model worked. Those tokens are on us. The same goes for the automatic repair round and for a build interrupted halfway.

That number is written out here and on the pricing page, because it is the thing nobody in this category is willing to say: what exactly you get when you buy a “credit”.

A ceiling per single build, per day and per month, all checked before the work starts. When you reach one, the request stops and says which one — it does not carry on and send a bill. You can turn the hard stop off, and then they are a warning only.

Every credit movement is recorded with the build that caused it. The billing screen shows the balance, the movements and the ceilings — and you can change them. On each project's log screen you see every build with the tokens measured and what was actually charged, side by side.