Use cases¶

Nexus exposes one account and API surface for different kinds of work. Pick the shortest path that matches the thing you are building.

Personal use

Start with the Telegram bot, a trial or a small top-up, then issue a separate key for each project

Quick start

Business and teams

Keep one profile balance while using named keys with model policies, spending limits, IP allowlists and independent revoke actions

Bot and profile

Automation

Use GET /v1/models at startup, select a visible model, and handle the structured error envelope and x-request-id in logs

API reference

Chat bots

Use the same API key lifecycle as any other application. Keep prompts and keys in your own secure storage and send only the request shape your protocol needs

API reference

Developers

Choose OpenAI-compatible, Anthropic-compatible or Gemini-compatible routes and start with the protocol-specific quickstart

Client setup

Coding tools

Use Codex, Claude Code or CC Switch. Nexus does not claim official partnership with any third-party brand

Client setup

A safe integration sequence¶

Authenticate with a key from the Telegram bot.
Read the key-specific model catalog.
Send a minimal request with an explicit output limit.
Record x-request-id and the public error code, never a key or prompt.
Treat a missing or contradictory usage result as not charged; do not invent a later charge in client code.