For the complete documentation index, see llms.txt. This page is also available as Markdown.

Manage agents & funds

The owner-signed actions — approve or revoke an API wallet, withdraw, and de-risk a credit account.

A handful of actions move value or manage who can trade for you. They are owner-signed: your main wallet signs them under auth_scheme: "eip712", never the API wallet — each is a real POST /trade action the API accepts directly, or do it through the Native web app.

These sit outside the API wallet's reach — it can trade, but never move funds. For the full agent-vs-owner split and what each key may sign, see Nonces & API Wallets.

Approve or revoke an API wallet

  • approveAgent — authorize an agent key in a slot (03). This is what creates an API wallet; the web app returns the connection bundle.

  • revokeAgent — retire a slot. The old agent's agent_epoch stops validating.

Both are owner EIP-712 signatures, not batchable, and carry no agent_epoch.

Withdraw funds

  • withdraw — move an asset off Native to a destination chain. Owner EIP-712; enforces per-chain/asset minimums and a withdraw fee. A credit account cannot withdraw.

Deposits are not a /trade action — they are on-chain transfers into a vault contract on the source chain. Deposit & Withdraw walks both directions end to end, including how to confirm each one settled.

De-risk a credit account

Only relevant if the protocol granted you a credit account.

  • settle — move a long position out of the credit account into a spot account's available balance.

  • repay — spend a spot account's balance to cover a credit account's short.

Both are owner EIP-712, single-signature, and carry a required cloid used only for txStatusByCloid lookups.

Signing

These use the EIP-712 v4 scheme (MetaMask-compatible), not the legacy binary payload. The typed-data fields are in Transaction Signing.

Next steps

Last updated