Problem
Hosted tenants will want to bring their own AI. Provider terms differ sharply between API keys (clearly permitted) and consumer subscription accounts (restricted or prohibited for multi-tenant/hosted use). The supported connection models need a written decision before hosted GA, so tenant-facing docs and the BYOK surface (#9709 family) promise only what provider terms allow.
Scope
- Review current terms for the major providers used by ORB/AMS: what is permitted for (a) BYO API key, (b) BYO subscription/consumer account, (c) platform-provided AI resold via tiers
- Decision doc: supported models at GA, explicitly unsupported models, and the enforcement point in the BYOK flow
- Follow-up issues for any BYOK-surface changes the decision requires
Acceptance
One decision doc merged; hosted onboarding and BYOK docs reference it; no hosted tier ships a connection model the doc marks unsupported.
Problem
Hosted tenants will want to bring their own AI. Provider terms differ sharply between API keys (clearly permitted) and consumer subscription accounts (restricted or prohibited for multi-tenant/hosted use). The supported connection models need a written decision before hosted GA, so tenant-facing docs and the BYOK surface (#9709 family) promise only what provider terms allow.
Scope
Acceptance
One decision doc merged; hosted onboarding and BYOK docs reference it; no hosted tier ships a connection model the doc marks unsupported.