Pricing
Quoted first.
Charged after.
Priced on the result. A free estimate comes first — a static scan of seconds, in which none of your code runs. Only continuing takes the 2-credit analysis deposit, credited in full against the patch. You decide whether to pay only once it is confirmed faster end to end in your own program.
- The best rate we offer, once per account
- ≈ 2–3 full runs on your own repository (a run takes about 2–5 credits)
- Credits valid 24 months
- Private code welcome (zip upload)
- Credits valid for 24 months
- Private repos, results kept private
- Buy more as needed, no commitment
- A run takes about 2–5 credits ≈ $1.5–4, depending on code size, complexity, what the run finds and the speedup
- Cards and WeChat Pay, any amount; WeChat is a desktop QR scan
$0.50–$5000. Card or WeChat Pay; WeChat is a QR code you scan from a computer.
- 50% bonus credits per dollar during the beta
- ≈ 10–15 full runs per month
- Private repos · 5 concurrent
- ≈ 40–60 full runs per month
- Private repos · priority queue · 5 concurrent
- ≈ 85–130 full runs per month
- Top queue priority · 5 concurrent
- For heavy individual use: big repos, many runs in flight
What a run costs
Compute always at 50%, tokens at 5–10% by speedup
Metered on the compute and tokens actually burned, against public list prices: the GPUs at Beam's or Modal's list, the tokens at Anthropic's own API price list. The machine is hardware we rent and costs the same whatever the run finds, so it is always 50%; a run that never touches a GPU (submitted as CPU only) has no machine line at all; the tokens are the agent's work, and the speedup says what that work was worth. Below: one real RTX 4090 run, 2.8 hours, 1.61× end to end, whose tokens land in the 8% tier.
What you pay for tokens, by the end-to-end speedup the run delivered — the run above is 1.61x and lands in the highlighted tier. It is the number at the top of your report, which you can check yourself. Under 1.10x the patch is not sold: the deposit comes back and nothing is charged.
Rate table: list / what you pay
When money moves
When 4.6 credits pay for themselves
The patch is bought once; the speedup keeps running. 1.61× = 62% of the machine time, so every hour keeps 38% of what it used to cost you. At public cloud rates:
A job that retrains 20 hours a week saves more H100 time in its first month than the patch cost.
Billing rules
When you're charged, and when you're not
| Estimate | Free; none of your code runs. |
| Continue | 2-credit deposit, credited in full against the patch. |
| Unlock | The quote, which is actual usage with no markup; never more than it. |
| Target missed | No patch sold, report still yours, deposit returned. |
| Our failure | The deposit returns to your balance. |
| Order | This period's subscription credits first, then packs, oldest first. |
Speedup = the wall clock of your own command end to end, optimised against the frozen baseline; the report breaks it into startup, the key loop and what follows.