Skip to content
YieldSeeker Docs

Use with your own AI

Your own AI assistant, such as OpenClaw, Grok or Hermes, can steer your agent through a signed API token but cannot withdraw funds. OpenClawGrokHermesSigned API tokenYour AI assistantANY MODELYour agentSTEER · NOT WITHDRAW

You can connect an AI assistant such as OpenClaw, Grok, Hermes, or another model to your YieldSeeker agent. Give it the agent’s wallet address and a signed YieldSeeker authentication token. The token authenticates API requests as you; it is a bearer credential, so anyone who receives it can make API requests until it expires. Never give the AI your private key or seed phrase.

The assistant does not get Agent Wallet ownership or unrestricted blockchain access. Its token authenticates specific YieldSeeker API operations, while AgentWalletKit constrains wallet execution.

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 supported Vault Agents, and update their names, emojis, and investment profiles
  • save, update, and remove memories
  • simulate memory instructions before saving them
  • request a vault-position withdrawal back into the Agent Wallet
  • request an Autoseek run

What your AI cannot do

Section titled “What your AI cannot do”

An external AI cannot:

  • send assets to the AI provider or an arbitrary recipient
  • directly withdraw assets from the Agent Wallet to any wallet, including yours; those withdrawals are owner-only onchain actions
  • change wallet ownership or blocklists
  • make unrestricted contract calls or bypass the Adapter Registry and registered targets

Direct Agent Wallet withdrawals require the owner’s authorization. API access lets the AI request supported agent operations, but does not let it sign owner-only wallet actions.

Why the wallet remains protected

Section titled “Why the wallet remains protected”

AgentWalletKit separates API access from wallet ownership:

  • Agent operations that interact with protocols use registered adapters and targets with protocol-specific validation.
  • The YieldSeeker Agent Wallet disables unrestricted execute and executeBatch calls for agent operations.
  • The connected wallet remains the Agent Wallet owner and retains owner-only withdrawal control.
  • The owner can block an adapter or target for that wallet.

These controls keep API access separate from wallet ownership. Treat the token as action-capable, not read-only.

Give access safely

Section titled “Give access safely”

Use the access signature box above to connect your wallet and create the token. 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; the token can authorize API actions, including agent runs and position withdrawals back into the Agent Wallet.
  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”