macOS and Linux, on Apple silicon, Intel and ARM. It installs one binary, f3b, in ~/.local/bin, after checking its SHA-256. Read the script before you run it.
Usage
f3b build
Uploads your Lean file and builds it against a pinned Lean 4 and Mathlib, in a sandbox that is already warm. You get Lean's messages back, and an exit status that is the verdict.
$ f3b build Riemann.leanf3b: lean v4.35.0: accepted · 1840 ms × 1 core · charged $0.0001840 · $19.9998 left
Every complete verdict carries an Ed25519 receipt over the Lean version, the environment's hash, your code and the verdict. f3b checks it before it believes anything. Add --audit zeta_zero to see which axioms a theorem rests on.
f3b balance
Shows your credits.
$ f3b balance$19.9998 left · $0 held · $0.0001840 spent · $20.0000 paid in
f3b topup
Loads credits with Stripe. It opens Stripe Checkout in your browser and waits until the payment lands. No account, no sign-up: the first top-up opens a meter and keeps its token in ~/.config/f3b/token.
$ f3b topup 20f3b: pay $20.00 with Stripe:
https://checkout.stripe.com/c/pay/cs_live_…
f3b: waiting for the payment (Ctrl-C to stop; `f3b balance` shows it later)
f3b: paid. $20.0000 left · $0 held · $0 spent · $20.0000 paid in
Pricing
You pay for the time Lean runs, by the core-second, and nothing else.
$5f3b topup 5
$20f3b topup 20
$100f3b topup 100
A build reserves its ceiling (the price × cores × timeout) and is charged for the time it took. A build someone already ran, on the same code and the same environment, comes from the cache at a tenth of the price. A refusal costs nothing. f3b info prints the current price.
For scripts and agents
The exit status is the verdict, so f3b build drops into a loop as it is.
0
Lean accepted the file.
1
Lean rejected it.
2
Out of credits: f3b topup.
3
The service refused or failed.
4
The build timed out, which says nothing about the file.
5
The receipt does not verify, so nothing is believed.
Agents with a wallet can skip Stripe and pay per request over HTTP 402.