Outborn Agent Platform · Manual
Provider Subscription
Connect a supported provider account/session and use that subscription allowance without treating it as an API-key integration.
Applied guidance
Best practices for provider subscription
Recommended
- Use only providers and account connection methods shown as supported in the current deployment.
- Review the provider's subscription terms and current account state before production use.
Avoid
- Do not use a subscription connection as a generic provider API credential.
How it fits together
01
What Provider Subscription is
Provider Subscription is a provider-neutral runtime mode for using a connected provider account's included subscription allowance when supported.
02
Supported providers
OutbornAI should expose only providers and account-connection methods that the current runtime adapter supports. Provider availability may differ by deployment and can change as provider terms or authentication flows change.
03
Authentication mechanisms
A provider may use an account sign-in, device authorization, browser/session flow, or another provider-approved mechanism. Provider Subscription does not use a provider API key unless the provider explicitly defines that as its subscription authentication method.
04
Account and session connection
Each connection keeps its own account/session identity and can be enabled, disabled, reconnected, or revoked independently.
05
Multiple accounts from the same provider
You can keep multiple connected accounts from the same provider as separate runtime sources, each with its own label, session, model, enabled state, and routing priority.
06
Model selection per account
Choose from the models that the connected provider account and current adapter expose for that account.
07
Priority and fallback
Each provider-subscription account can participate independently in routing priority and fallback.
08
Usage and quota visibility
When the provider exposes allowance information through a supported interface, OutbornAI can show it with that provider account. Do not present it as Outborn Hosted AI credit.
09
Provider-specific restrictions
Providers may restrict models, geography, concurrent sessions, automation, or account use. The provider's own terms and account controls remain authoritative.
10
Security considerations
Treat account sessions as sensitive credentials. Keep them protected server-side, scope access to the intended user or organization, and revoke them when no longer needed.
11
Difference from API keys
Provider Subscription uses a connected subscription/account allowance. Provider API uses API credentials and provider API billing. They are separate runtime sources.
Related documentation