Skip to content

Service Overview

What Nexus Is

Nexus is a general AI API for a wide range of tasks. It accepts requests from applications, automations, chat bots and CLI clients, validates the key, and returns a response in the selected compatible protocol.

For users, this means:

  • no need to set up separate foreign access;
  • you can keep using familiar CLI tools;
  • the key, balance, and model list are managed in one place;
  • support is available in Russian, and documentation is available in Russian and English.

How Access Works

Each Nexus API key is configured separately. Every key has:

  • its own list of allowed endpoints;
  • its own list of allowed models.

The balance is tracked at the Nexus profile level, and multiple keys on the same profile spend the shared profile balance.

That means two keys can see different models and different endpoints. Always check the current list with GET /v1/models.

What Is Supported

Nexus supports:

  • GET /v1/models to check which models your key can use;
  • GET /v1/balance to check the current profile balance;
  • Realtime-compatible WebSocket clients via GET /v1/realtime;
  • Claude Code via POST /v1/messages;
  • token counting for Claude-compatible clients via POST /v1/messages/count_tokens;
  • Codex via POST /v1/responses;
  • compact response workflows via POST /v1/responses/compact;
  • OpenAI-compatible clients via POST /v1/chat/completions;
  • legacy OpenAI-compatible workflows via POST /v1/completions.
  • Gemini-compatible discovery and generation, token-counting and embedding actions under /v1beta.

The detailed endpoint list is on the Supported Endpoints page.

Public status for the Nexus API, model compatibility, documentation and Telegram bot is available at status.nexus-hub.ru.

Streaming

Streaming is supported on:

  • POST /v1/chat/completions;
  • POST /v1/messages;
  • POST /v1/responses;
  • POST /v1/responses/compact;
  • POST /v1beta/models/{model}:streamGenerateContent.

How Pricing Works

Pricing is based on actual model usage or a fixed per-request price. Token-based pricing uses input, cached input, cache write, and output categories.

Complete usage is charged after the response; missing or contradictory usage is left uncharged without a later backcharge.

GET /v1/realtime follows the same post-fact rule and charges only reliable terminal usage.

More details: Pricing and Balance