Skip to main content
Automatic protection freezes an agent and its wallets when its payment activity crosses a threshold. It is off for new agents. While it is off, a crossed threshold creates a dashboard alert and the agent keeps paying. A frozen agent cannot start new payments until a team member restores it. Use it as a backstop alongside payment policies and approval rules. Policies decide whether each payment is allowed. Automatic protection can stop the agent when a pattern of activity needs review.

Protection settings

Read the current settings with GET /api/agents/{id}/freeze-config. A new agent returns "enabled": false:
The large-payment check needs 10 confirmed payments of history, and the velocity check ignores hours with less than $50 of spend. The velocity check counts the agent’s confirmed wallet payments, its card purchases, and its checkout purchases together, and runs after each wallet payment, each connected-card purchase, and each new checkout. A checkout counts while its spend is held and after it is paid. Test card purchases are not counted. Consecutive failures and policy violations protect a new agent from its first payment.

Update settings

Send only the values you want to change. Omitted values keep their current setting. Set "enabled": true to turn protection on.
The API key needs the agents:write scope. The dashboard has no control for these settings. The agent’s Safety tab shows freeze status and history.

Freeze or restore an agent manually

reason is optional and appears in the freeze history.

Review status history

Use GET /api/agents/{id}/freeze-history to reconcile when and why access changed:
Use each event id as a stable reconciliation or support reference. Automatic events include a plain-language reason. Team actions include the optional reason supplied with the freeze or restore request.