Status¶

Developer preview

The Telbox developer platform is in preview. The external API-key path (apikey_auth_enabled) is off in production until launch, so the REST, MCP, and OAuth surfaces are reachable today only with a developer session JWT from the console — not with tb_live_… keys. There is no published uptime SLA or availability target for the developer platform yet; a formal status page and SLA are part of the launch.

We don't publish fabricated uptime figures. Until a dedicated status dashboard exists, here is how to check things yourself.

Is the API up?¶

The API exposes an unauthenticated liveness probe. A 200 means the API process is serving requests:

curl -i https://api.telbox.ai/v1/healthz

What a 200 does and doesn't mean

/v1/healthz is a lightweight liveness probe — a 200 confirms the API is reachable and serving, not that every downstream subsystem (database, queue, model provider) is healthy. Authenticated endpoints can still return 4xx for auth or quota reasons even while this probe is green; see Errors.

Is the developer platform reachable for me?¶

Because the external key path is gated, the honest way to confirm your access is to make a real authenticated call with your developer session and read the result:

# Replace with the session JWT the developer console mints over email + OTP.
curl -i https://api.telbox.ai/v1/agent-templates \
  -H "Authorization: Bearer $TELBOX_SESSION_JWT"

A 200 with a template list means your session is live and the Agents surface is serving. A 401/403 points at auth (see Authentication), not necessarily an outage.

This docs site¶

docs.telbox.ai is a static site on Cloudflare Pages, independent of the API — it can be up while the API is down, and vice versa. If a page 404s or looks stale, it's a build/deploy issue with the docs, not an API incident.

Where to check¶

Surface	How to check	Notes
API liveness	`GET https://api.telbox.ai/v1/healthz`	Unauthenticated; `200` = serving.
Your Agents access	`GET /v1/agent-templates` with your session JWT	`200` = your session + the surface are live.
Developer console	https://developers.telbox.ai	Sign-in, key management, usage.
Docs	https://docs.telbox.ai	Static; separate from the API.

When something looks wrong, Errors and Rate Limits & Quotas explain the difference between an outage, an auth problem, and a quota limit. A public status dashboard with uptime history will ship with launch.