Outborn Agent Platform · Manual
AI runtime sources
The three AI runtime sources have different access, allowance, and billing boundaries.
Applied guidance
Best practices for ai runtime sources
Recommended
- Record which account supplies each runtime source and who pays for it.
- Confirm the selected source is supported for the model and organization.
Avoid
- Do not label a provider account session as an API key.
How it fits together
Hosted AI → Outborn access/credits
Provider Subscription → connected subscription allowance
Provider API → API credential + provider API billing
01
Hosted AI
Uses Outborn-hosted model access and Outborn plan/credits. No provider API credential is required from the user for this source.
02
Provider Subscription
Uses a connected user's/provider account subscription allowance when supported. The connection represents a provider account/session rather than an API key.
03
Provider API
Uses provider API credentials and is billed according to that provider's API usage.
04
Keep the sources distinct
Do not combine these sources into one quota number. They may use different credentials, limits, billing owners, provider terms, models, and failure modes.
Related documentation