Spend caps.

Every new key starts with a $5 / month cap. No opt-in, no setup.

Choose the cap when you make the key on /compute (Start → Build):

Field	Values
Spend cap	$1 – $1,000 per window, or uncapped
Reset window	monthly (default) or weekly

Anything outside $1–$1,000 falls back to the $5 default. Uncapped means no per-key ceiling - the prepaid credit balance still applies.

When a key hits its cap, the API answers 402 key spend limit reached until the window resets. Spend zeroes at the monthly or weekly rollover and the key works again. Jobs never bill past the cap.

HTTP/2 402
{"error":"key spend limit reached"}

Credits are the prepaid balance every job draws from (buyer price $0.05 per successful chat completion). A cap is a second, per-key circuit breaker on top of that balance. A 402 from the cap does not mean the account is out of credits - it means this key hit its own ceiling.

Signed in on /compute, GET /compute/api/keys lists each key with limit_cents, limit_remaining_cents, spend_cents, and limit_reset.