Billing and Invoices

There are three billing conversations in AnyInt:

• prepaid Pay As You Go balance for self-serve usage
• subscription billing for plan or custom recurring access
• enterprise billing and invoice workflows for organizations

Pay As You Go billing

For self-serve users, Billing is typically where you:

• top up account balance
• review balance consumption
• monitor request and model usage
• decide when to recharge before balance runs out

In this mode, API usage is deducted directly from prepaid balance through your API key.

Subscription billing basics

• the active subscription determines which key and limits apply
• regenerating a subscription key should invalidate the old key immediately
• usage caps and throttling should be visible before they become outages
• plan and custom subscriptions are mutually exclusive while active

Enterprise monthly billing

The enterprise product plan documents a monthly invoice workflow:

• billing period follows the calendar month
• invoices are generated at the start of the next month
• payment is due within the configured payment window

Typical invoice fields include:

• invoice ID
• billing period
• request and token summary
• model-level cost breakdown
• discount lines
• total amount due
• payment status

Invoice types

The current enterprise documentation anticipates:

• electronic invoices
• VAT or tax-special invoices where required
• international invoice formats

Finance-role visibility

The Finance role is intended to handle:

• billing views
• invoice access
• payment actions
• invoice management

That keeps product and engineering roles out of finance workflows by default.

What to publish publicly

Keep this page customer-facing and remove implementation details such as invoice ID generation rules, settlement jobs, or internal accounting tasks.