TorqueTorque

Search docs

Search Torque documentation pages & sections

How It Works

The Platform API is the integrator surface. Behind it, one unified balance and one execution engine handle Trade, Transfer, Lend, Borrow, and Checkout through a single order.

One Balance

Users see one spendable portfolio balance. Torque aggregates holdings across chains behind the scenes; depositable assets (including yield-bearing forms) count toward parent buckets such as ETH or BTC. Routing is automatic; integrators and end users never pick a source chain.

What the user sees
One portfolio balanceOne spendable amount per action
Ownership layer
Live portfolio totalUnified balance for MAX and spend
Execution readiness
Can this action route nowMulti-step plan when needed
Inventory layer (hidden)
Per-chain holdingsWhere tokens sit today
Torque ledger
Balance buckets (available / reserved)Order lifecycle

Indexers and observers feed ownership. Users never pick a chain.

Order Execution

Direct when one pocket funds; portfolio plan when split.

Money surfaces
TradeLend & BorrowTransfer & CheckoutAssistant
Quote and execution engine
Preview quote and receive amountSubmit frozen order
Direct path
Single routed transaction
Portfolio plan
ConsolidateSwap / bridgeDeFi delegate
One user-facing order
Single order ID and timelineSettlement legs behind the scenes
Balance lifecycle
Lock spendable balanceSend onchain txConfirm and debitRelease on failure
Onchain execution
Smart walletRouting and DeFi partners
PathWhenWhat Happens
DirectOne pocket holds enough to fund the actionSingle routed transaction
OrchestratedBalance is unified but split across chains or formsConsolidate, then swap, bridge, or DeFi delegate legs

Maps to the API Lifecycle

The engine above powers the READ → DECIDE → EXECUTE contract documented for integrators. See Introduction for the lifecycle diagram and Lifecycle for wallet_order schema and intent types.

StageEngineIntegrator Surface
READUnified portfolio and market contextGET /read/portfolio, portfolioData in Assistant context, Intelligence feeds
DECIDEIntent resolution and draft wallet_orderAssistant functionResults, Checkout SDK session (merchant pay)
EXECUTEOrder commit, routing, settlementPOST /execute/** (on_chain) or torque-checkout SDK + webhooks (merchant)

For Integrators

  • Unified portfolio READ, not per-chain pockets.
  • Third-party: business key for read/decide; user auth for execute.
  • EXECUTE commits wallet_order; routing stays inside Torque.
  • Trade, Transfer, Lend, Borrow, Checkout share one order lifecycle.
  • Merchant pay: Checkout SDK, not Assistant.

Next: Authentication, Actions, Checkout SDK, Assistant.

Was this helpful?