> 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/appstore/t-rex-engine.md).

# T-REX Engine

T-REX Engine is an API for the T-REX protocol. It lets a Platform, a financial institution or an existing back office operate identities, assets and distribution without writing contract calls. This page says what it does and how it relates to the protocol. T-REX Engine is a commercial service provided by Tokeny.

## What it does

|                           |                                                                                                                                                                                                                 |
| ------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **Integration**           | One standardized interface to the contracts, for modern front ends and for the systems financial institutions already run. The team that integrates does not need to build and maintain its own contract layer. |
| **Data access**           | Reads on transactions, on the activity of each party, on asset data and on the events of an asset's life cycle, for monitoring, reporting and reconciliation with off-chain systems.                            |
| **Life-cycle operations** | The operations of an asset from issuance to distribution and servicing: the API triggers the corresponding contract calls. It also exposes the [DINO](/appstore/dino.md) contracts.                             |
| **Security**              | The service is audited and holds a SOC 2 Type 2 certification.                                                                                                                                                  |

## How it relates to the protocol

T-REX Engine is an off-chain service in front of the contracts. It is one way to reach the protocol, not a part of it.

* **It is optional.** Every operation it offers is a call, or a sequence of calls, on the public interface of the contracts. The [Guides](/guides/about-the-guides.md) document each of them, and the [Build](/build.md) section covers direct integration.
* **It has no privileged path.** The protocol defines no role for T-REX Engine. A transaction submitted through the API is sent from an account, and passes the same access control and the same checks as a transaction from any other account: the roles of the suite's `TREXAccessManager`, the keys of an ONCHAINID, the eligibility gate and the compliance rules.
* **The contracts remain the record.** What the API returns is read from the chain. The register of an asset is the token and its compliance on the reference chain, whatever service is used to read or write it.

## When to use it

| Situation                                                                                        | Choice                                                                |
| ------------------------------------------------------------------------------------------------ | --------------------------------------------------------------------- |
| A team wants to launch or service an asset fast, from a system that speaks REST and not Solidity | T-REX Engine                                                          |
| A team wants full control of its contract calls, its keys and its indexing                       | Direct integration: start with the [Quickstart](/build/quickstart.md) |

The two can be combined: an asset operated through the API is an ordinary asset of the register, and any other integration reads and acts on it in the same way.

## Access

T-REX Engine is provided by [Tokeny](https://tokeny.com/). Access, pricing and the API reference are available from the provider.


---

# 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/appstore/t-rex-engine.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.