Developer platform coverage
Evidence-backed coverage for the Torq API, SDKs, events, lifecycle, AI, testing, and operations.
Category contract
Torq is Stripe for tokenized credit is a category position: Torq gives a product team one coherent developer contract for tokenized-credit discovery, customer access, non-custodial workflows, events, testing, and canonical completion. It does not mean equal company scale, transaction volume, ecosystem size, operating history, public availability, or support footprint.
The comparison is credible only when every customer-visible claim below stays bound to a governed API, SDK, event, source example, operational control, and current release status.
Exact reference and runnable endpoint-specific sample coverage
Durable polling, WebSocket, webhook, cursor, and replay contract
TypeScript, React, contracts, Python, JVM/Kotlin, and Swift
1 public-launch proof remains partial
End-to-end integration coverage
| Integration stage | Torq contract | Completion evidence |
|---|---|---|
| Design the product | Use-case playbooks and reference architectures | The custody, signer, tenant, data, and support boundaries are explicit |
| Create access | Organizations, applications, keys, origins, scopes, and wallet sessions | The application and environment are approved and credentials remain in their correct boundary |
| Discover products | Assets, markets, vaults, tranches, funds, wrappers, partner programs, and networks | Canonical responses include freshness evidence |
| Evaluate suitability | Eligibility, allocations, liquidity, fees, share mobility, NAV, and risk state | The wallet and product state are current and no unavailable field is inferred |
| Prepare an action | POST /v1/workflows/prepare | Typed input, preflight, snapshot, expiry, exact intents, and postconditions are visible |
| Sign and submit | Customer-controlled signer, then POST /v1/workflows/{requestId}/transactions | The exact prepared target, value, calldata, chain, and recipient were approved and submitted |
| Confirm completion | GET /v1/workflows/{requestId} | Status reaches final_success, then the affected resource is reread |
| Stay synchronized | Events, webhooks, WebSockets, cursor resume, and periodic reconciliation | Delivery is deduplicated and current canonical state wins |
| Operate safely | Sandbox, rate limits, audit evidence, compatibility, migration, support, and API status | Test failures, incidents, and version changes have explicit handling |
Investor product data coverage
The public developer surface is designed to support a complete investor Earn application, without exposing protocol-operator controls and without reconstructing shared state from RPC.
| Product screen or decision | Exact governed reads |
|---|---|
| Asset identity and pricing | GET /v1/assets, GET /v1/assets/{resourceId}, GET /v1/oracles, GET /v1/nav-reports |
| Market economics and risk | GET /v1/markets, GET /v1/markets/{resourceId}, GET /v1/markets/{resourceId}/activity, GET /v1/credit-facilities |
| Vault overview and details | GET /v1/vaults, GET /v1/vaults/{resourceId}, GET /v1/tranches |
| Allocation and exposure | GET /v1/vaults/{resourceId}/allocations, GET /v1/allocation-intelligence |
| Liquidity and exit terms | GET /v1/vaults/{resourceId}/liquidity, GET /v1/vaults/{resourceId}/share-mobility |
| Wallet access and holdings | GET /v1/eligibility, GET /v1/positions, GET /v1/activity |
| Yield and distribution economics | GET /v1/fees, GET /v1/partner-programs, GET /v1/wrappers |
| Impairment and recovery | GET /v1/liquidation-recovery, GET /v1/funds, GET /v1/funds/{resourceId}, GET /v1/funds/{resourceId}/holdings |
Every operation page lists every response field and nested schema. The API explorer can run an endpoint-specific sample for all 65 governed operations, including writes and server-only operations, without accepting credentials or mutating protocol state.
API, SDK, and event coverage
- REST and GraphQL: all 65 governed operations have an exact page, auth boundary, request, response, errors, production cURL and TypeScript snippets, and endpoint-specific sample response.
- TypeScript high-level client: canonical investor resource lists and deep vault, market, asset, and fund reads; wallet sessions; typed workflows; transaction tracking; events; and customer-owned execution.
- React: canonical resource and workflow hooks plus an EIP-1193 signer adapter.
- Python: authenticated resource and canonical workflow support for backend and institutional signer integrations.
- JVM/Kotlin and Swift: authenticated reads and workflow preparation. Their raw-intent execution helpers remain disabled until full canonical executors are available.
- Contracts: checksummed active-V2 ABI, address, deployment, and chain metadata.
- Events:
GET /v1/eventsversioned polling, WebSocket streams, signed webhooks, cursor resume, retry, replay, and at-least-once deduplication guidance.
The REST reference remains canonical where a language SDK does not expose a named high-level method. Documentation never converts a missing SDK helper into an invented method or arbitrary request escape hatch.
Lifecycle and recovery coverage
The complete credit lifecycle keeps one customer experience intact from product discovery, deposit and tranche selection through yield, liquidity, redemption, impairment, recovery monitoring, optional Distressed Recovery Fund participation, proceeds, and final reconciliation.
An affected vault position and a recovery-fund position are separate capital allocations. Torq
does not automatically enroll, compensate, or create a claim for the customer. A product must show
the evidence, collect explicit customer approval, and use only an exported typed workflow. If the
approved application does not have that workflow, it returns capability_not_ready; the client
must never synthesize a target or calldata.
Operations and support coverage
- Projects and environments for organizations, applications, keys, origins, and access separation.
- Testing and sandbox for Sepolia admission, faucet policy, wrong-network, stale-state, revert, duplicate-delivery, and delayed-indexing cases.
- Webhooks and events for signatures, retries, replay, dead-letter handling, cursor resume, and reconciliation.
- Errors and rate limits for stable codes, idempotency,
Retry-After, request IDs, and blocked states. - Compatibility and migration for REST path majors, SDK SemVer, event schema versions, deprecations, and support windows.
- API status for public Gatus-backed current health. Availability is not release readiness.
- AI and agents for machine-readable context, retrieval, secure action preparation, and safety evaluation.
Current Private Preview boundaries
The developer contract is broad and repository-proven, but release maturity is not the same claim as domain coverage. The current release remains Private Preview:
- Public package registry publication and clean independent installation are not yet proven for the complete SDK family.
- The protected public-CI proof remains
partial_proven; a genuinely passing protected public-GA candidate is still required. - Credentials, sandbox admission, approved-role scopes, and production access remain controlled.
- External investor recovery-fund write workflows remain unavailable unless the exact approved Preview executor is supplied.
Public GA remains disabled until the public package registry publication and protected public-CI proofs are current and complete. See Developer Preview availability for the release boundary and API status for current service health.