Managed provider prerequisite

Sage Router Provider Resale Terms

Effective June 19, 2026. These terms describe the public boundary Sage Router must meet before any managed model-provider access can be offered. Managed provider access is not active in the public hosted plans unless the public pricing metadata explicitly marks it enabled.

Authorized Resale Only

Sage Router may only route managed provider access that Sage Router is authorized to resell or operate. A provider family must be explicitly allowlisted and its terms acknowledged before it can be part of a managed-access pilot. This page does not create provider resale rights by itself, does not override any provider agreement, and does not make third-party model access available until the applicable provider authorization, billing controls, operator audit events, and abuse controls are in place.

What This Does Not Allow

  • It does not authorize pooled accounts, shared personal subscriptions, stolen keys, leaked credentials, proxy abuse, or bypassing provider terms.
  • It does not guarantee access to any specific provider, model, region, throughput level, context window, or latency target.
  • It does not expose provider credentials, provider accounts, or upstream billing relationships to customers.
  • It does not remove customer obligations under the Acceptable Use Policy, hosted Terms, or any provider-specific restrictions.

Operational Controls Required

  • Durable monthly quotas, request-per-minute limits, and secret-free operator audit events must be enforced before managed access is enabled.
  • A configured positive provider cost model and public plan-margin checks must pass before bundled model access can become active.
  • Accounts, generated API keys, billing state, fraud risk, chargeback risk, and abuse signals may be reviewed before or after activation.
  • The public pricing checkpoint may show readiness status, missing controls, cost-model status, public revenue per 1,000 requests, derived maximum safe provider cost per plan, and per-plan margin status, but it must not expose provider credentials, provider accounts, upstream billing relationships, actual provider costs, prompts, or raw responses.
  • Sage Router may throttle, suspend, degrade, change, or remove managed routes when provider capacity, authorization, safety, compliance, payment, margin, or cost-model controls require it.
  • Private-beta customers may be limited to approved use cases, specific plans, manual onboarding, and lower initial quotas.

Customer Boundary

Customers still own the legality, safety, and authorization of their workloads. Managed provider access, if introduced, is a convenience and reliability feature. It is not unlimited unmetered resale, not a provider marketplace guarantee, and not permission to evade provider controls.