Incident response cuts an agent off in one step and alerts your team.

An agent has one status among three: active, quarantined or disabled. Six steps change it, from the agent's page in the dashboard or from the API. Each step opens or closes an incident, writes a line to the journal and alerts your team. It needs the member role, or an admin key.

A quarantine stops the actions and keeps the agent visible.

POST /v1/agents/{agent_id}/quarantine
Content-Type: application/json

{"reason": "Refund loop on order ord_4821"}

The agent still identifies itself, but every decision answers quarantine, whatever its permissions and its rules say. Its requests and its traces still reach the journal, so your team sees what it tries. The SDK throws DeniedError, with a message that says the agent is in quarantine.

POST /v1/agents/{agent_id}/release, with an optional reason, lifts the quarantine and closes the incident.

Disabling turns the agent off.

POST /v1/agents/{agent_id}/disable disables the agent, with an optional reason. Paidwen then refuses each of its requests with 403, without evaluating it and without a line in the journal. The SDK throws RequestError, and the action never runs, even with onUnavailable set to "allow".

POST /v1/agents/{agent_id}/enable turns the agent back on and closes the incident. Disabling an agent in quarantine closes the quarantine and opens the new incident.

Revoking and rotating replace the agent's keys.

• POST /v1/agents/{agent_id}/revoke-keys revokes all of the agent's active keys at once. The agent no longer identifies itself until it gets a new key.
• POST /v1/agents/{agent_id}/rotate-key revokes every active key and creates a new one. The answer carries the new key, only once.

On October 5, 2026, a revoked key reached every decision point within 29 ms with 1 agent, and within 374 ms with 10,000 agents.

Revoking and rotating cannot be undone. Paidwen never changes your keys at your providers: if an agent leaked a provider key, you rotate it at that provider.

A rule can quarantine an agent on its own.

An active rule that returns quarantine puts the whole agent in quarantine, not only the action. The agent's next decision, on any decision point, answers quarantine at once. The incident names the rule and the action that triggered it.

A rule in observe mode that returns quarantine only records what it would have done. Paidwen never decides a quarantine alone: only one of your rules, or a person, starts one.

Your incident contacts hear about each step.

Each opening and each closing goes by email from [email protected] to each contact of your organization, and to its Slack channel when you set one. The message names the agent, the step, its author or its rule, the reason and the time, with a link to the agent's page.

An admin sets the contacts in Settings, then Organization: 1 to 100 email addresses and an optional Slack channel. At first, the list holds the address of the person who created the organization.

A step that does not apply gets 409.

Lifting the quarantine of an agent that is not in quarantine, enabling an active agent, or quarantining a disabled agent gets 409. Quarantining an agent already in quarantine returns its open incident.

Incident response has four limits.

• A quarantine decided by a rule does not stop the decisions already in flight on another decision point.
• A disabled agent writes nothing more to the journal, so its attempts do not appear in your journal.
• A step taken by a person reaches the decision points in under a second, not at the same instant.
• Paidwen never stops an action that already left. It only sees the next question.