# Status and metrics

# Status and metrics

You manage an X agent in the dashboard with the switch set to Twitter. Status shows on the agent's entry and activity in the Metrics tab.

## Switching to the agent view

The **Telegram / Twitter** switch is at the top of the dashboard content. It appears only when the account has both a Telegram bot and an X agent. Set it to **Twitter**, then pick the agent under **Currently managing:**.

| Tab | Under Twitter |
| --- | --- |
| Management | Only the **Profile** sub-tab, which lists the account's Telegram bots and agents |
| Whitelist | Add and remove the handles that can trigger the agent |
| Metrics | Mentions, replies and estimated cost |
| Meme Bot | The characters of the matching Telegram bot |
| Support | Support tickets |

**Whitelist** and **Metrics** are hidden while the switch is set to **Telegram**.

- [The whitelist](/x-agents/xagent-whitelist)

## Agent status

| Status | Meaning |
| --- | --- |
| **Setup required** | The keys are not entered. Click **Set up X agent**. |
| **Provisioning** | The deploy is running. A five-step strip refreshes every 6 seconds. |
| **Failed** | The deploy failed. The error shows on the row. Click **Retry provisioning**. |
| **Live** | The agent is connected to X |
| **Idle** | The agent is not connected to X. Causes: an empty whitelist, missing or wrong keys, or an X rate limit. |

A **Live** or **Idle** agent shows a card with its display name, @handle, bio and a **View on X** link. Its Product type reads **Twitter Agent**. Name, handle, avatar and bio come from the X account and refresh when the agent restarts.

- [Deploying an X agent](/x-agents/xagent-deploy)

## The Metrics tab

The tab refreshes every 60 seconds. Click **Refresh** to update it now. It states `Costs are estimated at $0.005 per mention received and $0.01 per reply sent.`

| Card | Shows |
| --- | --- |
| **Mentions received** | Posts X delivered to the agent, ignored ones included. The sub-line reads `N stream events ingested`. |
| **Replies sent** | Successful and failed replies. The sub-line reads `x/y succeeded`. |
| **Cycle cost** | The estimated cost at the two rates above |
| **Cap headroom** | The percent free, and `used/cap used, resets in N d` |

**Cap headroom** counts the whole X project, not only this agent.

Below the cards are three sections: **Daily activity (30d)**, in UTC days, **Per-user attribution (this cycle)** with the columns User, Mentions, Generations, Replies and Cost, and **LoRA usage (this cycle)**.

The footer shows **Stream: live** or **Stream: idle**. Activity is counted from the agent's most recent 10,000 log lines. When that limit is reached, the footer reads `Showing the most recent N log events`.

If X usage cannot be fetched, the tab shows a **Partial data** warning and still loads the rest.

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

## The offline banner

When a key is missing, the **Whitelist** and **Metrics** tabs show a banner: `This agent is offline. Its X API keys are missing, so @<handle> can't read mentions or post replies. Re-enter the four keys from your X developer app to bring it back.`

1. Click **Re-enter keys**.
2. Fill in all four keys.
3. Submit.

A banner then confirms the keys are saved and the agent is restarting. The agent is back on X within a minute.

- [Replacing keys](/x-agents/xagent-api-keys#replacing-keys)

## Pausing and deleting

There is no pause control. To stop replies, remove every handle from the whitelist.

There is no delete control. To delete an agent, open a ticket in the Support tab. The tab shows with the switch set to Twitter.

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