Manage an EMQX Agents Deployment
Use the EMQX Agents deployment pages to monitor Credits usage, view deployment configuration, rename the deployment, and delete it.
View Credits Usage
Use the Credits Usage page to check your deployment's balance, review current and historical Credits cycles, and analyze consumption by date, source, agent, or model. Users with read-only access can also view this page.
Credits measure LLM consumption based on the actual cost of model calls. A failed execution can still consume Credits if it makes billable model calls.
The availability of each section on the Credits Usage page depends on the deployment status. The following table lists the states in which each section can be viewed.
| Section | Available Deployment States |
|---|---|
| Overview | The deployment is Running, Scaling, or Upgrading. |
| Analytics | The deployment is Running. |
If Analytics displays a message requesting an upgrade, contact EMQX Cloud support to arrange a deployment upgrade.
Check the Credits Balance
- In the Cloud Console, open your EMQX Agents deployment.
- Click Usage in the left navigation menu.
- In Overview, open the Cycle list and select the current cycle or an earlier cycle. The most recent available cycle is selected by default.
- Review the following values for the selected cycle:
The screenshots in this section use example data.

| Field | Description |
|---|---|
| Remaining Credits | Total remaining Credits, including both included and purchased Credits. For a historical cycle, this is the balance at the end of that cycle. |
| Included Credits Usage | Included Credits used and granted for the selected cycle. The progress bar and % left show the proportion of included Credits remaining. This value does not include consumption covered by purchased Credits. |
| Purchased Credits | Purchased Credits remaining. This amount is already included in Remaining Credits. For a historical cycle, it reflects the remaining purchased Credits at that cycle's end. |
| Cycle | Start and end dates of the selected Credits cycle, displayed in your local time zone. |
Credits cycles do not necessarily follow calendar months. For example, a cycle can run from September 15 to October 15. The start is included and the end is excluded. Use the ranges displayed in Cycle for your deployment.
For subscription pricing, Included Credits, and reset rules, see Plan and Billing.
Selecting a historical cycle displays the balance recorded for that cycle and does not change the Credits currently available to the deployment. Viewing usage does not consume Credits, and you cannot purchase Credits from this page.
Analyze Credits Consumption
Use Analytics to identify when Credits were consumed and which sources, agents, or models accounted for the consumption.
- Open Date range (UTC).
- Select a preset or a custom start and end date through today. Both selected dates are included.
- Review Usage Trend to compare consumption from Agent Runs and Chats.
- In Usage Ranking, select Agent or Model from Group by to locate the main consumers. In the Agent ranking, click an agent name to open its details and review its runs.
- Use Usage Details to review daily consumption and its model breakdown.
The following example shows daily usage over a 30-day range.

Analytics initially shows the current UTC calendar month through today. Its date range is independent of the cycle selected in Overview. Changing one selection does not change the other.
Usage Trend
The bar chart shows total Credits and consumption by source. The legend shows each source's total and share for the selected range. Click a legend entry to show or hide its bars.
| Series | Meaning |
|---|---|
| Total Credits | All recorded consumption in the selected range, including every source. |
| Agent Runs | Model calls made during deployed agent executions. |
| Chats | Model calls made in chats. Calls for automated tool-call risk reviews also consume Credits and are counted here. |
| Unassigned | Consumption whose source cannot be identified. This consumption remains included in the total. |
Ranges of 60 days or fewer use daily bars. Longer ranges use monthly bars. A monthly bar includes only the selected dates within that month. Dates without recorded consumption contribute zero.
The 63-day range in the following example uses monthly bars.

