What this tests
semantics
Point your client at this specimen and find out — before prod does — whether it interprets status codes and content types correctly, or makes things up.
Anatomy
HTTP 402 — "Payment Required", reserved since HTTP/1.0 for "future use" and then actually used by a few brave APIs (Google's old one, some payment gateways, your invoice) to mean exactly what it says: your account has run out of money. Not rate-limited. Not forbidden. Just broke. It is the only 4xx that is specifically about the state of your wallet, and it separates clients cleanly: those that treat 4xx as "client error, retry with better input" will retry a billing problem forever, and those that read the body will learn they've been switched to a payment plan they didn't know had a bottom. A rare status in the wild — which is exactly why it belongs in the museum: the day an API returns 402 is the day your error handling discovers it has a gap in the enum.
Replay it
curl -i https://faultydata.com/r/FD-2026-083
// response appears hereSignature
{Status:402 Headers:map[] Body:{"error":"payment_required","message":"Your account balance is insufficient to continue. Please top up."} Corrupt: Delay:<nil> Flaky:<nil> Sequence:<nil> Drip:<nil> StallAfter:0 Hang:false Reset:false Raw: Phases:[]}
Keep digging
FD-2026-004 — GitHub secondary rate limit FD-2026-010 — Gateway timeout from the edge (Cloudflare 522 pattern) FD-2026-023 — Global 502s from a bad WAF rule (Cloudflare, Jul 2019) FD-2026-029 — Production database deleted, backups broken (GitLab, Jan 2017) FD-2026-030 — Dependency vanishes from the registry (left-pad, Mar 2016) FD-2026-048 — Origin unreachable (Cloudflare 523)