Hosted API reference

Connect a client to the TEKIZ.AI API.

Use the hosted base URL and a generated sk_tekiz_* key. Activate your free evaluation or a plan in Account. Use available hosted capacity or provider access you are authorized to connect. Start with tekizai/auto, then check /v1/models for the profiles available to your account.

Create API key Create a new API key Ask about managed access Quickstart Gateway migration Troubleshooting Model catalog Pricing

Create an account now. Connect an authorized provider or add billing when you are ready to route.

Hosted API base URL: https://api.tekiz.ai/v1. Browser account and billing UI live at https://app.tekiz.ai.

Auth

Bearer key

Send Authorization: Bearer sk_tekiz_.... Generated keys are scoped to a TEKIZ.AI account and should be rotated from the account page if exposed.

OpenAI

Compatible clients

Point OpenAI-compatible SDKs and tools at https://api.tekiz.ai/v1. Use tekizai/auto after your account has active routing. On Pro or Max, select tekizai/fusion when the required models are online and your account shows that profile.

Limits

Request limits

Plans enforce monthly request quotas and request-per-minute limits. Responses include safe quota and rate-limit headers for client backoff.

Client setup

Send your first chat request.

export OPENAI_BASE_URL=https://api.tekiz.ai/v1
export OPENAI_API_KEY=sk_tekiz_your_key_here

curl "$OPENAI_BASE_URL/chat/completions" \
  -H "Authorization: Bearer $OPENAI_API_KEY" \
  -H "User-Agent: OpenAI-compatible-client/1.0" \
  -H "Content-Type: application/json" \
  -d '{
    "model": "tekizai/auto",
    "messages": [{"role": "user", "content": "Return ok."}]
  }'

Before sending this request, activate your free evaluation or a plan. Your account needs an available hosted model or an authorized provider route. OpenAI-compatible Python and JavaScript SDKs can use the same base URL and key. If a raw HTTP client gets Cloudflare 1010, set a descriptive User-Agent and retry.

Endpoint Auth Purpose Notes
GET /v1/models Generated key Authenticated model list for OpenAI-compatible clients. Use this to verify keys before wiring agents. Anonymous requests return guided 401.
POST /v1/chat/completions Generated key OpenAI-compatible chat completions with routing profiles and provider fallback. Supports common chat client flows, including streaming-shaped compatibility responses. tekizai/fusion is a premium chat model alias, and {"type":"tekizai:fusion"} is accepted as a premium server tool for Pro/Max-style synthesis.
POST /v1/responses Generated key OpenAI Responses-compatible shape for Codex and other tools that use the Responses API. Codex profiles should set wire_api = "responses". Pro and Max requests may attach {"type":"tekizai:fusion"} as a server tool.
GET /model-catalog Public metadata Public model families and examples for catalog pages. Discovery only. Live /v1/models and model traffic still require an active generated key.
GET /pricing Public metadata Hosted plans, request limits, API base URL, and checkout links. Managed model access remains disabled until provider permission, usage limits, and private audit records are ready.

Responses API

Use the Responses API for Codex-style clients.

curl https://api.tekiz.ai/v1/responses \
  -H "Authorization: Bearer $OPENAI_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "model": "tekizai/frontier",
    "input": "Return one sentence about TEKIZ.AI."
  }'
Signal Header or field When to use it
Authentication WWW-Authenticate, apiKeyPrefix, accountUrl, accountSetupUrl, primaryActionUrl, managedAccessUrl, keyRecoveryUrl If a key is missing or invalid, create a new key from your account and retry. The response can also link to same-email setup recovery or a separate managed-access review.
Billing or quota X-Quota-Limit, X-Quota-Used, X-Quota-Remaining, X-Quota-Period, X-Quota-Reset, upgradeUrl, billingUrl, supportUrl Show current usage, the monthly reset time, and links to account or billing help.
Rate limit Retry-After, X-RateLimit-Limit, X-RateLimit-Remaining, X-RateLimit-Reset Wait for the indicated time before retrying a request that exceeded the per-minute limit.
Reliability X-TEKIZAI-Router-Retry-Count, status page health, selected upstream Understand failover behavior when a backend returns 401, 429, 502, 503, or 504.

Boundary

The hosted API is authenticated and customer-authorized.

  • Model requests under /v1/* require a generated account key. A missing key returns setup guidance.
  • Connect only provider access you are authorized to use. Personal provider accounts stay with their owners.
  • Do not send prompts, provider credentials, OAuth tokens, generated keys, private keys, session cookies, raw provider responses, or customer data in support requests.