Anthropic API prepaid credits and billing boundary — Hovvi
How Anthropic makes prepaid API credits legible through a purchase boundary, completed-work charging, a hard stop, optional auto-reload, expiry and a separate invoiced path.
Published by Hovvi Research. Observed ; materially updated .
What happened
Require a bounded prepaid balance, charge only completed value and make exhaustion, reload and expiry behavior visible before commitment. Make the prepaid boundary and its operating consequences legible before payment details are entered.
Evidence
Commit funds before the first successful call.
| Decision | Observed rule | User-visible consequence |
|---|---|---|
| Entry | Prepaid usage credits | Purchase before API or playground use |
| Consumption | Successful calls and completed tasks | Failed requests are not charged; a completed request can still be billed if its response is lost |
| Exhaustion | Balance reaches zero | API and playground stop |
Auto-reload is explicit, threshold-based and optional.
The user chooses both the low-balance trigger and the reload amount instead of receiving an invisible automatic extension.
Unused value has an expiry and no refund path.
The one-year expiry and non-refundable purchase make the funding decision materially different from postpaid usage.
Observed facts
- Anthropic states that Claude API and playground usage for self-serve accounts is billed through prepaid usage credits that must be purchased before use.
- The same usage-credit balance can fund Claude API access, playground usage and Claude Code.
- Anthropic says billing applies to successful API calls and completed tasks, while failed requests are not charged; a successful request may still be charged when the response is lost to a connection error or timeout.
- When the credit balance is exhausted, API calls and playground use stop until more credits are available.
- Anthropic offers an optional auto-reload rule with a user-set balance threshold and reload amount.
- Purchased credits expire one year after purchase, cannot be extended and are non-refundable.
- Anthropic documents monthly invoicing in arrears as a separate path for Console organizations with an invoicing arrangement established through Sales.
Editorial inference
- A prepaid API can feel bounded rather than punitive when successful consumption, the hard stop, reload control and expiry are explained together before purchase.
Evidence views
- Public API pricing context
- Credit purchase boundary
- Balance and exhaustion explanation
- Auto-reload control
- Expiry and refund terms
Founder takeaway
Explain what consumes prepaid value, what happens at zero and what cannot be recovered before asking for payment.
Use when
- A self-serve API needs payment assurance before variable usage begins
- Users can start with a deliberately bounded balance
- The service can stop cleanly when funds are exhausted
Avoid when
- Users require postpaid procurement or consolidated enterprise invoicing
- The minimum commitment is disproportionate to evaluation value
- A hard stop would interrupt safety-critical or continuity-sensitive work
Next implementation step
Design a prepaid API commitment path that explains funding, consumption, exhaustion and reload before payment details are entered.
Acceptance criteria
- A developer can state whether payment is prepaid or postpaid before entering card details
- The interface explains which successful activity consumes the balance
- The zero-balance behavior is visible before commitment
- Auto-reload remains off until the user explicitly configures it
- Expiry and refund limits appear before purchase confirmation
- No private account field is included in public evidence or Agent output
Related cases
- Funding boundary versus usage meter: OpenAI API token-based pricing pattern — Hovvi
Anthropic explains when funds must be committed and what happens at zero; OpenAI isolates the token units that make variable model cost legible.
- Prepaid balance versus included allowance: Cloudflare Workers pricing: free quota, overage and CPU limits — Hovvi
Anthropic starts self-serve use with a funded balance and hard stop, while Cloudflare pairs a free boundary with included paid allowance, overage and a configurable ceiling.
Version history
Current snapshot: snap_anthropic_api_credits_2026_08_26 — Added the first bounded Anthropic Task Reference using public link-only billing evidence; authenticated Console imagery and account data remain excluded.
Use with an Agent
Example read-only MCP query:
Retrieve the Hovvi Founder case fc_anthropic_api_prepaid_credits_2026_08 with observed facts, evidence screens, applicability limits and citations.