> ## 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.

# Introduction

> What the Nito API is.

You authenticate once with an organization key, send a request in the OpenAI or Anthropic shape, and get the reply in that shape. The model ID selects the model and the privacy level it runs at.

## Three Things Define the API

* **One key, every leading model.** A `z_sk_` key reaches the whole [catalog](/models). You select a model by ID and never hold accounts with the model makers.
* **The privacy level travels with the model.** Each catalog entry runs at Anonymous, Private, Confidential, or Encrypted. Frontier models run anonymized. Open-weight models run with zero data retention upstream, and `:confidential` runs them inside sealed hardware. See [Privacy Levels at a Glance](/models/privacy-levels-at-a-glance).
* **Attestation you can verify.** For Confidential calls, Nito gathers the evidence, binds it to a challenge, and returns it through `GET /api/v1/attestation`. See [How Attestation Works](/privacy/tee-attestation/how-attestation-works).

## The Model ID Carries Two Decisions

The base ID names the model. A `:confidential` suffix asks for the attested variant. There is no privacy field in the request body.

```text theme={"theme":{"light":"github-light","dark":"github-dark"}}
z-ai/glm-5.2                 Private
z-ai/glm-5.2:confidential    Confidential, with attestation evidence
```

A level never silently weakens. If a model cannot serve the level you asked for, the call is rejected before any provider work.

## Principles

* **Nito stores nothing you send or receive.** Prompts, completions, reasoning, tool calls, and file contents are request-local. See [Data Retention and Visibility](/privacy/data-retention-and-visibility).
* **Stronger levels narrow the options.** Fewer models, some features off. Match the level to the work by picking the model.
* **Attested, verifiable.** Nito brokers the evidence; you verify it.
* **Compatibility first.** Most integrations are a base-URL change.

## Boundaries

* Nito does not run your function tools. The model asks, your code runs the function and returns the result.
* Nito is a gateway, not a model. You always name one.
* Nito keeps no conversation history.

## Next

<CardGroup cols={3}>
  <Card title="How the API Works" icon="gears" href="/api/get-started/how-nito-works">
    The request lifecycle.
  </Card>

  <Card title="Quickstart" icon="play" href="/api/get-started/quickstart-60-seconds">
    A working response in minutes.
  </Card>

  <Card title="Privacy Overview" icon="shield-check" href="/privacy/overview">
    The four levels.
  </Card>
</CardGroup>


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