yield-xyz-agentkit-moonpay

Yield.xyz AgentKit × MoonPay

The MoonPay connector for the Yield.xyz AgentKit: MoonPay handles wallet auth and signs + broadcasts the transactions that yield-xyz-agentkit builds.

yield-xyz-agentkit (this skill's base) owns all yield logic — discovery, schemas, validator selection, balances, building unsignedTransaction (actions_enter / actions_exit / actions_manage), output formatting, and the MCP tool reference. Use it for all of that; this skill only signs and broadcasts.

MoonPay             → confirm auth + wallet (provides the address)
yield-xyz-agentkit  → discover yield + build unsignedTransaction
MoonPay             → sign + broadcast
yield-xyz-agentkit  → submit_hash + poll get_transaction

---

Two MCPs, One Flow

This skill requires both MCP servers connected:

MCP	Role
Yield.xyz AgentKit	Yield discovery + transaction building (owned by the yield-xyz-agentkit skill)
MoonPay	Auth + wallet + sign + broadcast — wallet_list, transaction_sign, transaction_send, token_balance_list, and more

If either MCP is missing, stop and tell the user. See references/setup.md for connection instructions.

---

CRITICAL

• Never modify unsignedTransaction before signing — not addresses, amounts, fees, or encoding, on any chain. If anything looks wrong, have yield-xyz-agentkit build a NEW action. Modifying it will result in permanent loss of funds.
• Never call the Yield.xyz API directly (curl/HTTP) — it requires an API key and returns 401. All Yield.xyz access goes through the MCP (handled by the yield-xyz-agentkit skill).

---

Full Flow

Step 1 — Check MoonPay auth and wallet

Before anything else:

1. Call MoonPay wallet_list to confirm a wallet exists.
2. If no wallet or not authenticated, guide the user through login (they receive an email code; once verified they can proceed).
3. Note the wallet address — this is the address the yield-xyz-agentkit skill uses in all its calls.