Introduction

Getting access

An API key is a JWT of your Aist Ai account. You can issue one yourself in a couple of minutes, and we will set up companies together with you.

Self-serve

  1. Sign in to Aist Ai at chat.aist-ai.com with email, phone, VK ID or Yandex ID. No account yet? Sign up right there.
  2. Issue a key — open “Настройки” (Settings) → “API-ключи” (API keys), name the key (for example, after your project) and press “Выпустить” (Issue). The Issue a key link opens that section directly; if you're not signed in, it asks you to sign in first.
  3. Store it — the key is shown only once and the server doesn't keep it. Put it in an environment variable or a secrets manager, for example AIST_AGENT_TOKEN.
  4. Check it — paste the key into the dashboard: it shows the expiry date, your limits, the available assistants and ready-to-run code for the first request. From code, GET /api/me returns the same.
What the key gives you
The key is valid for one year. The API gives you the same assistants as the app: the catalog plus your own from “Мои ассистенты” (My assistants) — GET /api/assistants returns the list. Tasks draw on your account balance just like chat messages do; if the balance runs out, the task fails with Insufficient balance.

Revoking a key

In the same “API-ключи” (API keys) section, every key has its own revoke button. Aist Backend stops accepting a revoked key immediately: requests for assistants and files get 401 Token revoked, and tasks fail with the same error. You can issue several keys — say, one per service — so you can revoke them one at a time.

For companies

Get in touch if you need:

  • an assistant built for your use case — with its own instructions, knowledge base and tools;
  • team members and a shared balance in an organization;
  • a contract for a legal entity and electronic document exchange;
  • help with an integration or a question about the API.

An assistant built for you may not appear in the public catalog: we'll send you its assistant_id, and you create tasks with it as usual.

Next steps

Quick start — your first task in two requests; Authentication — how the token works.