Hosted billing

Tekiz Billing

Choose a plan, manage billing, and create an API key from your account.

Open account Recover account access Compare plans Get support safely Troubleshoot API errors

Your generated key begins with sk_sage_. Hosted API endpoint: https://api.tekiz.ai/v1.

Choose a plan

Lite, Pro, and Max are selected from pricing or the account page.
Plan links such as /account.html?plan=pro&start=checkout preserve the selected tier through sign-in.
Your account shows the included quota and current usage.

Finish checkout

Stripe checkout starts from the signed-in account page.
Email verification may be required before checkout or key creation.
Alternative payment options appear in your account when they are available. Manual or crypto settlement is available only for approved invoice-based arrangements; it is not a self-service checkout option or a claim on network ownership.

Route with a generated key

Create a generated sk_sage_* key after sign-in.
Hosted model traffic begins when the account is active or trialing.
Revoked generated keys stay revoked and must be replaced with a fresh key.

Activation states

What each billing state means for API routing.

The API uses the same account state shown on the hosted account page. This keeps access and billing status consistent.

Payment recovery: update your payment method or pay the outstanding invoice in the billing portal before expecting hosted model traffic to resume.

State	Customer action	API behavior
Signed in, no paid plan	Choose Lite, Pro, or Max and finish checkout.	`/v1/*` returns guided `402` onboarding instead of provider traffic.
Active or trialing	Create or reuse an active `sk_sage_*` key and run the quickstart.	Model traffic routes within quota, request-per-minute limits, and provider availability.
Past due	Update payment method or pay the invoice through Stripe portal.	Routing can be blocked until payment recovery updates the account state.
Suspended	Resolve abuse, chargeback, provider-risk, or security review with support.	Routing stays blocked. Payment recovery does not override operator suspension.

Stripe portal

Self-service billing after checkout.

After a Stripe customer is linked, the account page opens the Stripe billing portal for payment methods, invoices, cancellation, and subscription changes. Signed webhooks update the Tekiz customer record and plan quota.

Successful subscription create/update events enable active or trialing routing.
Failed or uncollectible invoices mark the account past due.
Later paid invoice events restore routing unless the account is operator-suspended.

Need help?

Keep billing details in your account.

Use the account page for available payment options and billing status. For an approved invoice, support can confirm a manual or crypto settlement path. It never needs your API key, wallet credentials, or private data.

Use the billing portal for invoices, payment methods, and subscription changes.
Contact support if your account state does not update after a completed payment.
Do not share wallet private keys, seed phrases, provider credentials, prompts, raw responses, or generated API keys.

Safe recovery

What to send when billing or routing looks wrong.

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.

Safe: account email, selected plan, timestamp, HTTP status, safe error class, request id, and non-secret key prefix.
For 401: confirm the key starts with sk_sage_ and is active in the account page.
For 402: use the response upgradeUrl, billingUrl, supportUrl, quota headers, and reset epoch to upgrade, recover payment, or request overflow review without sharing prompts or keys.
For 429: check current plan quota and request-per-minute limits.
For 503: check public status and include timestamp, request id, route profile, and safe model name only.

Open safe support path Run quickstart View status