Skip to content

Build tokenized credit products with Torq

Developer documentation is public. API credentials, sandbox admission, production access, package distribution, and approved-role scopes remain controlled controlled developer access access. Torq public GA is not open.

Financial infrastructure for tokenized credit

Torq gives an integration one contract for governed credit discovery, account state, non-custodial workflows, signed events, and canonical completion. The API owns product-visible shared state; the customer's wallet or custody service owns transaction signing and submission.

Chain -> Indexer -> Projector -> Postgres -> API -> Your product

Integrations do not reconstruct markets, vaults, positions, permissions, or accounting state from RPC. RPC is used for signing-time simulation, transaction submission, and receipt observation. Torq API state remains authoritative for product-visible completion.

Choose what to build

Build from deposit through impairment and recovery
Add Torq Earn to a self-custody wallet
Add regulated Earn to a neobank
Add custodial Earn to an exchange
Launch and operate managed Earn vaults
Build a white-label Earn platform
Compare and route Earn opportunities
List Torq vaults inside an existing lending protocol
Add tokenized-credit yield to a wallet or app
Build deposit, position, and redemption UX

Start building

  1. Read Developer resources and choose a product guide.
  2. Create an approved Developer project and test application.
  3. Complete the few-line Earn quickstart with a Sepolia wallet.
  4. Prepare a typed workflow, submit through your signer, and wait for canonical success.

Documentation and tools

Choose an end-to-end integration path
Install an SDK or choose a signer boundary
Read markets, vaults, positions, or eligibility
Prepare and track an action
Handle failures, idempotency, quotas, and retries
Test safely on Sepolia
Receive updates
Inspect every REST and GraphQL operation
Adapt a checked-in integration
Manage applications, keys, origins, and environments

Libraries and SDKs

  • Browser wallet or embedded wallet: use @torq-finance/sdk and @torq-finance/react.
  • Node backend or customer HSM/MPC service: use @torq-finance/sdk with a signer callback.
  • Python neobank backend: use the controlled distribution torq-sdk source package supplied to your approved integration.
  • JVM, Kotlin, or Swift integration: use the respective controlled distribution source client for authenticated API reads and workflow preparation. Do not pass raw intent JSON to its signer helper; those helpers are intentionally disabled until each client has a full canonical workflow executor.
  • Contract tooling: use @torq-finance/contracts.

Package names identify checked-in controlled distribution clients. They do not prove public registry publication. Use the package source and version supplied with the approved application.

Operate and upgrade

Every unavailable capability fails closed with capability_not_ready; it never falls back to caller-supplied contract calls.