Telegram Bot Guide¶
The Telegram bot is the easiest way to manage Nexus on your own. From the bot you can create a profile, top up your balance, issue and revoke API keys, set limits, open a support ticket, and check the model list.
The bot handle is @nexus_hubbot
1. Start the Bot¶
- Open Telegram and find @nexus_hubbot.
- Send
/start. - Choose your language when prompted: 🇷🇺 Русский or 🇬🇧 English.
After you pick a language, the bot opens the main menu. For an already linked account, an explicit /start now sends the Nexus Hub logo as a separate photo first and then posts a separate editable menu message. Repeating /start creates a fresh logo + menu pair.
The main menu for an active profile is laid out as a large Top up button, then a Keys + Models row, then a History + More row. For administrators, Admin remains a separate button.
The More section contains Support, I paid but see no balance, Transfer to new Telegram, Change language, public service status, documentation, and an optional news link.
For a frozen profile, the top level is reduced to Models, More, and, if applicable, Admin.
Inside More, support, payment recovery, language, and documentation remain available even for a frozen profile.
The command menu (the / button in Telegram) is now intentionally reduced to /start for every role. All user scenarios open through the bot's inline buttons.
2. Create or Restore Access¶
A profile holds your balance, your API keys, and their settings.
- After choosing a language, pick one of the options:
- Create new Nexus account if you are starting from scratch;
- I already have Nexus ID if you still have access to the old Telegram account and need recovery or payment restoration.
- Before creating a new account, the bot shows a warning that it will create a separate Nexus ID with a separate balance.
Nexus ID is public: use it for payments and support, but not as a password. Direct /login by Nexus ID is intentionally disabled.
When to choose “Create new Nexus account”¶
Use this option only if:
- you have never created a Nexus account before;
- you have never topped up before;
- you do not need to recover an older balance or older API keys.
Important: the bot creates a separate Nexus ID and a separate balance. If you already had another account, money and keys will not be merged automatically.
When to choose “I already have Nexus ID”¶
Use this option if:
- you already have an existing Nexus account;
- you still have access to the old Telegram account;
- you want to move the binding to a new Telegram account without creating a new balance or a new Nexus ID.
In this flow, Nexus ID itself is not used as a password. Recovery uses a one-time transfer link.
When to choose “I paid but see no balance”¶
Use this option if:
- you paid through Digiseller / Plati but the balance did not appear where you expected;
- the payment went to the wrong Nexus ID;
- the profile was created without Telegram binding;
- you are not sure which account received the top-up.
The bot will ask for an order number, invoice number, or another payment reference and then try to resolve it safely.
3. Move the Account to a New Telegram¶
This flow is for cases where the old Telegram account is still available.
- In the old Telegram account, open More.
- Tap Transfer to new Telegram.
- The bot will show a one-time command like
/start transfer_<token>. - Open the bot from the new Telegram account and send that command.
- After confirmation, the new Telegram account will get access to the same Nexus account.
Important details:
- the transfer link is one-time;
- it expires after a short time;
customer_id, balance, history, and API keys do not change;- the old Telegram account loses the binding to that Nexus account.
If the bot says the link expired, generate a new one from the old Telegram account.
4. If You Paid but See No Balance¶
- From the recovery screen after I already have Nexus ID, or from More, choose I paid but see no balance.
- Send one of the payment identifiers:
- Digiseller / Plati order number;
- invoice number;
- another payment reference you received after the purchase.
- The bot will inspect the payment and choose one of these outcomes:
- automatically bind the found account to your Telegram;
- automatically move the top-up to your current Nexus account;
- create a manual review request if the case is ambiguous.
Automatic transfer is allowed only for safe cases. If the mistaken profile already spent balance, used API keys, or has other ambiguity signals, the bot will not move the money automatically.
If the bot creates a manual review request, keep its identifier so you can share it with support if needed. If the bot can safely bind or transfer the payment automatically, it sends a separate notification with the amount and the resulting balance.
5. Top Up Your Balance¶
- From the main menu, choose Top up.
- Pick the amount.
- Choose Digiseller as the payment method.
- Complete the payment through the Digiseller checkout.
- The bot confirms once the balance is credited in rubles.
The credit notification shows the amount, the current balance, and a button for the next step: return to the main menu or open the top-up screen again.
The balance is shared across all API keys on your profile. Check the Nexus ID shown in your profile before paying: topping up a different Nexus ID credits a different account.
6. Issue a Full API Key¶
After topping up, you can issue a full key with no time limit.
- From the main menu, choose Keys.
- Tap Issue a key.
- The new key gets a sequential profile-local name such as
#1,#2,#3. - Copy the new key and store it securely. The bot deletes the plaintext key message automatically after the configured TTL.
Use the key as a Bearer token against the base URL https://api.nexus-hub.ru.
7. Name a Key and Set a Spending Limit¶
Helpful when you run several projects or want to cap usage.
- Open Keys. By default the bot shows only active, non-expired keys.
- Switch between Active, All, and Revoked when needed. The selected filter and page stay preserved when you open a key card and come back.
- Tap the key you want to manage.
- Choose Rename to give it a clear name.
- Choose one of the inline limit options to set or clear a spending limit.
A limit caps how much a single key can spend; once reached, that key stops until you raise the limit. The profile balance stays shared across keys.
8. Restrict Models per Key¶
Each API key can have its own model allowlist.
- Open Keys and tap the key you want to manage.
- Choose Available models.
- On the top-level screen, pick one of the presets:
- All for every public model;
- None to temporarily block model access for that key.
- Then open the model family you want, for example Claude family, Gemini family, or OpenAI/Codex family.
- On the family screen you can:
- allow the whole family;
- toggle exact public models inside that family.
- Tap Back to return to the family list without applying.
- Tap Apply only when the final policy looks right.
Until you tap Apply, the bot keeps the changes only as a draft. Back on the top-level screen and returning from a family screen do not update the key.
The bot shows only public models from the current catalog. To confirm the final access policy of a specific key, check the API response for that key:
curl -H "Authorization: Bearer $NEXUS_API_KEY" \
https://api.nexus-hub.ru/v1/models
9. Manage IP Allowlists¶
You can restrict a key so it only works from trusted IP addresses.
- Open Keys and tap the key you want to manage.
- Choose IP allowlist.
- Add or remove the addresses that are allowed to use the key.
If the allowlist is empty, the key works from any address.
10. Revoke a Key¶
- Open Keys and tap the key you want to manage.
- Choose Revoke.
- Confirm.
A revoked key stops working right away. Revoke any key you no longer use or that may have leaked.
11. Request and Balance History¶
- From the main menu, choose History.
- Pick a range: 24h, 7d, 30d, All time, or Custom.
- For Custom, send the start and end dates in
DD.MM.YYYY. The bot interprets them inMSK(UTC+3), and the end date stays inclusive for you. - Switch between All, API, and Top-ups. The selected range stays preserved while you change filters or pages.
The header shows your current balance and a summary for the selected range: confirmed spend, input/output tokens, and request count. Table timestamps are always shown in MSK.
If your Telegram client or server cannot render the rich table, the bot automatically falls back to the regular text list with the same keyboard.
12. Open a Support Ticket¶
- From the main menu, open More.
- Choose Support.
- Describe your question or issue.
- Choose how support should contact you: via your Telegram account or a contact method you enter manually.
- Send it. The bot creates the ticket and stores the selected contact method.
Under My tickets, you can open a ticket card and see its status, description, public support comments, and attachment count. The Reply button opens a draft where you can add text, photos, and documents. Delivery happens only after you press Send, and Open attachments asks the bot to resend the saved files without downloading them to the server again.
If the ticket was already marked resolved or closed, your new reply automatically reopens it.
When support posts a public reply or changes the ticket status, the bot sends a separate notification with an Open ticket button. Admins, in turn, receive their own notifications about new tickets, your public replies, reopen events, and the number of new attachments. Those notifications do not copy the full comment text, ticket description, or file metadata.
All timestamps in ticket cards are shown in MSK.
If the issue is related to a mistaken top-up or access recovery, include these details in the ticket description right away:
- your current Nexus ID;
- the order number or invoice number;
- what exactly happened: a new account was created, the wrong Nexus ID was used, the balance is missing, or the old Telegram account is gone.
13. View Available Models and Prices¶
- From the main menu, choose Models to see the models available to you and their prices in rubles.
The same screen also gives you direct Status and Documentation buttons, while Back returns you to the main menu.
The models screen is split into separate Claude, Gemini, and GPT / Codex family pages. Each page header includes a branded custom-emoji logo, and table cells are centered for a cleaner layout. Each family page shows one shared model table with the endpoint, input-token prices, output-token prices, and available cache-related prices. The table footer shows the real refresh interval for the data.
If your Telegram client cannot display the rich table, the bot automatically falls back to a simpler text list of prices instead of failing.
The list depends on your key settings, so rely on /v1/models for your own key rather than someone else's example.
Stay Updated¶
News and announcements are posted in our channel.