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

# API keys

> Create, separate, and revoke technical access to your NBQ.

An API key connects a backend to one NBQ and a precise set of permissions. Complete secrets are displayed only when created.

<Frame>
  <img src="https://mintcdn.com/zelinqa-d77427f3/Yj84d-FlY_UhrTB0/images/studio-capture-pending.svg?fit=max&auto=format&n=Yj84d-FlY_UhrTB0&q=85&s=db721b85a66499695ac3f76725245e47" alt="Placeholder for the final API Keys page screenshot" width="1440" height="810" data-path="images/studio-capture-pending.svg" />
</Frame>

## Recommendation

Create at least:

* one `runtime` key per environment for conversations;
* a separate management key only if you automate configuration;
* no public key in a browser or mobile application.

The list displays only a masked form, final characters, status, and non-sensitive metadata. Revocation immediately blocks new calls.

<Card title="Secure an API key" icon="shield-halved" href="/en/security/api-key-safety">
  Review storage, rotation, and exposure-response practices.
</Card>
