Introduction
Torque is a digital wallet platform that unifies balances, execution, and settlement. Individuals and businesses hold assets and move value through Torque; integrators embed those capabilities via the Platform API and SDKs.
These docs cover authentication, the platform lifecycle, surface APIs, and SDKs. Run Quickstart for a working end-to-end flow, or pick an integration path below if you already know what you're building.
How It Works
Intent becomes committed execution through one lifecycle: READ → DECIDE → EXECUTE. The core primitive is Financial Action = Intent + wallet_order: a user goal (Intent) paired with the executable unit the platform commits (wallet_order).
Context loaded
Read-only; no wallet_order
Intent → draft
functionResults
wallet_order committed
on_chain: merchant channels
Context loaded
Read-only; no wallet_order
Intent → draft
functionResults
wallet_order committed
on_chain: merchant channels
How balances aggregate and orders execute: How It Works. Full schema, intent types, and execution boundary: Lifecycle.
Choose Your Path
Surface market data, feeds, and desk context
Fintech & AppsEmbed Assistant planning and onchain Actions
Embedded WalletsPrivate-label deposits and balance; Connect consent for cash-out in v1
MerchantsAccept payments at checkout
FAQ
What is Torque?
Torque is a digital wallet platform for individuals and businesses. Users hold assets and move value in one place; integrators embed those capabilities through the Platform API and SDKs.
Do users pick a blockchain network?
No. Users work with product buckets (USD, BTC, NVDA, and similar). Torque routes across inventory and settlement automatically. See Chains for supported networks; that page is infrastructure, not a user-facing picker.
What is a unified balance?
Users see one spendable portfolio balance. Holdings across chains roll up behind the scenes (for example ETH and WETH count toward ETH). Routing picks the onchain leg at execution.
What are READ, DECIDE, and EXECUTE?
READ loads portfolio and market context. DECIDE drafts a wallet_order from user intent (Assistant, checkout session, and similar). EXECUTE commits and settles the order onchain or through the merchant channel.
When do I use a business API key vs a user token?
Use your business API key (sk_live_…) on your server for reads, provisioning, and Assistant chat. Use a smart wallet JWT or Connect token only when that specific user is approving a trade or cash-out.
Where do I get API keys?
Create keys in the developer portal at developers.torque.fi. Keep secret keys on your server only.
Can I embed wallets in my app?
Yes. White-label the product layer: provision with POST /accounts/end-users, show deposit addresses and balance in your UI, and start cash-out from your app. Torque holds custody; execution requires user consent (Connect in v1). See Integrator Wallets.
What assets and protocols does Torque support?
See Assets for product rows users trade and hold, Protocols for DeFi venues Torque routes through, and Chains for network coverage.
API: https://app.torque.fi/api/v1
Questions or corrections? hello@torque.fi