Outborn Agent Platform · Manual
Usage, limits & billing
Read each allowance and bill in its own scope. Outborn and provider usage sources are intentionally not one combined quota.
Applied guidance
Best practices for usage, limits & billing
Recommended
- Review each allowance at its own source and identify the billing owner.
- Set an operational response for exhausted credits, subscription limits, and provider rate limits.
Avoid
- Do not report one combined usage balance across unrelated providers.
How it fits together
01
Outborn plan allowance
Plan allowance covers the product entitlements and limits defined by the organization's Outborn plan.
02
Outborn Hosted AI credits
Hosted AI consumes Outborn-managed inference allowance or credits according to the current plan and commercial catalog.
03
Provider Subscription allowance
Provider Subscription uses the connected provider account's subscription allowance when supported. It is not an Outborn Hosted AI credit balance.
04
Provider API usage and billing
Provider API calls use the supplied provider API credentials and are billed under the provider's API account and terms.
05
Application and connector limits
Connected applications may have their own provider quotas, rate limits, plan restrictions, or request limits.
06
Organization limits
The Outborn plan can also bound organization-level resources such as users, Spaces, agents, or other product features.
07
Do not merge the sources
A single combined quota would obscure who supplies the service, which credential is used, where usage is billed, and what action the user should take when a limit is reached.
Related documentation