Skip to content

Telegram Bot Guide

The Telegram bot is the easiest way to manage Nexus on your own. From the bot you can automatically get 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

  1. Open Telegram and find @nexus_hubbot.
  2. Send /start.

On the first /start, the bot first asks for the interface language and then the display currency: RUB, USD, EUR, or CNY. After both choices, the bot creates one profile, saves the settings, and shows a new public six-digit Nexus ID together with the main menu.

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.

The More section contains Support, Invite friends, Transfer balance, and Change language. See the Referral program page for the terms.

For a frozen profile, the top level is reduced to Models and More.

Inside More, support, balance transfer, and language remain available even for a frozen profile.

2. Profile Creation

A profile is created after the language and currency choices. It holds your balance, API keys, and their settings. Each Telegram user has exactly one profile, and the profile keeps its own Nexus ID.

Nexus ID is public: use it for payments and support, but not as a password or recovery method. If you already have an older profile and still control it, use the separate balance-transfer flow.

3. Transfer Balance

Use balance transfer when the old Telegram account is still available and its profile has a positive available balance.

  1. In the old Telegram account, open More.
  2. Tap Transfer balance.
  3. The bot will show a one-time command like /start transfer_<token>.
  4. On the target Telegram account, open the link. If this is the first launch, choose the language and currency first; the transfer is then processed automatically.

At apply time, the whole available positive RUB balance is transferred. The source and target remain separate profiles: the Nexus ID, Telegram bindings, API keys, history, payments, and settings do not move.

The link expires after a short time and works once. Invalid, expired, or reused links receive a neutral response. If it expires, create a new link from the source profile.

4. Top Up Your Balance

  1. From the main menu, choose Top up.
  2. Pick the amount.
  3. Choose an available payment method. The list, order, limits, label, and displayed fee come from the payment configuration.
  4. Check the preview: amount, payment method, displayed fee, adjustments, and total credited. When an amount bonus applies, the preview also shows its percentage, for example 5,000 ₽ → 5,400 ₽ (+8%).
  5. Follow the payment link.
  6. To check progress, use the status of your own payment intent; starting another top-up creates a new intent.

If the selected method supports promo codes, the bot lets you enter a code or continue without one. The preview shows the payment amount, amount bonus, promo bonus, and total credited separately.

Balance payment history shows one event with the principal amount, bonus, and total credited. Other balance operations are shown as separate typed events.

A Digiseller post-payment message includes links to the Nexus bot and documentation. If the purchase was made without a Nexus ID, it also contains a one-time activation code and bot deep link. Open the link or choose Top up → Activate purchase and enter the code. The Transaction ID is only for support requests.

The Activate purchase button opens the activation flow for an already paid purchase. Send the one-time code from the payment message, or open the bot with /start pay_<code>. The code is accepted once; invalid, used, and revoked codes have the same neutral response.

After activation, the bot shows the paid amount, adjustments, total credited, final balance, and the assigned Nexus ID. A first-time user is offered an API-key button, followed by Models and Documentation. The activation flow does not ask for a Transaction ID or provide a payment search.

Balance Code

If support sent you a balance code, open Top up → Activate balance code and send the code. This flow does not use links or /start parameters.

A balance code is a support-issued credit, not a purchase payment. It is accepted once; invalid, used, revoked, and expired codes receive the same neutral response. After a successful activation, the bot shows the credited amount and current balance.

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.

5. Issue a Full API Key

After topping up, you can issue a full key with no time limit.

  1. From the main menu, choose Keys.
  2. Tap Issue a key.
  3. The new key gets a sequential profile-local name such as #1, #2, #3.
  4. Copy the new key and store it securely. The bot deletes the plaintext key message automatically.

Use the key as a Bearer token against the base URL https://api.nexus-hub.ru.

6. Name a Key and Set a Spending Limit

Helpful when you run several projects or want to cap usage.

  1. Open Keys. By default the bot shows only active, non-expired keys.
  2. Switch between Active, All, and Revoked when needed. The selected filter and page stay preserved when you open a key card and come back.
  3. Tap the key you want to manage.
  4. Choose Rename to give it a clear name.
  5. Choose one of the 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.

7. Restrict Models per Key

