Account & Billing
Use this section to understand API keys, BYOK, prepaid balance, subscriptions, invoices, and the billing states that can affect API access.
Use this section to understand API keys, BYOK, prepaid balance, subscriptions, invoices, and the billing states that can affect API access.
Start here
| Task | Page |
|---|---|
| Understand account access and billing models | Overview |
| Create, store, rotate, or revoke API keys | API Keys |
| Share access across projects or departments | Team Keys |
| Keep upstream provider credentials customer-owned | BYOK |
| Use prepaid balance for self-serve API usage | Pay As You Go |
| Use fixed tiers and shared limits | Subscriptions |
| Buy specific models, limits, or enterprise terms | Custom Subscriptions |
| Review invoices, renewals, and finance workflows | Billing and Invoices |
Security baseline
Treat API keys as production credentials. Do not put real keys in source control, documentation examples, screenshots, or client-side code.
Operational baseline
Billing state can affect whether API requests are accepted. Production systems should monitor subscription status, prepaid balance, and limit events instead of treating billing as only a finance workflow.