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

# Resources

Practical material around the protocol: where the contracts are deployed, the reference documents, the vocabulary, common questions, the history of the code, and how to reach the team.

| Page                                     | What it contains                                                                  |
| ---------------------------------------- | --------------------------------------------------------------------------------- |
| [Deployments](/resources/deployments.md) | The addresses of the protocol contracts on each network, and how to verify them   |
| [Whitepaper](/resources/whitepaper.md)   | The design document of the protocol                                               |
| [Glossary](/resources/glossary.md)       | The terms these docs use, each with one definition                                |
| [FAQ](/resources/faq.md)                 | Short answers to common questions, with the page that gives the full answer       |
| [Changelog](/resources/changelog.md)     | The versions of the two codebases and what each one changed                       |
| [Security](/resources/security.md)       | How to report a vulnerability, the audits, and where the trust model is described |
| [Community](/resources/community.md)     | Where to follow the project, contribute and get in touch                          |


---

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