Skip to main content
The Developer console at app.trynito.ai/api has three tabs: Overview, API keys, and Playground. Pick the organization at the top if you belong to more than one. The API is prepaid. Add funds from Billing; every key in the organization spends from that balance, after any subscription allowance. Creating a key needs an owner or admin role and a funded organization.

​
Create a Key

1

Open API keys

Choose Create key, name it, and pick an expiry: 7, 30, 90, or 180 days, one year, or never.
2

Set a spend cap (optional)

A cap in USD for a daily, monthly, or overall period. Daily and monthly caps reset on the UTC boundary; an overall cap expires the key when reached.
3

Copy the key

It starts with z_sk_ and is shown once. Afterwards the list shows the key’s details, never the key itself.
A key grants full inference access for its organization. Use one key per workload with its own cap, and Revoke when it is no longer needed. Send the key as Authorization: Bearer; the console’s examples use X-API-Key with X-Org-ID, which the gateway also accepts. See Authentication.

​
Overview

For the window you select: spend, requests, and token totals; spend by model and by day; top models by requests; active keys and last use (owners and admins); and a copyable request example. A Free organization with no prepaid balance sees requests and tokens but no spend.

​
Playground

Runs a single non-streaming request so you can confirm a key and a model before writing code. Paste a z_sk_ key, choose a model, set web search and web fetch, and Run. The response and its usage appear alongside a code sample.

​
Keys and the Plugin

The Plugin and the nito command line tool sign in through the browser rather than with a key. Those connections are under OAuth and CLI tokens in Settings > Security.

​
Next

API Quickstart

A first request.

Authentication

Headers and key types.

Billing

Add funds.

Checking Usage

Usage on each surface.

​
Manage keys from your own code

Owners and admins can enable Admin access when creating a key. That key can call the key-management API, provided its owner remains an organization owner or admin. Ordinary application keys default to admin: false; use a separate admin key for provisioning and rotation.