Live routing health.

# Tekiz hosted setup
# 1. Create your generated key:
# https://app.tekiz.ai/account.html?plan=pro&start=create_key&utm_source=status&utm_medium=setup-copy&utm_campaign=sage-router-launch&utm_content=status-revenue-setup
# 2. Replace the placeholder below with the one-time sk_sage key.

export OPENAI_BASE_URL=https://api.tekiz.ai/v1
export OPENAI_API_KEY=sk_sage_your_key_here
export SAGE_ROUTER_MODEL=sage-router/frontier

curl "$OPENAI_BASE_URL/models" \
  -H "Authorization: Bearer $OPENAI_API_KEY"

Tekiz one-subscription managed-access review

Request: review Tekiz as one subscription for hosted routing, quotas, failover, and Max implementation support.
Intent: one-subscription
Provider access posture: needs-managed-access
Target provider family: mixed-frontier
Commercial preference: one-subscription
Support need: managed-provider-review
Target launch window: this-month

Review URL: https://tekiz.ai/managed-access?intent=one-subscription&utm_source=status&utm_medium=managed-access&utm_campaign=sage-router-launch&utm_content=status-one-subscription-packet©_open=1#managed-access-direct-contact-primary

Boundary: managed provider access is disabled until provider authorization, provider terms acknowledgment, an authorized provider allowlist, a private cost model, positive unit economics, quotas, audit events, and acceptable-use controls pass.
Provider families under review: Ollama/Ollama Cloud, OpenAI, and Anthropic. OpenRouter stays BYOK unless separate managed-access authorization is added later.
Immediate fallback: create a Max BYOK setup key at https://app.tekiz.ai/account.html?plan=max&start=create_key&utm_source=status&utm_medium=managed-access&utm_campaign=sage-router-launch&utm_content=status-one-subscription-packet

Do not paste prompts, provider credentials, OAuth tokens, generated API keys, private keys, cookies, raw provider responses, or customer data.

Tekiz one-subscription private-beta contact request

Work email: <work email>
Intent: one-subscription
Deployment preference: hybrid hosted edge + private Tailnet
Expected monthly routed requests: 50k to 200k
Provider access posture: needs-managed-access
Target provider family: mixed-frontier
Commercial preference: one-subscription
Support need: managed-provider-review
Target launch window: this-month

Review URL: https://tekiz.ai/managed-access?intent=one-subscription&utm_source=status&utm_medium=managed-access-contact&utm_campaign=sage-router-launch&utm_content=status-contact-packet©_open=1#managed-access-direct-contact-primary
Immediate fallback: https://app.tekiz.ai/account.html?plan=max&start=create_key&utm_source=status&utm_medium=managed-access-contact&utm_campaign=sage-router-launch&utm_content=status-contact-packet

Boundary: this is a contact request only. Managed provider access stays disabled until provider authorization, provider terms acknowledgment, an authorized provider allowlist, a private cost model, positive unit economics, quotas, audit events, and acceptable-use controls pass.

Do not paste prompts, provider credentials, OAuth tokens, generated API keys, private keys, cookies, raw provider responses, actual provider costs, authorization references, or customer data.

Tekiz managed provider authorization handoff

Use when one-subscription demand exists but provider resale is still gated.
Purpose: request written provider authorization for Ollama, OpenAI, and Anthropic managed-access review before any public entitlement is enabled.
Boundary: copy-only operator handoff. This does not send provider email, acknowledge provider terms, stage authorization evidence, write provider costs, change prices, deploy Cloud Run, or enable managed resale.

Recommended command order:
scripts/configure_managed_provider_resale_readiness.sh --provider-source-review-packet
scripts/configure_managed_provider_resale_readiness.sh --provider-outreach-packet
scripts/configure_managed_provider_resale_readiness.sh --provider-reply-triage-packet
scripts/configure_managed_provider_resale_readiness.sh --authorization-ledger-template

After an operator actually uses or shares the outreach packet:
scripts/configure_managed_provider_resale_readiness.sh --record-provider-outreach

