Hosted acceptable use policy

Sage Router Acceptable Use

Effective June 19, 2026. This policy applies to hosted Sage Router accounts, public API edge traffic, generated API keys, account/billing flows, analytics, and related hosted routing services.

Core Rule

Use Sage Router only with provider access, local models, subscriptions, API keys, cloud accounts, and endpoints that you are authorized to use. Do not use Sage Router to evade provider terms, provider rate limits, platform safeguards, billing controls, abuse controls, or legal obligations.

Prohibited Use

  • Unauthorized access to third-party model providers, pooled accounts, stolen keys, leaked credentials, or compromised infrastructure.
  • Traffic intended to overload Sage Router, a Tailnet host, Cloudflare, Google Cloud, Supabase, Stripe, a provider API, or any other service.
  • Credential harvesting, secret exfiltration, account takeover, phishing, spam, malware, botnet operation, vulnerability exploitation, or evasion of security controls.
  • Attempts to bypass quotas, rate limits, billing status checks, account suspension, generated-key revocation, provider usage policies, or provider safety systems.
  • Routing content or automation that is unlawful, abusive, infringing, privacy-invasive, or likely to cause harm to people, systems, or services.
  • Misrepresenting Sage Router as a provider marketplace that grants model access independently of valid customer/provider authorization.

Abuse Controls

Sage Router may rate-limit, throttle, challenge, block, suspend, revoke keys, disable routes, or require manual review when traffic appears abusive, risky, unpaid, unauthorized, or operationally harmful. Operator recovery/admin tokens are private and must not be shared with customers.

Provider Compliance

Customers are responsible for checking whether their use of OpenAI, Anthropic, Ollama, NVIDIA, Gemini, OpenRouter, OpenAI-compatible endpoints, local models, or other providers is allowed under those providers' terms. Sage Router routing policy does not override third-party restrictions.

Managed Provider Access

Managed provider access, if introduced, will be limited to provider access Sage Router is authorized to sell or operate. Customers may not use managed access to evade provider terms, safety systems, regional restrictions, payment rules, export controls, or abuse controls. Sage Router may require identity, billing, usage, durable operator audit events, or manual review before enabling any managed access route.

Reporting

Report suspected abuse, exposed generated keys, suspicious billing activity, or security issues through the project repository or the private support path associated with your hosted account.