Pricing
Quoted first.
Charged after.
Priced on the result. A free estimate comes first — a static scan that takes seconds and runs none of your code. Only continuing takes the 2-credit analysis deposit, which is credited in full against the patch. You decide whether to buy only after the speedup is confirmed 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 supported (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
- Card or WeChat Pay, any amount; WeChat Pay requires a QR scan on desktop
$0.50–$5000. Card or WeChat Pay; WeChat Pay requires scanning a QR code on desktop.
- 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: large repos, many parallel runs
What a run costs
Compute always at 50%, tokens at 8–13% by speedup
Metered on the compute and tokens actually consumed, against public list prices: GPUs at Beam's or Modal's list price, tokens at Anthropic's published API rates. The GPUs are hardware we rent, and they cost the same whatever the run finds, so compute is always billed at 50%. A run that never uses a GPU (submitted as CPU only) has no machine charge at all. Tokens are the agent's work, and the speedup determines what that work is worth. Below is a real RTX 4090 run: 2.8 hours, 1.61× end to end, whose tokens land in the 11% tier.
The share of list you pay for tokens depends on the end-to-end speedup the run delivered — the run above reached 1.61x, the highlighted tier. That speedup is the headline number in your report, and you can verify it yourself. Below 1.10x the patch is not sold: the deposit is returned and nothing is charged.
Rate table: list price / what you pay
When you are charged
How quickly 4.2 credits pay for themselves
You buy the patch once; the speedup lasts. At 1.61×, the same work takes 62% of the machine time, saving 38% of your compute cost every hour it runs. At public cloud rates:
For a job that retrains 20 hours a week on an H100, the first month's savings alone far exceed the cost of the patch.
Billing rules
When you are charged, and when you are refunded
| Estimate | Free; none of your code runs. |
| Continue | 2-credit deposit, credited in full against the patch. |
| Unlock | Charged at the quote, which is actual usage with no markup; never more. |
| Target missed | No patch sold; you still get the report; deposit returned. |
| Our failure | The deposit returns to your balance. |
| Deduction order | Current-period subscription credits first, then packs, oldest first. |
Speedup = the end-to-end wall-clock time of your own command, optimised versus the frozen baseline. The report breaks it down into startup, the key loop and everything after it.