Usage and billing
Aleph attributes runtime usage to the account that owns the agent while retaining the agent ID on every event.
Billing accounts
| Agent placement | Billing account |
|---|---|
| Personal | Creating user |
| Organization | Organization |
| Team | Organization, with team attribution |
This is similar to repository hosting: an organization pays for shared work, while teams organize access and reporting rather than forming separate billing accounts.
Usage credits
Each account has one monthly usage-credit balance. The Usage page keeps the categories visible so you can understand what consumed it:
- model usage, based on the input and output tokens and model used;
- isolated runtime, based on the resources used while an agent works;
- web searches, based on each search request;
- turns, which attribute chat, schedule, and channel activity without charging for the same work twice.
Free includes 250 credits each month. Pro is $29 per month and includes 8,000 credits. Credits reset at the start of each UTC calendar month and do not roll over.
Aleph warns at 80% of the account allowance and stops new agent runs at 100%. There are no automatic overage charges. Per-agent attribution explains where consumption came from, while personal or organization Billing shows the shared remaining balance.
Platform model access is included in this accounting model; there is no user-supplied model key today. Checkout and invoice availability can depend on deployment configuration, while usage tracking itself does not.