Key Rules

The required rules every agent must follow when building and executing yield transactions.

These rules apply to every transaction flow built with the Yield.xyz Agent Openclaw Skill.

Transaction Rules

  • Always call yields_get first. The schema defines exactly what inputs are required for that yield and chain.
  • Amounts are human-readable. "100" = 100 USDC, "1" = 1 ETH. Do not pass wei or smallest-unit values.
  • Execute in stepIndex order. Wait for CONFIRMED status before sending the next transaction in the array.
  • Never modify unsignedTransaction. Sign exactly what the API returns. Any modification will cause the transaction to fail or behave unexpectedly.
  • Always submit the tx hash after broadcasting. Call PUT /v1/transactions/{txId}/submit-hash with your broadcast tx hash. Required for Yield.xyz to track position status correctly.

Rebalancing

There is no single rebalance tool. To shift capital between strategies:

  1. Call actions_exit on the current position
  2. Call actions_enter on the target

Signing Providers

Yield.xyz returns unsigned transactions. You need a compatible wallet or signing infrastructure to execute them:

ProviderDocsBest for
Privyhttps://docs.privy.io/recipes/agent-integrations/openclaw-agentic-walletsEmbedded wallets, consumer apps
Moonpayhttps://support.moonpay.com/en/articles/586487-moonpay-agents-fund-your-aiEmbedded wallets, user onboarding, and payment infrastructure
BankrBothttps://skills.bankr.bot/Agent-native execution, skill-based automation

For chain-specific transaction formats and signing flows, see references/wallet-integration.md and references/chain-formats.md.

API Keys

Use caseKeyHow to get it
Testing / evaluationShared default, pre-configuredNo action needed
ProductionYour own dedicated keydashboard.yield.xyz

Set YIELDS_API_KEY as an environment variable for production workloads.


What’s Next