> ## Documentation Index
> Fetch the complete documentation index at: https://docs.anchorage.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Pause or revoke an agent

> Stop an agent right away, from its page in the web UI.

Stop an agent right away, from its page in the web UI.

| Action | What happens | Can you undo it? |
| - | - | - |
| Pause | Tool calls, API-key requests, and payments are refused. Keys and sessions are kept. | Yes, select **Resume** |
| Revoke a key | That one key stops working on its next request. | No, mint a new key |
| Deactivate | Revokes the agent's identity: credentials are invalidated, every key and session ends, and tool calls fail immediately, with no grace window. Its history stays visible. | No, create a new agent |

The agent's user, an org admin, or Anchorage can pause an agent. Only Anchorage lifts a pause caused by an account freeze or an organization change. For the spend limits that apply to every agent, see [Limits](https://docs.anchorage.com/agentic-banking/reference/limits.md).

## Deactivate an agent

**Deactivate** the agent from the web UI to revoke its identity and stop it instantly yourself, with no grace window: its credentials are permanently invalidated, every session is revoked, and tool calls fail right away. This is permanent — the revoked agent can never complete OAuth consent again, so reconnecting means creating a new agent and consenting for that one.

## Find an agent

The agents list opens on the **Active** tab. Use the **Inactive** tab above the list to see paused and deactivated agents, or the **All** tab to see every agent; each tab shows how many agents it covers. Each agent's status badge reads **Paused** or **Deactivated**, so you can tell them apart on any tab. A deactivated agent's page, and every payment and transaction that names it, stay available.

To find an agent by name, type in the search box beside the tabs and press Enter. The search matches any part of the name, ignoring case, across every page of the list, and the tab counts show how many matching agents each tab covers. Switching tabs, switching between **My agents** and **All agents in org**, and paging all keep the search.

Above the list, **My Agents** shows how many of your agents are active, how many approvals are waiting on you if you're an org admin, and your personal budget. Each agent's row ends in a **⋯** menu with the actions you can take on that agent: **Pause** on an active agent, **Resume** on a paused agent whose pause you can lift, **Deactivate** on an active or paused agent, and **Edit budget** if you're an org admin. **Deactivate** asks you to confirm first.

## What a pause does

**Pause the agent** from its page in the web UI to stop it with one action while keeping its identity and credentials. The agent's user, an org admin, or Anchorage can pause it, and the same people can resume it from the same page. A paused agent shows as **Paused** in the web UI, and its page shows who paused it and when; a pause Anchorage placed shows as paused by Anchorage. While the agent is paused, tool calls, API-key requests, and payments are refused with the error "This agent is paused. Its owner can resume it from the agent page." Its keys and sessions are not revoked, so the agent works again as soon as you resume it, with no new consent and no new key. An agent connected through OAuth can still refresh its connection while paused, but every request is refused until you resume. OAuth sessions keep their normal expiry during a pause, so a session that expires while the agent is paused needs a new consent; API keys do not expire. Pausing an agent that is already paused is refused as a conflict. If the pause was placed before keys were kept on pause, resuming it ends the agent's existing keys and sessions. You can deactivate a paused agent.

## When Anchorage pauses an agent

An account freeze or removing the agent's user from your organization also pauses the agent, and revokes its API keys and sessions. Only Anchorage resumes an agent paused this way, including one you had already paused. The agent's page shows the reason for the pause and offers no resume button, and a client that resumes after the pause is lifted needs a freshly minted key. While the lock is in place the agent's credentials are refused as unauthenticated, not with the "This agent is paused" message. A resume attempt by anyone but Anchorage is refused with "An organization change locked this agent. Contact Anchorage support to resume it."

Removing a member from your organization revokes the API keys of every agent that acts for that member, and pauses those agents. Only Anchorage resumes an agent paused this way.


## Related topics

- [Agents](https://docs.anchorage.com/agentic-banking/concepts/agents.md)
- [Connect a harness with an API key](https://docs.anchorage.com/agentic-banking/guides/connect-your-harness.md)
- [Quickstart](https://docs.anchorage.com/agentic-banking/quickstart.md)
- [Errors and retries](https://docs.anchorage.com/agentic-banking/reference/errors-and-retries.md)
- [Limits](https://docs.anchorage.com/agentic-banking/reference/limits.md)