Priced per build, not per token

Per build operation. A build operation is one change you asked for, carried through to a verified, content-hashed version you can open. It is a unit you can point at: you asked for something, and here is the working version that came back.

sup3rapp is in private beta. Access is by request; there is no self-serve signup yet. Prices are not published yet. When they are, they will appear on this page and on the canonical claim sheet, and this site will not carry a number that is not on both.

Because per-token pricing charges you for the model’s behaviour rather than for your result. If the model is verbose, you pay more. If it takes a wrong turn and has to be talked back, you pay for the wrong turn. If it needs three attempts at something it should have got in one, you pay three times — for one outcome.

None of that is a signal you can act on, and none of it is under your control. The build operation is: you asked for one change, you got one working version, that is one unit.

It follows from that unit that the repair attempts inside a build are not billed separately. Repairing a failed verification is part of delivering the build you asked for, not extra work you commissioned.

Access is by request and granted in batches. There is no self-serve signup, no card to enter, and no plan to choose — which is also why there is nothing on this page to compare.

Tiers, limits and prices will be published before general availability, not after. If you are in the beta when that happens, you will hear it from us first.

sup3rapp is in private beta. Access is by request; there is no self-serve signup yet. Tell us what you want to build and we will match you to a batch as places open.