# Deploying an X agent

# Deploying an X agent

You buy Heavy+, pay, then enter your four X keys. The X agent deploys first and the matching Telegram bot deploys right after it.

## The plan

#### Heavy+ ($499/mo)

| Setting | Value |
| --- | --- |
| Price | $499/mo |
| X agents per purchase | One |
| Telegram bot | A matching Telegram bot on the same character, included |
| Delivery | Up to 4 hours |
| Payment window | 20 minutes |

## Setup

1. Pick **Heavy+** in the package picker. From the dashboard: Management → **Add another bot** → Heavy+.
2. **Name your character.** Letters, digits and underscore, up to 31 characters. The name is the trigger word on Telegram and on X.
3. **Set up your bot.** Display Name (up to 64 characters), Bot username (up to 32) and Bot bio (up to 70). These are the Telegram bot's fields. No X field is asked here.
4. Upload 10 to 80 training images, review the **Order summary** and pay.
5. After the payment confirms, the images upload and the bot saves. The **Connect your X account** card then appears. The card has no skip button.
6. Fill in the four keys and click **Deploy X Agent**. The card's footer reads `Telegram bot deploys right after the X agent.`
7. When the checklist finishes, the Telegram bot deploys. The dashboard opens afterwards.

- [Your X API keys](/x-agents/xagent-api-keys)

## The deploy checklist

**Deploying your X agent** shows five stages in order.

1. `Creating DNS Record (memescale.ai)`
2. `Creating User Folder + Config`
3. `Issuing HTTPS webhook endpoint`
4. `Pushing agent config`
5. `Starting X agent service`

After 120 seconds a notice appears below the checklist saying that certificate issuance can take a few minutes. Keep waiting.

## Entering keys later

If you close the tab at the keys step, resuming skips to the Telegram bot deploy. The agent waits for its keys.

1. Open Management → Profile.
2. Find the agent. It shows **Setup required**, and its handle line reads `X handle attaches after you paste keys`.
3. Click **Set up X agent**. The **Connect your X account** card opens.
4. Fill in the four keys and submit the card.

If the agent could not be created at all, a recovery banner above the Heavy+ Telegram bot has a **Contact support for X agent setup** link.

## When a deploy fails

| Message | What to do |
| --- | --- |
| Error card titled **X agent provisioning failed** | Click **Retry X agent** to deploy again with the keys already entered. Click **Continue Telegram setup** to deploy the Telegram bot first and retry the agent from the dashboard. |
| **Failed** in Management → Profile, with the error text, `Stalled during "<stage>"` or `Provisioning did not complete` | Click **Retry provisioning**. It asks for all four keys again. |
| `Missing X API field: <field>` | Fill in the field the message names. |
| `No Twitter Combo bot slot available. Each Twitter Combo purchase covers one X agent. Contact support if you believe this is incorrect.` | One purchase covers one X agent. Open a support ticket if the message is wrong. |

A failed agent does not use a Heavy+ slot.

- [Support](/group-access/access-reference#support)

## After the deploy

Add at least one handle to the whitelist. Until then the agent does not connect to X and shows **Idle**.

A post that triggers the agent before the character finishes training gets no reply.

- [The whitelist](/x-agents/xagent-whitelist)
- [How the agent replies](/x-agents/xagent-replies)