Hosted support

Sage Router Support

Use this page to pick the right support path for hosted accounts, generated API keys, billing, quotas, setup, public edge reliability, abuse, and security reports.

Do Not Send Secrets

Do not send prompts, workflow text, provider credentials, OAuth tokens, generated API keys, private keys, session cookies, raw provider responses, or customer data in public support channels. Share only account email, plan, timestamp, request id, HTTP status, safe error class, and the non-secret key prefix when needed.

Account and Billing

  • Use the account page to sign in, choose Lite, Pro, or Max, generate keys, test /v1/models, and open the Stripe billing portal.
  • Use Stripe portal for payment methods, invoices, cancellation, and subscription changes when a Stripe customer is linked.
  • Use manual or crypto settlement only when Stripe is not available or a separate manual activation has been agreed.
Finish setup key Compare plans Billing help

Quota and API Keys

  • For 401, confirm the key starts with sk_sage_, is active, and was copied from the account page when first shown.
  • For 402, finish checkout or manual activation before expecting hosted model traffic to route.
  • For 429, check current plan quota and request-per-minute limits before retrying at lower volume.
Read quickstart API reference Troubleshoot errors Create or test API key

Reliability and 503s

  • Check public edge status before changing client config. Sage Router routes to the lowest-latency healthy Tailnet or cloud installation.
  • For 503, include timestamp, request id if present, route profile, safe model name, and whether the same request works against a local router.
  • Do not include prompt bodies, provider responses, bearer tokens, or local router secrets in a reliability report.
View status Browse models

Security and Abuse

  • Revoke exposed generated keys from the account page before filing a report.
  • Report abuse, account compromise, quota bypass attempts, or unsafe traffic with non-secret evidence only.
  • Use GitHub private security advisories for security reports that should not be public.
Review security Acceptable use

Implementation Help

For private deployment guidance, Tailnet routing, team onboarding, or managed-access beta interest, start from the account, pricing, quickstart, and public repository paths. The public launch remains local-first and customer-authorized by default; managed provider access is not active unless a separate written arrangement and runtime readiness checks are in place.

Open a GitHub issue Provider terms Margin policy