Managed model access

Terms for plans that include model access

Effective June 19, 2026. These terms explain what TEKIZ.AI must have in place before a hosted plan can include model access. Managed access is active only when the public pricing page says it is included.

Provider permission is required

TEKIZ.AI may include only provider access it is allowed to resell or operate. Each provider must be approved and its terms accepted before it can join a managed-access pilot. This page does not create resale rights or override a provider agreement. Access begins only after provider permission, billing controls, private audit records, 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.

Controls required before launch

  • Monthly and per-minute usage limits, plus private audit records, must be enforced before managed access is enabled.
  • Provider cost and plan margin checks must pass before a plan can include model access.
  • 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.
  • TEKIZ.AI 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 responsibilities

Customers remain responsible for the legality, safety, and authorization of their work. Managed access is measured and limited. It does not guarantee a marketplace or provider, and it is not permission to evade provider controls.