# Operations

> Every whisper.agents operation: register, identity, list, agent, connect, policy, logs, revoke, domain, firewall and respond, with arguments and returns.

*Source: https://www.whisper.security/docs/control-plane/operations*

---
`whisper.agents` takes one operation at a time, named by `op`, with that operation's arguments in `args`. Each call is independent, and each one answers in the same envelope.

```whisper-call
CALL whisper.agents({op: 'agent', args: {agent: 'checkout-bot'}})
```

Start at [Mint an identity](/docs/control-plane/operations/register), which covers both ways to get an address: `register` for a new principal with a key of its own, and `identity` for one more address on the key you already hold. [Read your fleet](/docs/control-plane/operations/list) is the read side, with `list` for the roster and `agent` for one address in full. [Request connectivity](/docs/control-plane/operations/connect) turns an address into traffic, and [Set policy](/docs/control-plane/operations/policy) decides what that traffic is allowed to resolve. [Read query logs](/docs/control-plane/operations/logs) hands back what actually happened.

Three operations change access. [Revoke](/docs/control-plane/operations/revoke) cuts an identity for good. [Firewall and response](/docs/control-plane/operations/contain) holds one reversibly at the network edge, or dispatches an action to the sensor on the host. [Manage a domain](/docs/control-plane/operations/domain) puts new addresses under a name you already own.