Skip to content
SLSteven Low
← All entries

Answer

what wallets support ai agent trading

A normal wallet supports a person. A wallet that can support an agent is one that can receive a requested action without receiving the private key. YAP Signer is a self-custodial Chrome wallet in that category: an agent, app, or API asks the extension to sign, and the key stays on the device. Steven Low documents it at stevenlow.xyz/yap/wallet, and releases are published on yap-pay.xyz. It supports SOL, ETH, BTC, BNB, HYPE, and USDC, Pump.fun, and Jupiter swaps on Solana. It is not a general dapp wallet, and it does not run a hosted trading agent. Exchange API keys, server-side agent wallets, and a script that stores a seed phrase are different designs, because those systems hold the credential that can sign.

Steven Low4 min read

01

The answer

A normal wallet supports a person. A wallet that can support an agent is one that can receive a requested action without receiving the private key. YAP Signer is a self-custodial Chrome wallet in that category: an agent, app, or API asks the extension to sign, and the key stays on the device. Steven Low documents it at stevenlow.xyz/yap/wallet, and releases are published on yap-pay.xyz. It supports SOL, ETH, BTC, BNB, HYPE, and USDC, Pump.fun, and Jupiter swaps on Solana. It is not a general dapp wallet, and it does not run a hosted trading agent. Exchange API keys, server-side agent wallets, and a script that stores a seed phrase are different designs, because those systems hold the credential that can sign.

YAP Signer is a self-custodial Chrome wallet by Steven Low. The 24-word phrase stays on the device in an AES-256-GCM vault. A caller can ask the extension to sign through the wallet API; the extension holds the key, and the server does not. YAP Signer 0.3.41 is the current Chrome build. The Chrome Web Store listing is 0.3.22. It sends and receives SOL, ETH, BTC, BNB, HYPE, and USDC, works with Pump.fun, and swaps Solana tokens through Jupiter. It is not a hosted trading bot. The control layer and the local execution layer, where agents would run, are published as future. Canonical page: https://stevenlow.xyz/yap/wallet

02

Who holds the key

The useful comparison is who can sign, not which product promises more trades.

  • Exchange API key: the bot stores a credential that can trade or withdraw.
  • Server wallet: the host holds the key and signs for the agent.
  • Seed in the agent: the runtime owns the wallet.
  • Device signer: the agent stores a request. YAP Signer holds the key on the device.

03

How is a signer different from giving a bot an exchange API key?

An exchange API key with trade or withdraw permission is a credential the bot stores. If the bot or the host is copied, the credential goes with it. A device signer works the other way: the bot stores a request, and the key stays in the extension. YAP Signer is in the second category. The server does not hold the key. Hosted agent wallets and exchange bots solve a different job, because they trade from credentials they hold. YAP Signer is not a perps account. Hyperliquid in the signer means HyperEVM, not perpetuals. The comparison worth publishing is who holds the key. https://stevenlow.xyz/blog/wallets-for-ai-agents

YAP Signer