> For the complete documentation index, see [llms.txt](https://docs.t-rex.network/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.t-rex.network/guides/agents.md).

# Agents

These guides cover the operations that an Issuer's agents perform on a live asset: maintaining registrations of addresses for the asset, and servicing the register with freezes, forced transfers, recoveries and the pause. Each operation is gated by its own role.

| Order | ID | Guide                                                                                                                            | What it does                                               | Role                                             |
| ----- | -- | -------------------------------------------------------------------------------------------------------------------------------- | ---------------------------------------------------------- | ------------------------------------------------ |
| 1     | 06 | [Register an investor for an asset](/guides/agents/06.-register-an-investor-for-an-asset.md)                                     | Attributes an address to an identity, for one asset.       | `AGENT`                                          |
| 2     | 17 | [Update an investor's registration](/guides/agents/17.-update-an-investors-registration.md)                                      | Changes the identity an address is registered with.        | `AGENT`                                          |
| 3     | 18 | [Remove an investor's registration](/guides/agents/18.-remove-an-investors-registration.md)                                      | Deletes a local registration.                              | `AGENT`                                          |
| 4     | 13 | [Freeze and unfreeze an address or a partial balance](/guides/agents/13.-freeze-and-unfreeze-an-address-or-a-partial-balance.md) | Immobilizes an address, or an amount on it.                | `AGENT_ADDRESS_FREEZER`, `AGENT_PARTIAL_FREEZER` |
| 5     | 14 | [Execute a forced transfer](/guides/agents/14.-execute-a-forced-transfer.md)                                                     | Moves tokens without the holder.                           | `AGENT_FORCED_TRANSFER`                          |
| 6     | 15 | [Recover a position from a lost wallet](/guides/agents/15.-recover-a-position-from-a-lost-wallet.md)                             | Restores a position to a new address of the same identity. | `AGENT_RECOVERY_ADDRESS`                         |
| 7     | 16 | [Pause and unpause a token](/guides/agents/16.-pause-and-unpause-a-token.md)                                                     | Halts and resumes the asset.                               | `AGENT_PAUSER`                                   |

The "Order" column groups the registry operations first, then the token operations. The "ID" column is the permanent reference number of each guide. See [How guides are numbered](/guides/about-the-guides.md).

Minting and burning are agent operations too. They are in the Positions guides, with transfers.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.t-rex.network/guides/agents.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.