Skip to main content

​
Keys

Keys are created in the developer console at app.trynito.ai/api by an owner or admin. The secret is shown once; the gateway keeps only a hash. Lost a key? Revoke it and create another. A key belongs to an organization, and inference usage is metered against that organization. A personal account is its own organization. Keys have no per-feature scopes; the way to bound one is an optional daily, monthly, or overall spend cap, set at creation. When the cap is reached the key stops working. API access is prepaid. See Plans.

​
Public Model Discovery

GET /v1/models and GET /api/v1/models are public. They return the same catalog with or without credentials or an organization header. Browsing the catalog requires no prepaid balance. Inference requests still require authentication and account eligibility. See List models.

​
Sending the Key

Authorization: Bearer <key> is the header; X-API-Key: <key> is also accepted for clients that only support an API-key header. On routes that require authentication, a missing, malformed, revoked, or expired key returns 401. Rate limits are checked in the same step: over a limit returns 429 with Retry-After, X-RateLimit-Limit, X-RateLimit-Remaining, and X-RateLimit-Reset.

​
Token Prefixes

CLI tokens are accepted on the inference routes. MCP tokens are bound to the MCP endpoint and rejected elsewhere.

​
Errors

  • 401. Check the prefix is z_sk_ and there is one space after Bearer.
  • An MCP token on the HTTP API. Use a z_sk_ key.
  • A key in source control. Keys are full organization credentials. Keep them in environment variables or a secrets manager; rotate by revoking and recreating.

Developer Console

Keys, usage, playground.

Secure API Key Handling

Store, cap, rotate.

Rate Limits

The limit headers.

​
Automating key management

An owner or admin can create a key with Admin access in the developer console, then use it to create, list, and revoke API keys. Ordinary inference keys default to admin: false. Keep the admin credential separate from application keys; newly created keys have independent spend caps and expiry.