> For the complete documentation index, see [llms.txt](https://axiology.gitbook.io/axiology-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://axiology.gitbook.io/axiology-docs/object-and-participant-types.md).

# Object and Participant Types

Axiology DLT TSS participants can have several roles.

1. **TSS Operator** - only Axiology, manages the security and compliance of the network, approves changes made to regulated securities, and lists/delists securities from secondary market.
2. **Broker Issuer** - broker that can issue and manage security assets - equities or bonds.
3. **Broker Agent** - creates and manages investor wallets, makes OTC trades on behalf of them, places orders, etc.
4. **Money Issuer (EMI)** - issues currency (EMTs), makes deposits to wallets, manages withdrawals.

<figure><img src="/files/xhF0UXA9SbkYnB4marBe" alt=""><figcaption></figcaption></figure>

More detailed processes and possibilities for all of the roles are provided together with internal Axiology documentation once testing environment with a participant is established.


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://axiology.gitbook.io/axiology-docs/object-and-participant-types.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.