How the price is set

From measured tokens to a credit — including what happens when a build fails.

Estimate before, measurement after

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.

Failure costs you nothing

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.

One credit = $0.10

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 diagram: one credit is worth $0.10. A full new build is estimated at 25 credits, a change to an existing app at 2 credits, and a build that fails its health check is not charged at all.One credit = $0.10012345678910111213141516171819202122232425A full new build25 credits · $2.50A change to an existing app2 credits · $0.20A build that failed its check0 credits · not chargedCharged from the tokens actually reported, after saving
These are the estimates shown before a build starts, worked out by the same function the engine charges with.

The ceiling is yours

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.

You can follow it

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.

Did not find your answer?Write to us