Account & Billing
Overview
AnyInt account setup has two operational layers: credentials that authorize requests and billing entitlements that decide which usage can run.
AnyInt account setup has two operational layers: credentials that authorize requests and billing entitlements that decide which usage can run. Treat both layers as part of production readiness.
Key types in practice
| Key type | Best for | Typical owner |
|---|---|---|
| Personal or basic API key | individual development and simple integrations | one user |
| Subscription-backed key | plan or custom subscription usage | one account or environment |
| Team key | project, environment, or department-level usage | an organization or project owner |
Billing models in practice
| Billing model | Best for | How usage is charged |
|---|---|---|
| Pay As You Go | individuals, prototypes, variable workloads | requests deduct from prepaid balance |
| Subscription | users who want a predictable monthly tier | one packaged tier with shared limits across included models |
| Custom subscription | teams that want recurring access model by model | per-model configuration with separate service level and limits |
Header styles you will see
Different route families expect different auth headers:
Authorization: Bearer <ANYINT_API_KEY>or
x-api-key: <ANYINT_API_KEY>Anthropic-compatible routes also require:
anthropic-version: 2023-06-01Key lifecycle basics
- create the key in the dashboard or through the subscription flow
- show the plain key once
- store only the masked prefix in UI and the secret in your vault
- rotate the key when ownership or environment changes
- revoke the old key immediately if exposure is suspected
What billing changes operationally
- which models are visible to your account
- which keys are valid for paid usage
- whether requests consume prepaid balance or subscription entitlement
- what rate and usage limits apply
- how billing and invoice records are generated