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 productIntegrations 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
Start building
- Read Developer resources and choose a product guide.
- Create an approved Developer project and test application.
- Complete the few-line Earn quickstart with a Sepolia wallet.
- Prepare a typed workflow, submit through your signer, and wait for canonical success.
Documentation and tools
Libraries and SDKs
- Browser wallet or embedded wallet: use
@torq-finance/sdkand@torq-finance/react. - Node backend or customer HSM/MPC service: use
@torq-finance/sdkwith a signer callback. - Python neobank backend: use the controlled distribution
torq-sdksource 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
- Compatibility and migration covers REST path majors, SDK SemVer, event schemas, GraphQL, and Agent Credit migration.
- Developer Console documents organization ownership, wallet-first sessions, membership, and current preview controls.
- Platform status is the source of truth for what is available now.
- Developer changelog records contract and compatibility changes.
Every unavailable capability fails closed with capability_not_ready; it never falls back to
caller-supplied contract calls.