After a provider replies, store the reply only in the private system of record, then record a private evidence reference only after review. Keep OpenRouter BYOK-only unless separate written managed-access authorization is added.

Do not paste prompts, provider credentials, OAuth tokens, generated API keys, private keys, cookies, raw provider responses, actual provider costs, provider agreements, provider account IDs, authorization-reference values, or customer data.

Tekiz hold-safe revenue handoff

Use when activation follow-up sends are held by operator decision and managed provider resale is still gated.
Effect: copy-only operator packet for setup-copy recovery, founder-sales outreach, and managed-access contact capture.
Boundary: this does not send email, approve activation sends, expose customer data, acknowledge provider terms, stage costs, change prices, or enable managed resale.

This status-page packet combines the setup bundle, recommended founder-sales reply, and managed-access contact request above. Copying it records setup-copy, founder-sales, and managed-access handoff telemetry only after the operator uses the button.

Metrics recorded when copied:
- status_first_request_setup_copied / operator-first-request-setup
- outreach_snippet_copied / operator-hold-safe-revenue-packet
- operator_managed_access_packet_copied / hold-safe-managed-access-contact-packet

Use one no-secret snippet per warm conversation. Do not paste prompts, provider credentials, OAuth tokens, generated API keys, private keys, customer data, raw provider responses, provider agreements, or private provider costs.

Tekiz signup-to-key activation approval

Use when no-key signup follow-ups are queued but real sends still need explicit operator approval.

Refresh the no-secret aggregate packet:
scripts/summarize_sagerouter_launch_funnel.sh --days 30 --approval-packet --verify-recovery --verify-auth-repair

Refresh the persistent review worksheet:
scripts/update_activation_approval_review.sh --days 30 --write

Record terminal review after an operator actually reviews the packet:
scripts/summarize_sagerouter_launch_funnel.sh --days 30 --record-activation-approval-review --verify-recovery --verify-auth-repair

Review worksheet path:
docs/launch/execution/activation-approval-review.md

Approval boundary:
- This packet does not send email, trigger recovery links, write customer records, repair auth links, deploy infrastructure, or change billing state.
- The review recording command does not approve a send; run it only after actual operator review so activation-review work is measured.
- Real sends require a fresh approvalPacketIssuedAt from the current packet, private operator auth, trusted Tekiz origin, and sendConfirmation=SEND_ACTIVATION_FOLLOWUPS.
- Review-only missing_auth_user rows stay excluded until auth repair or explicit exclusion is reviewed.

Do not paste emails, customer IDs, generated keys, key hashes, prompts, OAuth tokens, provider credentials, raw campaign URLs, raw provider responses, or private funnel rows.

scripts/update_activation_approval_review.sh --days 30 --write

scripts/summarize_sagerouter_launch_funnel.sh --days 30 --record-activation-approval-review --verify-recovery --verify-auth-repair

Private launch funnel required for approve/hold decisions.

Public /pricing metadata cannot verify whether the last approval packet covers the live sendable queue.
Open https://app.tekiz.ai/launch-funnel.html#activation-approval-decision after refreshing the no-secret approval packet.

Do not copy approve/hold decisions from the public status page.

Subject: Finish your Tekiz setup key

You started Tekiz setup, but the hosted API key step is not complete yet.

Start here with the same email or account you used before:
https://tekiz.ai/setup-key-recovery?plan=pro&utm_source=status&utm_medium=operator-followup&utm_campaign=signup_to_key_recovery&source_surface=status_no_key_recovery

If you are already signed in, create the generated setup key here:
https://app.tekiz.ai/account.html?plan=pro&start=create_key&utm_source=status&utm_medium=operator-followup&utm_campaign=signup_to_key_recovery&setup=status-no-key-recovery&source_surface=status&next=generated-key

After the sk_sage setup key exists, verify the endpoint:
OPENAI_BASE_URL=https://api.tekiz.ai/v1
model=sage-router/frontier

Boundary: use this as a no-secret manual follow-up only. Do not include prompts, provider credentials, OAuth tokens, generated API keys, private keys, cookies, raw provider responses, customer IDs, private funnel rows, or provider costs.