Credits and quotas
How a balance turns into requests.
One credit is one cent of API spend. That is the entire definition — credits are an accounting unit for real cost, not a points system.
Your share#
Your daily quota is your share of the pool, and your share is your share of the tokens:
your_credits = (your_balance / active_supply) × pool_credits
Active supply counts tokens held in wallets that have connected at least once. Tokens sitting in wallets that never show up are excluded, so dormant supply does not dilute the people actually using the product.
Why share-based, not per-wallet#
A flat allowance per wallet — say 50 credits each — is free money for anyone willing to open a thousand wallets. Splitting a fixed pool by holding share removes the incentive entirely: dividing your bag across ten wallets gives you ten tenths of the same quota, minus gas.
Sybil resistance here is arithmetic, not detection. There is nothing to catch because there is nothing to gain.
Cost per request#
A typical request is roughly 10k tokens in and 1k out. At published API rates that works out to:
| Model | Credits | Relative | Available to |
|---|---|---|---|
| Haiku 4.5 | 1.5 | 1× | Everyone |
| Sonnet 5 | 4.5 | 3× | Everyone |
| Opus 5 | 7.5 | 5× | Holders |
Long contexts and long answers cost more; the counter under the composer always shows the current model's rate and how many requests your remaining balance covers.
Resets#
Quotas reset at 00:00 UTC. Unused credits do not roll over — an unspent balance would be a claim on money the treasury has already converted, and carrying those claims forward is how a system like this goes insolvent.