Agent sizes and billing
Every Fleet Agent runs on its own dedicated box. The box size determines how much compute the agent has for concurrent work, and it sets the agent’s monthly price.
The size ladder
Four sizes are available for new boxes on accounts created from 16 October 2026. The same ladder applies to hosted agents and Outposts.
| Size | Instance type | Monthly price | Built for |
|---|---|---|---|
| Small | t3.small | $100 | Q&A and simple tasks |
| Medium | t3.medium | $200 | Multi-user work, projects, light development |
| Large | t3.large | $400 | Complex development, many users |
| XLarge | t3.xlarge | $800 | Heavy development and project orchestration |
The HQ Console creation wizard and hq agents provision show the size names
and the monthly price for your company before you create an agent. Contract
pricing, credits or sponsorship can make the displayed price different from
the price for the size.
You can move an agent up or down the ladder at any time from its settings; a mid-cycle change is prorated on your next invoice using standard Stripe proration.
Agent Settings shows the current size as a compact summary with its lanes, workers, and net monthly price. Choose the row to compare the rungs in place. The square glyph grows with each rung, while the text remains the source of truth for the size and capacity. Clicking elsewhere closes the picker without selecting or requesting a change.
Prices for existing customers
Accounts created before 16 October 2026 keep the earlier ladder and its prices, for the boxes they run today and for new boxes, until HQ tells them otherwise:
| Size | Instance type | Monthly price |
|---|---|---|
| Basic | t3.medium | $100 |
| Power | t3.large | $250 |
| Dev | t3.xlarge | $500 |
On that ladder, hq agents provision --size basic|power|dev picks the size.
Outposts on those accounts keep their current add-on price.
Earlier ladders also included a smaller entry box and a larger top box. Agents already running on those sizes are grandfathered: they keep billing exactly what they bill today and keep running unchanged. Those sizes are no longer available for new agents, and an explicit resize moves the agent onto the current ladder.
Who can change an agent’s size
Changing a size changes your bill, so applying a size change requires the
changeAgentSize capability:
- Company owners always have it.
- Company admins have it when the owner grants it.
- Everyone else sees a request path instead: the request goes to the owner, who can approve or decline it.
The confirmation step always shows the exact monthly change before anything is applied.
After the new size is in place and the agent is healthy, HQ updates the size shown in the Console and sends the requester a completion notification. A failed change reports the size the agent remains on instead of claiming the requested size is ready.
Billing
Boxes are billed per box on every account, separately from usage. The $10 of usage included each month does not cover them. No plan upgrade is needed to create an agent.
Every hosted agent is billed at its size from the first agent. A hosted agent needs billing set up for the company (a card or payer on file) before it is created.
Self-run bots that you enroll as team members carry no fee. See Billing and usage for the usage card.
Companies that subscribed earlier
Companies that subscribed to Workforce before per-box billing took effect keep three included boxes in the flat plan fee:
- 1 Dev-size box (your first agent)
- 2 Basic-size boxes
Upgrades beyond what is included are available for the price difference, and agents beyond the included three bill at the ladder price. Deleting an agent never raises the bill on the agents that remain — the plan’s inclusions belong to the plan, not to a particular agent.
Pricing API
A machine-readable statement of the usage card, box sizes, legacy plans and billing rules is described in Pricing API.
See also
- Configure an agent — identity, model, and runtime settings.
- Operate and troubleshoot — health, lifecycle, and diagnostics.