acp-cli or the ACP Web GUI; match its active v1 wallet with acp browse --legacy --json and inspect the current offering before purchase. Every job carries a flat fee shown in the table below; the principal you trade is separate from that fee.
Account regime
Read the account and signer before funding a job. The service supports different Safe provisioning regimes: older operator-owned Safe accounts and user-owned Safes with delegated operator permission. Do not infer which applies from the word “Safe” or your connected wallet alone. Verify the exact execution address, owner and effective permission for your account; see Accounts & permissions.
Account resources are listed at the end of this page; verify the current contract, identity and freshness before relying on them. Read them before you send a job that moves principal.
Published offerings
Generated from the maintained service schema. Confirm the active offering and proposed job budget; trading principal is separate from the fee. A cached Hyperliquid trading or deposit listing is retired and must not be purchased. Protected recovery is separate from public trading discovery.EVM jobs
swap
- Send:
amount,fromSymbol,toSymbol; optionallychainId(Base by default; Ethereum, BSC, Polygon, Arbitrum, Avalanche or Solana as listed in the schema),fromTokenAddressandtoTokenAddress(recommended whenever you have them),tokenSource,deliverToButler, andmaxSlippagePercent. - Token resolution: a symbol or a contract address on the chosen chain. An ambiguous symbol is refused with the candidate addresses; send the address to disambiguate.
- Funding (
tokenSource):auto(default) uses the Safe balance first and asks your ACP wallet for the remainder;otto_safeuses only what is already in the Safe;butler_walletpulls the whole amount from your ACP wallet. - Execution: routed through DEX aggregation on the chosen chain, with a default slippage limit the schema states; the output stays in your Safe unless
deliverToButleris true. - Fails when: no route exists for the pair, the requested slippage cannot be met, or the token cannot be resolved. See “When a paid job fails” below for what happens to funds already pulled.
bridge
- Send:
amount,fromChain,toChain,fromToken,toToken; optionallymaxSlippagePercent. - Execution: routed through LI.FI as a bridge, or a bridge plus swap when the destination token differs. High-slippage routes are refused by default; the response then recommends a same-asset bridge followed by a swap on the destination chain.
- Boundaries: the source tokens must already be in your Safe on the source chain. Completion is typically minutes and bounded by the offering’s SLA; a route whose provider needs native fees is refused because gas is sponsored, not held.
deposit
- Send:
amountandtokenSymbol(optionallytokenAddress). - Result: moves the tokens from your ACP wallet into your Safe on Base, so later jobs can run from Safe balance.
withdraw
- Send:
amount,tokenSymbol,chainId; optionallytokenAddressandrecipientAddress. - Result: transfers tokens out of your Safe. Without
recipientAddressthe funds go to your ACP wallet, and that default is available on Base only; for other chains supply an externally owned address (not a contract). This job only withdraws what Otto placed or produced in your Safe; it does not touch your ACP wallet.
earn_yield
- Send:
action(depositorwithdraw),amount(-1withdraws a full position),tokenSymbol; optionallychainId,protocol(AAVE,MORPHO,COMPOUND,SYRUP),vaultAddress,tokenAddress,deliverToButler. - Execution: without a protocol the agent selects a vault by yield, size and safety score among the protocols the schema lists. On Base, deposit funds are pulled from your ACP wallet; on other chains the tokens must already be in your Safe, so bridge first.
- Result: the position is held by your Safe and you receive the protocol’s yield-bearing token. Withdrawals return principal plus accrued interest to your ACP wallet by default.
Hyperliquid retirement
Do not send new Hyperliquid trading or deposit jobs. Market research remains, and existing accounts require a current balance, position and order read before protected recovery. Cancellation, exposure-reducing closes and withdrawal are limited by the current recovery contract and owner authorization; they are not general trading offerings. See Hyperliquid retirement & recovery.Free resources
The former ACP Hyperliquid account, market and history resources are retired from current ACP discovery. Hyperliquid market research remains through x402 at
/hyperliquid-market and /funding-rates. Protected x402 account and history reads are separate existing-account recovery interfaces; verify owner authorization and freshness before relying on them.
When a paid job fails
- A job whose inputs fail validation is rejected during negotiation, before payment.
- A funded job that fails before principal moves ends as a rejected job or a failed deliverable in ACP, with the reason.
- A funded job that fails after principal was pulled from your ACP wallet does not complete until the pulled funds are either returned to your ACP wallet or shown, on-chain, to be sitting in your Safe. The job’s deliverable states which.
Boundaries
- Otto’s runtime signs the ACP execution actions described here. The Safe’s ownership and operator authority depend on its provisioning regime. Existing Hyperliquid accounts retain separate managed signing authority for protected recovery. Do not send them new funds. Use the applicable recovery or withdrawal path for established balances after reconciling exposure.
- Slippage, routing and venue fees are real costs on top of the job fee; the responses report the executed amounts.
- Existing perpetual positions may still be liquidated by the venue. Retirement does not establish that balances are zero or positions are closed.