Usage Ranking
The ranking is ordered from highest to lowest Credits usage for the selected range. Scroll through the table to review additional rows.
With Agent selected, the table provides the following information:
| Column | Meaning |
|---|---|
| Agent | The agent name, or its identifier when the name is unavailable. Click the name or identifier to open the agent details. |
| Runs | Executions that started in the selected UTC date range, including failed and zero-consumption executions. Queued executions that have not started and dropped executions are excluded. |
| Credits | The agent's consumption from deployed runs. Chat consumption is counted separately, even when the chat was used to create or edit this agent. |
| Avg/Run | The agent's Credits divided by its Runs count for the selected range. A dash (—) means no average is available because the Runs count is zero. |
| Usage Share | The agent's proportion of the deployment's total Credits in the selected range, including Chats and Unassigned in the denominator. |
Agent shares can add up to less than 100% because Chats and Unassigned consumption do not create Agent ranking rows. Runs are counted by execution start time, while Credits are counted by model-call start time. Therefore, a run that starts before the selected range can consume Credits within the range without increasing the Runs count.
With Model selected, each row shows the model, its total Credits, source amounts, and Usage Share. Model totals include Agent Runs, Chats, and Unassigned consumption. A chat can call both the conversation model and a separate model for tool-call reviews, so one chat's consumption can appear under multiple models.
Usage Details
The table shows daily consumption summaries for the selected range:
| Column | Meaning |
|---|---|
| Date (UTC) | The UTC date on which the model calls started. |
| Source | Agent Runs, Chats, or Unassigned. |
| Agent | The associated agent for an Agent Runs row. Chats and Unassigned show —. |
| Credits by Model | The models used within this row and the Credits consumed by each model. |
| Credits | The total consumption for the row, including all listed models. |
Each row is a daily consumption summary, not an individual Run or model call. Agent Runs rows identify the associated agent, while all Chats consumption for the same day is combined into one row and Unassigned consumption into another. Rows are ordered by date, newest first, and then by Credits within the same day. Use the pagination controls to view additional rows.

Refresh and Interpret Usage Data
The page does not refresh automatically. Reopen or refresh it to retrieve the latest values.
A dash (—) in an Overview card means the value could not be loaded; it does not mean the balance or usage is zero. In Analytics, — under Agent identifies a Chats or Unassigned row, and — under Avg/Run means the Runs count is zero. If no detail rows appear after the page loads successfully, verify that the selected date range contains recorded consumption.
Displayed values are rounded independently, so the sum of displayed components can differ slightly from the displayed total.
Deployment Settings
The Deployment Settings page shows configuration details for an EMQX Agents deployment and provides an option to rename it. To open it, click Deployment Settings in the left navigation menu.
Deployment Info
| Field | Description |
|---|---|
| Deployment Name | The display name for this deployment. Click the edit icon to rename. |
| Deployment ID | The unique identifier for this deployment. Use this when contacting support. |
| Plan | The current plan, for example EMQX Agents - Starter. |
| Network ID | The network that contains the deployment. The network is read-only and cannot be changed after deployment creation. |
Cloud Info
| Field | Description |
|---|---|
| Cloud Platform | The cloud provider hosting this deployment (read-only). |
| Region | The region where this deployment is running (read-only). |
Billing Method
The Billing Method section displays the billing method, subscription status, and applicable billing or expiration date. Depending on your permissions and subscription status, you can also cancel or resume the subscription. For details, see EMQX Agents Subscriptions and Invoices.
Rename a Deployment
- Go to Deployment Settings.
- Click the edit icon next to Deployment Name.
- Enter the new name and click the confirm icon.
Delete a Deployment
Permanent Deletion
Deleting a deployment is permanent and cannot be undone. Deletion stops running agents and removes all agents, chats, connectors, and run history associated with the deployment.
You need the root account, the Administrator role, or the Project Administrator role for the deployment's project to delete the deployment. For complete role permissions, see Role Permissions Matrix. The Console displays the deletion action for a deployment in the Running or Stopped state.
Deleting a deployment immediately cancels its associated subscription instead of waiting for the current period to end. To stop renewal and keep using the deployment until then, follow Cancel a Subscription.
The deployment and its data are also automatically deleted after the subscription ends.
- Go to Deployment Settings.
- In Danger Zone, click Delete Deployment.
- Enter the deployment name as requested in the confirmation dialog, then confirm deletion.
- Verify that the Console returns to the project's Agents deployment list and the deployment is removed after deletion completes.
If deletion fails, the subscription may already have been canceled. Check the deployment and subscription status before retrying, or submit a support ticket for assistance.