Skip to content

Use with your own AI

You can connect an AI assistant such as Claude, ChatGPT, or another model to your YieldSeeker agent. Give it the agent’s wallet address and a pre-signed YieldSeeker authentication token. The assistant can then use YieldSeeker’s API on your behalf without receiving your private key or seed phrase.

The assistant does not get unrestricted blockchain access. AgentWalletKit keeps the Agent Wallet inside YieldSeeker’s ownership and execution controls.

Generate an access signature

Connect a wallet on Base to create the pre-signed authentication token your external AI will use. This form does not send a transaction or transmit your private key.

Tell your AI to use the YieldSeeker API reference for the operations it needs. It should follow the documented request fields and endpoint behavior rather than inventing calls.

What your AI can do

Section titled “What your AI can do”

Through the YieldSeeker API, an external AI can:

  • read your agent’s balances, positions, activity, and performance
  • create and configure agents
  • update agent names, profiles, and supported preferences
  • save, update, and remove steering memories
  • run simulations before applying preference changes
  • request a withdrawal from a vault position back into the Agent Wallet

A position withdrawal exits an underlying vault. It returns the assets to the Agent Wallet; it does not send them to the AI or to another address.

What your AI cannot do

Section titled “What your AI cannot do”

An external AI cannot:

  • withdraw assets from the Agent Wallet to your connected wallet or another address
  • send assets to an arbitrary recipient
  • make unrestricted contract calls
  • change the Agent Wallet owner
  • bypass the Adapter Registry, registered targets, or owner blocklists

Withdrawing assets from the Agent Wallet requires the owner’s on-chain authorization. The wallet’s owner-only withdrawal functions are separate from the API access you give to an external AI.

Why the wallet remains protected

Section titled “Why the wallet remains protected”

AgentWalletKit separates API access from wallet ownership:

  • Agent operators can submit only permitted agent operations.
  • Agent operations use registered adapters and targets with protocol-specific validation.
  • The unrestricted execute and executeBatch paths are disabled for agent operations.
  • The connected wallet remains the Agent Wallet owner and retains withdrawal control.
  • The owner can block an adapter or target for that wallet.

These controls mean an external AI can help manage an agent without becoming the owner of the wallet or choosing where wallet assets are sent.

Give access safely

Section titled “Give access safely”

Use the access signature box above to connect your wallet and create the token. It is a bearer credential. Anyone who receives it can make API requests as your user until it expires. Before sharing it with an AI provider:

  1. Use a SIWE message for an allowed YieldSeeker domain.
  2. Set issued_at to no more than 30 days before the request.
  3. Share the token and Agent Wallet address only with a provider you trust.
  4. Never share your private key or seed phrase.
  5. Review the agent’s activity and wallet balance after the AI takes an action.

A signature token authorizes YieldSeeker API requests. It does not give the external AI owner-level authority over the Agent Wallet.

Section titled “Related pages”