Hosted service terms

Tekiz Terms

Effective June 19, 2026. These terms cover the hosted Tekiz web app, public API edge, account management, billing, generated API keys, quotas, analytics, and related hosted routing control-plane services.

Service Boundary

Tekiz sells routing infrastructure, account management, API key management, usage quotas, analytics, reliability tooling, support, and optional private deployment help. Tekiz does not grant unauthorized access to third-party model providers, does not promise to bypass provider terms, and does not pool customer provider accounts as a default service.

Public hosted plans are customer-authorized by default. Any managed-provider access pilot, one-subscription review, or provider-resale path requires a separate written agreement or posted pilot terms, explicit provider authorization, an authorized provider-family allowlist, provider terms acknowledgment, a private provider cost model, positive plan-margin checks, durable quotas and rate limits, billing controls, audit events, abuse review, and acceptable-use enforcement before activation. A public pricing page, waitlist submission, beta request, or managed-access review request does not grant third-party model access by itself.

Accounts and API Keys

  • You are responsible for activity under your Tekiz account and generated sk_sage_* API keys.
  • Keep API keys confidential. Revoke keys immediately if they are exposed or no longer needed.
  • We may suspend or disable accounts, keys, or routes that create abuse risk, security risk, payment risk, infrastructure harm, or legal risk.

Provider Access

You are responsible for ensuring that any model provider, local model, subscription, API key, cloud account, or proxy endpoint you connect to Tekiz is authorized for your use. Provider terms, license terms, rate limits, content rules, and billing obligations remain between you and the provider unless a separate written agreement says otherwise.

Billing and Plans

Hosted plans may include monthly request quotas, request-per-minute limits, billing portal access, analytics, and support. Stripe checkout and billing portal flows are the primary self-service billing paths. Crypto or manual settlement may be available by agreement and may require manual activation.

Reliability

Tekiz is built for health-aware fallback and CDN-style routing across available installations, but no hosted service is guaranteed to be uninterrupted. Public status and route health are provided for operational visibility, not as a guarantee of model provider availability.

Acceptable Use

Your use must follow the Acceptable Use Policy. Do not use Tekiz to attack, overload, scrape, evade provider controls, violate third-party terms, route unlawful content or traffic, or resell or pool provider access through the Service unless a separate managed-provider agreement expressly allows it.

Privacy

The Privacy Policy describes hosted account data, billing data, generated-key metadata, usage counters, and privacy-safe route telemetry. Tekiz is designed not to store prompts, message bodies, provider credentials, OAuth tokens, API keys, or raw provider responses in launch analytics.

Changes

We may update hosted terms, plans, limits, security controls, or service behavior as the product matures. Material changes should be reflected on this page or in customer-facing release notes.