Each API key can have its own model allowlist.

  1. Open Keys and tap the key you want to manage.
  2. Choose Available models.
  3. On the top-level screen, pick one of the presets:
  4. All models for every public model;
  5. Deny all to temporarily block model access for that key.
  6. Then open the model family you want, for example Claude family, Gemini family, or GPT / Codex family.
  7. On the family screen you can:
  8. allow the whole family;
  9. toggle exact public models inside that family.
  10. Each choice is saved immediately. Tap Back to return to the family list.

8. Manage IP Allowlists

You can restrict a key so it only works from trusted IP addresses.

  1. Open Keys and tap the key you want to manage.
  2. Choose IP allowlist.
  3. Add or remove the addresses that are allowed to use the key.

If the allowlist is empty, the key works from any address.

9. Revoke a Key

  1. Open Keys and tap the key you want to manage.
  2. Choose Revoke.
  3. Confirm.

A revoked key stops working right away. Revoke any key you no longer use or that may have leaked.

10. Request and Balance History

  1. From the main menu, choose History.
  2. Pick a range: 24h, 7d, 30d, All time, or Custom.
  3. For Custom, send the start and end dates in DD.MM.YYYY (UTC).
  4. Switch between All, API, and Balance.

The header shows a summary for the selected range: total requests, errors, charged amount, and input/output tokens for charged requests only. Each page has at most five events with expandable details. Table timestamps are always shown in UTC.

Charged requests show their RUB calculation components and actual deduction. Older records without the detailed formula show their tokens and actual deduction with an availability note.

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.

11. Open a Support Ticket

  1. From the main menu, open More.
  2. Choose Support.
  3. Choose a category and, when applicable, a problem type.
  4. Answer only the questions relevant to that category.
  5. Describe the issue, optionally add photos or a document, and choose a contact method.
  6. Check the safe summary and press Create ticket.

For top-up questions, create a support ticket and include the transaction details. If the purchase was made without a Nexus ID, first use the one-time activation code from the post-payment message. Never send a full API key, prompts, or full request bodies.

The draft is kept for a short time, so going back preserves entered answers and a bot restart does not immediately lose the flow.

Under My tickets, you can open a ticket card and see its status, what is happening now, created/updated time, contact, attachment count, your message, and the conversation with support. A ticket can also be waiting for you or an external service. 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.

The history visually separates your messages, support replies, and system events. A New messages divider and an event count mark unread updates; changing a ticket timestamp alone does not create unread state. Private staff notes are never shown to customers.

If the ticket was already marked resolved, closed, or waiting for your reply, your new reply automatically reopens it.

After a resolution, open the ticket card and tell us whether it helped. You may optionally give a score from 1 to 5. If the problem remains, choose Reopen: the problem remains and send a new comment; the ticket will be reopened. Repeating the same submission does not create a duplicate.

When support posts a public reply or changes the ticket status, the bot sends a separate notification with an Open ticket button.

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.

12. Partner Program

Open Partner Program under More to submit an application or check its status. Complete the form step by step: your name or company name, contact, platform links, audience description, average reach, promotion format, payout jurisdiction, and an optional comment. Use the Back button to return to the previous step or leave the form.

You can save an application as a draft, submit it for review, or withdraw it before the review is complete. After submission, the bot shows one of these statuses: Draft, Submitted, Under review, Approved, Rejected, or Withdrawn. The bot sends a separate notification when a decision is made; rejected applications include a safe message with the next action.

Once approved, your partner dashboard is activated automatically and opens to its overview. Campaigns show percentages with up to two decimal places: the reward fund, the partner/customer split and, when configured, a first-top-up bonus. Campaign creation asks for the required fields first; a code is generated automatically and dates and limits are unlimited by default. You can change those optional settings before the first attribution. Referral and accrual lists are shown as tables, with a plain-text fallback for clients that do not support them.

The partner program does not guarantee approval. Available capabilities and terms are determined during review; the interface does not expose public partner tiers or rankings.

13. View Available Models and Prices

  1. From the main menu, choose Models to see the models available to you and their prices in your selected display currency.

The same screen also gives you direct News, Status, and Documentation buttons, while Back returns you to the main menu. News appears when the bot has a channel link configured.

The models screen is split into separate GPT / Codex, Claude, and Gemini family pages. Each family page shows one shared model table with the model, ID, input, output, cache, cache-write, per-request prices, and available endpoints. Prices are stored and calculated in rubles, then displayed in the selected currency.

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.