Skip to main content
All limits in Agent Loadout are pooled across your entire organization. Your five agents share one bucket of inbound messages, one bucket of machine time, and so on. This makes it easy to concentrate resources on the agents that need them most without redistributing allowances manually.

Pooled resources

The following resources are tracked at the org level and shared across all agents:
Each additional Pro agent seat adds 200 outbound recipients, 1,000 inbound messages, 1 GB mailbox storage, and 10 h of machine time to the shared pool.

What happens at a limit

When your organization reaches a resource cap:
  • Outbound sending pauses. Queued messages are not delivered until capacity is restored.
  • Mailbox imports pause. New inbound messages cannot be written to mailboxes until the inbound limit resets or additional capacity is added.
  • Incoming overflow has a limited recovery window. Agent Loadout does not drop incoming mail immediately, but you should not rely on overflow as a long-term storage buffer. Monitor your inbound usage and add capacity before you approach the limit.
Do not rely on the incoming mail overflow window as a substitute for adequate inbound message capacity. Messages held in overflow are not guaranteed to be retained indefinitely.
The REST API returns HTTP 402 when access is paused or a quota has been reached:
Quota error response

Adding capacity

You have two ways to add capacity without upgrading your entire plan:

Add Agent Seats

Each new Pro seat expands the shared pool: +200 outbound, +1,000 inbound, +1 GB storage, +10 h machine time.An owner changes the agent quantity in Billing & usage.

Prepaid balance

On a paid plan, choose Top up in Billing & usage to pay for eligible usage beyond your allowances. Pay upfront in whole US dollars, with a $10 minimum. The balance never expires.
Usage above the included allowances requires a prepaid balance. Without one, or when it is used up, usage pauses at the available limits. Owner-set usage caps can lower those limits. There is no end-of-period usage invoice, and Free Sandbox has no paid usage. Processed mail data is a hard monthly cap; a balance does not extend it.

Machine time billing

Machine time is billed per second and weighted by machine size: a larger machine consumes the allowance faster than a standard one. Key details to keep in mind:
  • The full TTL window is reserved from your allowance when a machine starts, even if you stop it early.
  • Unused time is returned to the pool when you stop a machine before its window expires.
  • Stopping a machine snapshots the disk; resume_machine restarts it from that snapshot.
  • The Compute Scale add-on ($15 / month) unlocks large machines, 24-hour run windows, and 10 additional concurrent machines.

Sender trust limits

Sender trust limits are separate from your plan allowances and budget. They apply independently and govern production sending to unverified recipients. A live paid plan and sender trust are both required before production sending is enabled.
On the Free Sandbox, outbound mail is limited to verified recipients, with at most 25 per month and 5 per day. Sending attachments requires a paid plan.

Monitoring usage

Open Billing & usage in the dashboard to see real-time consumption across your organization:
  • Delivery counts and bounce/complaint rates for each sending domain
  • Remaining inbound and outbound allowances for the current billing period
  • Machine time consumed vs. available
  • Vault entry count and paired device count
  • Prepaid balance available, amounts reserved for work in progress, and usage charged this period
Check allowances, prepaid balance, and usage caps before starting a high-volume automation. Top up before the balance is exhausted; sender trust limits and hard caps still apply.