Key Rules
These rules apply to every transaction flow built with the Yield.xyz Agent Openclaw Skill.
Transaction Rules
- Always call
yields_getfirst. 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-hashwith 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:
- Call
actions_exiton the current position - Call
actions_enteron the target
Signing Providers
Yield.xyz returns unsigned transactions. You need a compatible wallet or signing infrastructure to execute them:
| Provider | Docs | Best for |
|---|---|---|
| Privy | https://docs.privy.io/recipes/agent-integrations/openclaw-agentic-wallets | Embedded wallets, consumer apps |
| BankrBot | https://skills.bankr.bot/ | Agent-native execution, skill-based automation |
| Moonpay | https://support.moonpay.com/en/articles/586487-moonpay-agents-fund-your-ai | Embedded wallets, user onboarding, and payment infrastructure |
For chain-specific transaction formats and signing flows, see references/wallet-integration.md and references/chain-formats.md.
API Keys
| Use case | Key | How to get it |
|---|---|---|
| Testing / evaluation | Shared default, pre-configured | No action needed |
| Production | Your own dedicated key | dashboard.yield.xyz |
Set YIELDS_API_KEY as an environment variable for production workloads.
Updated 3 days ago
What’s Next
