TRUST CENTER
Execution Model
Preview → checks → approval → execution
AI-assisted workflows prepare actions; they do not create unrestricted execution authority.
What the AI can do
Read market, protocol, portfolio, liquidity, and venue context; draft strategies and conditions; create previews; and prepare payloads only for supported, certified, and enabled workflows.
What the AI cannot do
It cannot bypass user approval, signer readiness, policy or feature gates, venue checks, or protocol certification; promise outcomes; or provide individualized investment, tax, financial, or legal advice.
Manual approval
The user reviews the exact preview and approves the bound request. If assets, amounts, routes, destination, risk context, or payload hash changes, approval must happen again.
Policy gates
Controls may limit markets, protocols, assets, contracts, size, exposure, daily volume, slippage, gas, liquidation risk, signer state, subscription state, idempotency, and venue health.
Permissions and revocation
Permissions differ by venue. API keys, agent wallets, broker credentials, token allowances, and protocol approvals may require separate stop, cancel, close, rotate, or revoke steps.
Remaining risk
Approved actions may still fail or settle differently because of network, signer, venue, indexer, protocol, oracle, wallet, bridge, liquidity, slippage, funding, liquidation, gas, balance, and volatile-market conditions.
What the AI can do
Read market, protocol, portfolio, liquidity, and venue context; draft strategies and conditions; create previews; and prepare payloads only for supported, certified, and enabled workflows.
What the AI cannot do
It cannot bypass user approval, signer readiness, policy or feature gates, venue checks, or protocol certification; promise outcomes; or provide individualized investment, tax, financial, or legal advice.
Manual approval
The user reviews the exact preview and approves the bound request. If assets, amounts, routes, destination, risk context, or payload hash changes, approval must happen again.
Policy gates
Controls may limit markets, protocols, assets, contracts, size, exposure, daily volume, slippage, gas, liquidation risk, signer state, subscription state, idempotency, and venue health.
Permissions and revocation
Permissions differ by venue. API keys, agent wallets, broker credentials, token allowances, and protocol approvals may require separate stop, cancel, close, rotate, or revoke steps.
Remaining risk
Approved actions may still fail or settle differently because of network, signer, venue, indexer, protocol, oracle, wallet, bridge, liquidity, slippage, funding, liquidation, gas, balance, and volatile-market conditions.