A 402 means the request was authenticated correctly but there is no balance to pay for it. Unlike a 401, nothing is wrong with your key.
Every 402 includes the URL that fixes it, pointing either at a wallet top-up or at a plan. Follow it, add credits, and repeat the request. From the CLI, exit code 5 carries the same meaning, so scripts and CI pipelines can branch on it and pause instead of failing loudly.
- Check your balance on Home or under Profile then Billing.
- Top up the wallet (500 for $17.50, 1,000 for $35, 3,000 for $105) or move to a plan for a lower per-credit price.
- Credits are booked the moment payment completes.
- Re-run the request. Nothing was consumed by the failed call.
A 402 also tells you which calls you were making. Counts and redacted previews never return it, because they are free on every tier, unlimited, forever. Only reveals and exports spend, and only those can be blocked this way.
If an agent hits this mid-run, that is the design working. Spending is enforced server-side against your balance, so a misbehaving agent can never spend past what you hold.
If your balance looks sufficient and you still get a 402, send the request details to support@argorant.com.