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 | Outcome |
|---|---|---|
| Understand account access and billing models | Overview | Know which billing states can affect API access |
| Create, store, rotate, or revoke API keys | API Keys | Keep production credentials controlled and auditable |
| Share access across projects or departments | Team Keys | Separate teams, environments, or products without sharing one key everywhere |
| Keep upstream provider credentials customer-owned | BYOK | Decide when your organization should bring its own provider key |
| Use prepaid balance for self-serve API usage | Pay As You Go | Understand balance-based usage and operational monitoring |
| Use fixed tiers and shared limits | Subscriptions | Plan predictable recurring access |
| Buy specific models, limits, or enterprise terms | Custom Subscriptions | Capture model, quota, and commercial requirements that do not fit self-serve plans |
| Review invoices, renewals, and finance workflows | Billing and Invoices | Keep finance processes from blocking production API usage |
Security baseline
Treat API keys as production credentials. Do not put real keys in source control, documentation examples, screenshots, or client-side code.
| Control | Recommended practice |
|---|---|
| Storage | Use a deployment secret manager or environment variable, not a checked-in file |
| Rotation | Keep a documented rotation path before a key is suspected to be exposed |
| Separation | Use different keys for development, staging, and production |
| Browser access | Do not call AnyInt directly from untrusted browser code with a long-lived key |
| Logging | Redact Authorization, x-api-key, prompts, uploaded file URLs, and generated private outputs when needed |
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.
| Signal | Why product and engineering teams should care |
|---|---|
| Expired subscription | Requests that worked yesterday may start failing for non-code reasons |
| Low prepaid balance | Batch jobs and background automations can consume quota before user-facing traffic runs |
| Key-level restriction | A model or route may fail for one key while another key still works |
| Custom entitlement | Access to a purchased model or higher limit may be scoped to a specific account or key |
| Invoice or renewal issue | Finance delays can become production incidents if nobody monitors them |
Recommended setup by environment
| Environment | Key and billing pattern |
|---|---|
| Local development | Use a low-risk development key with narrow access and avoid committing .env files |
| Staging | Use a separate key and model list so staging failures do not hide production access issues |
| Production | Use managed secrets, explicit owner contacts, alerting for balance or subscription state, and a rotation procedure |
| Enterprise teams | Use team or project-level keys so usage, limits, and ownership stay clear |
When to contact AnyInt
Contact your AnyInt representative when you need model access that is not visible through Models API, higher or custom limits, BYOK onboarding, enterprise invoicing terms, SSO or organization controls, or help separating keys across teams.