> 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/build.md).

# Build

This section is for teams that write code against the protocol: wallets, custodians, venues, applications, Claim Issuers, and the authors of compliance modules, gateway adapters and T-REX Lite implementations. The Concepts section explains how the protocol works, and the Guides document each operation. These pages say what to build around them.

| Page                                                                                      | For                  | What it covers                                                                                                            |
| ----------------------------------------------------------------------------------------- | -------------------- | ------------------------------------------------------------------------------------------------------------------------- |
| [Quickstart](/build/quickstart.md)                                                        | Every developer      | Get the code, build it, run the tests, and write a first test against a complete local suite.                             |
| [Integrate a wallet or a custodian](/build/integrate-a-wallet-or-a-custodian.md)          | Wallets, custodians  | Show balances that are true, check a transfer before sending it, hold for clients, and follow what happens to a position. |
| [Integrate a venue or an application](/build/integrate-a-venue-or-an-application.md)      | Venues, applications | Read the register, execute for holders with `transferFrom`, and meet the asset's spender policy.                          |
| [Integrate as a Claim Issuer](/build/integrate-as-a-claim-issuer.md)                      | Claim Issuers        | Sign, deliver, renew and revoke claims at scale.                                                                          |
| [Write a compliance module](/build/write-a-compliance-module.md)                          | Module authors       | The module interface, the three module types, and the rules a module must respect.                                        |
| [Build an ERC-7786 gateway adapter](/build/build-an-erc-7786-gateway-adapter.md)          | Messaging providers  | What an adapter must guarantee to carry the protocol's messages.                                                          |
| [Implement T-REX Lite on a new chain](/build/implement-t-rex-lite-on-a-new-chain.md)      | Chain integrators    | The wire format, the message types and the obligations of a satellite token.                                              |
| [Indexing: events and supply accounting](/build/indexing-events-and-supply-accounting.md) | Indexers, data teams | The events of each contract and how to rebuild balances, positions and supply.                                            |
| [Pre-flight checks with UtilityChecker](/build/pre-flight-checks-with-utilitychecker.md)  | Front-end developers | Explain to a holder why a transfer would fail, before it is sent.                                                         |

Applications already built on the protocol are listed in the [T-REX AppStore](/appstore.md).


---

# 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/build.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.