> ## Documentation Index
> Fetch the complete documentation index at: https://docs.trynito.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# Developer Console

> API keys, spend caps, usage, and the Playground at app.trynito.ai/api.

The Developer console at [app.trynito.ai/api](https://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](/plans/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

<Steps>
  <Step title="Open API keys">
    Choose **Create key**, name it, and pick an expiry: 7, 30, 90, or 180 days, one year, or never.
  </Step>

  <Step title="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.
  </Step>

  <Step title="Copy the key">
    It starts with `z_sk_` and is shown once. Afterwards the list shows the key's details, never the key itself.
  </Step>
</Steps>

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](/api/get-started/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](/web-app/settings).

## Next

<CardGroup cols={2}>
  <Card title="API Quickstart" icon="rocket-launch" href="/api/get-started/quickstart-60-seconds">
    A first request.
  </Card>

  <Card title="Authentication" icon="key" href="/api/get-started/authentication">
    Headers and key types.
  </Card>

  <Card title="Billing" icon="money-bill" href="/plans/billing">
    Add funds.
  </Card>

  <Card title="Checking Usage" icon="gauge" href="/plans/checking-usage">
    Usage on each surface.
  </Card>
</CardGroup>

## 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](/api/api-reference/api-keys), 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.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.