Managed model access

Terms for plans that include model access

Effective June 19, 2026. These terms explain the conditions for including managed model access in a hosted plan. That access is available only when the public pricing page lists it as included.

Provider permission is required

TEKIZ.AI may include only provider access it is authorized to resell or operate. We must approve each provider and accept its terms before adding it to a managed-access pilot. These terms do 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.

Limits on managed access

  • 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 page may show which controls are ready or missing, whether the cost model is ready, revenue per 1,000 requests, the calculated maximum safe provider cost for each plan, and whether plan margins pass. 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 has usage limits. It does not guarantee access to a marketplace or specific provider, and it does not permit customers to evade provider controls.