Docs/developers

T-REX Engine

The enterprise-grade API suite for ERC-3643 and the T-REX ecosystem.

The enterprise-grade API suite for ERC-3643 and the T-REX ecosystem.


Overview

The T-REX Engine is a complete, secure, and scalable API layer for interacting with ERC-3643 tokens, OnchainID, AssetID, and the broader T-REX ecosystem. It abstracts the protocol's smart-contract interactions behind a stable REST API, making it the recommended integration path for institutions building production workflows on top of ERC-3643.

The Engine is a commercial service operated by Tokeny, the technology partner anchoring the T-REX stack. It is not the only way to interact with the protocol — direct smart contract calls and the official open-source contracts remain fully available — but for most production deployments, using the Engine saves months of integration work and provides operational guarantees institutions require.

Status: Live in production.


What the Engine provides

A unified API across the ecosystem

A single set of endpoints to issue tokens, manage identities, configure compliance rules, run lifecycle operations, and query on-chain state — across every supported EVM chain, including the T-REX Ledger.

Lifecycle coverage

End-to-end coverage from issuance to redemption:

  • Token deployment with audited templates and embedded compliance.
  • Investor onboarding via OnchainID and claim management.
  • Primary distribution: subscriptions, capital calls, settlement.
  • Secondary lifecycle: transfers, eligibility checks, freezes, force transfers.
  • Corporate actions: distributions, redemptions, conversions.
  • Reporting and reconciliation across chains.

Operational guarantees

  • SOC 2 Type 2 certified — independently audited controls for security, availability, and confidentiality.
  • Production-grade SLAs for institutional users.
  • Maintained and supported by Tokeny's engineering and operations teams.

Compatibility with the T-REX Ledger

The Engine natively supports the T-REX Ledger, including testnet (Ingen) and — at launch — mainnet. The same API surface works across the Ledger and any other supported EVM chain, so integrations written today carry forward to mainnet without rework.


When to use the Engine

The Engine is the right choice when you need:

  • A stable, versioned API rather than direct contract calls.
  • Production support, incident response, and SLAs.
  • Multi-chain ERC-3643 coverage from a single integration.
  • Faster time-to-market: weeks instead of months of low-level Solidity work.

Direct contract interaction remains the right choice when you need protocol-level control, are contributing to open-source tooling, or are running purely experimental workflows. Both paths are fully supported by the T-REX ecosystem.


API documentation

Full API reference, authentication, endpoint specifications, code samples, and SDK information are maintained by Tokeny at:

docs.tokeny.com


Getting access

The T-REX Engine is available to institutional customers and qualifying ecosystem builders. For access, pricing, and onboarding:

Contact: contact@t-rex.network — we'll route you to the Tokeny team.

For builders applying to list on the T-REX AppStore, Engine access is part of the standard integration support package. See T-REX AppStore.