> ## Documentation Index
> Fetch the complete documentation index at: https://docs.vetox.io/llms.txt
> Use this file to discover all available pages before exploring further.

# Premium and Manage Bots

> Manage your server premium subscriptions — assign them to servers, extend, transfer ownership, and set up a Custom Bot.

Where a [Custom Bot](/en/premium/custom-bot) is set up and controlled.

<Info>
  Requires **Max+** or **Black+**. The page also lists your subscriptions.
</Info>

## The four-step setup

<Steps>
  <Step title="Create a Discord application">
    In the Discord Developer Portal, create an application and add a bot to it.
  </Step>

  <Step title="Submit your bot token">
    Paste it here. Vetox validates it against Discord before accepting.

    <Warning>
      **The token is write-only** — once submitted you cannot read it back. Save your own copy first.
    </Warning>
  </Step>

  <Step title="Invite the bot to your server">
    Using your own application's invite link.
  </Step>

  <Step title="Done">
    It starts within moments, and the public Vetox bot goes silent in that server.
  </Step>
</Steps>

### What you must provide

|                            |                                 |
| -------------------------- | ------------------------------- |
| **Bot token**              | From the Developer Portal       |
| **Server Members intent**  | Enabled in the Developer Portal |
| **Presence intent**        | Enabled in the Developer Portal |
| **Message Content intent** | Enabled in the Developer Portal |
| Redirect URI               | Optional                        |

<Warning>
  **All three privileged intents are mandatory.** The token is rejected without them, and this is the most common setup failure.
</Warning>

## Branding

Name, avatar, banner, a description of up to 400 characters, and a presence.

<Note>
  Presence must be **Playing**, **Watching**, **Listening** or **Competing** — Discord does not allow bots a plain custom status.
</Note>

<Note>
  Branding updates are additive. Clearing a field leaves the previous value; set a replacement instead.
</Note>

## Transferring

Two-step, and the request expires after **30 minutes**.

<Warning>
  Final once confirmed. The bot leaves the old server and the public bot resumes there.
</Warning>

## Disabling

Stops the bot and **clears the stored token**. Branding and the audit log are kept — resubmit the token to re-enable.

## Audit log

The last 50 actions on your Custom Bot.

## Troubleshooting

<AccordionGroup>
  <Accordion title="My token was rejected">
    Almost always a missing privileged intent. Enable all three, then resubmit.
  </Accordion>

  <Accordion title="The bot will not start">
    Same cause, or the token was regenerated in the Developer Portal after you submitted it.
  </Accordion>

  <Accordion title="It crashed and stopped">
    Three crashes in a minute stops it automatically. Fix the cause — usually a revoked token — then re-enable.
  </Accordion>

  <Accordion title="I am on Max+ and AI is locked">
    Correct. Custom Bot is not a tier change — AI requires Black.
  </Accordion>

  <Accordion title="My bot left another server">
    Expected. A Custom Bot serves one server.
  </Accordion>
</AccordionGroup>

<Card title="Custom Bot" icon="robot" horizontal href="/en/premium/custom-bot">
  What it is and what changes.
</Card>