Everything theworkspace does,the API does.
Every screen runs on the same API your systems can call. Send a request, stream firm quotes and pull the evidence record into your own ledger.
# 5,000,000 USDC on Base for USDT on Tron curl --request POST \ --url "$API/v1/workspaces/$WS/requests" \ --header "X-API-Key: $TETRAFI_API_KEY" \ --header "X-Workspace-Id: $WS" \ --data '{ "sell": { "asset": "USDC", "network": "base", "amount": "5000000" }, "buy": { "asset": "USDT", "network": "tron" }, "mode": "exact_input", "priority": "best_price" }'
One API.
Scoped, evented, embeddable.
The workspace ticket, your own systems over REST and an embedded wallet in your product all send the same request into the same flow.
Scoped API keys
Workspace API keys are minted against service accounts with explicit scopes, and always travel with a workspace id.
Asynchronous enablement
Venue enablement is asynchronous: a 202 with a ticket, then poll to ready or blocked with a machine-readable reason.
An event for everything
Webhooks deliver orders, compliance outcomes, team, credit, security and system events over HTTPS.
A one-file wallet SDK
The embedded wallet SDK is one file with no dependencies: connect, sign, link.
The same calls
the workspace makes.


Stop sending first.
See a trade requested, cleared, priced and settled in one flow, on your own corridors.