Wallet Overview

The managed wallet behind your account.

Every account gets a Superior-managed trading wallet on first use - the default credential source for deployments and one-time executions. It lives in Privy's secured wallet infrastructure under Superior's platform controls (the same custody that runs the Terminal); you never handle a key. Prefer full self-custody? Use BYOK instead - the wallet is a default, not a requirement.

GET/wallet

The wallet, its balance, and how to fund it:

{
  "address": "0x3a8d91d1...",
  "deposit": {
    "chain": "arbitrum",
    "asset": "USDC",
    "address": "0x3a8d91d1...",
    "min_usd": 5
  },
  "balance": {
    "held_usd": 180.4,
    "allocated": [
      { "venue": "hyperliquid", "deployment": "dep_01j8xv...", "balance_usd": 141.2 }
    ],
    "total_usd": 321.6
  }
}

• held_usd — un-deployed money sitting safely in the wallet (deposit to grow it).
• allocated — what's working on venues right now, per deployment. Both count toward total_usd: a fresh deposit is never displayed as $0.

Lifecycle

1. Deposit USDC on Arbitrum → shows in held_usd on arrival.
2. Deploy with { "credentials": { "type": "managed" } } (the default): on a live start the runtime allocates from held_usd to the venue and handles venue onboarding (agent wallet, approvals) automatically. Deploys land on the free wallet where the money already is.
3. Stop / delete: infrastructure never market-closes positions; deleting a deployment leaves its funds on the venue account, still yours and still counted in allocated.
4. Withdraw back to your verified login wallet whenever held_usd covers it.

How it relates to credentials

{ "credentials": { "type": "managed" } } on a deployment (the default — omission means the same) trades from venue accounts funded out of this wallet. The wallet is account-level: one wallet, many deployments, allocations tracked per deployment. The credentials page covers the choice between managed and BYOK.