Build tokenized credit products with Torq

APIs, SDKs, guides, samples, and operating tools for wallets, neobanks, fintechs, and credit applications.

Developer documentation is public. API credentials, sandbox admission, production access, package distribution, and approved-role scopes remain controlled Developer Preview 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

Product	Start here
Build from deposit through impairment and recovery	Complete credit lifecycle
Add Torq Earn to a self-custody wallet	Wallet provider playbook
Add regulated Earn to a neobank	Neobank playbook
Add custodial Earn to an exchange	Exchange and custodian playbook
Launch and operate managed Earn vaults	Asset manager playbook
Build a white-label Earn platform	Financial service provider playbook
Compare and route Earn opportunities	Yield aggregator playbook
List Torq vaults inside an existing lending protocol	Crypto lending protocol playbook
Add tokenized-credit yield to a wallet or app	Embed Torq Earn
Build deposit, position, and redemption UX	Build an earn flow
Launch a wallet, neobank, fintech, or partner channel	Platforms
Operate allocation, market attachment, caps, routing, and fees	Vault economics
Reconcile share value, accrued yield, and fees	Yield and fee accounting
Fund governed credit with an admitted stablecoin	Stablecoin-funded credit
Support auctions, RFQs, refunds, and claims	Distressed recovery
Support governed transfers and exits	Share mobility

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

Need	Start with
Choose an end-to-end integration path	Developer resources
Install an SDK or choose a signer boundary	SDK reference
Read markets, vaults, positions, or eligibility	Resource APIs
Prepare and track an action	Typed workflows
Handle failures, idempotency, quotas, and retries	Errors and rate limits
Test safely on Sepolia	Testing and sandbox
Receive updates	Webhooks and WebSockets
Inspect every REST and GraphQL operation	API reference
Adapt a checked-in integration	Code samples
Manage applications, keys, origins, and environments	Developer projects
Check current availability	Platform status
Connect an AI to Torq securely	AI & Agents
Follow a complete audience implementation	Earn use cases
Give an AI system a source-grounded index	Developer machine-readable index
Audit the complete platform contract and its current boundaries	Developer platform coverage

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 Private Preview torq-sdk source package supplied to your approved integration.
JVM, Kotlin, or Swift integration: use the respective Private Preview 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 Private Preview 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.