Billing and Credits
How Sovereign plans, credits, reservations, refunds, and usage accounting work.
Sovereign plans include a monthly credit allowance. Credits are consumed by model usage.
Plans
| Plan | Monthly Credits | Context | Output |
|---|---|---|---|
| Go | 25 | 256,000 tokens | 128,000 tokens |
| Plus | 75 | 512,000 tokens | 256,000 tokens |
| Pro | 400 | 1,024,000 tokens | 384,000 tokens |
How Usage Is Counted
Usage is based on:
- input tokens;
- output tokens;
- request limits;
- plan caps;
- provider-side usage metadata when available.
Reservations
Before a request starts, Sovereign reserves credits so users cannot exceed their available balance during long generations.
If the final request costs less than the reservation, the unused amount is refunded to the ledger.
Streaming
Streaming requests are charged with a conservative accounting flow. Sovereign tracks emitted output and finalizes the ledger after the stream ends.
Context Cache
The upstream reasoning provider may apply context caching automatically. When cache hit and miss metadata is returned, Sovereign records it in usage metadata and exposes compatible fields where possible.
Cache behavior is best-effort and should not be treated as a guaranteed discount or performance feature.
Viewing Usage
You can view plan and usage information from the Sovereign dashboard: