Yield Agentkit Moonpay

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

Input & Output Formatting

For exact input types for all Yield.xyz AgentKit MCP tools, see references/input-format.md.

For all Yield.xyz tool display rules, number formatting, badges, tables, and action summaries, see references/output-formats.md.

Never dump raw JSON or plain comma-separated data. Always follow the formats defined there.

MANDATORY: Before querying anything from Yield.xyz AgentKit MCP read references/input-format.md and before displaying any results, read references/output-formats.md using the Read tool. Do not skip this step.

⚠️ API Usage Policy

You must follow the guidelines defined in policies.md for Yield AgentKit MCP API usage, data fetching, and efficiency.

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 will receive a code by email
   • Once verified they can proceed
3. Note the wallet address, this is the address used in all AgentKit MCP calls

Step 2 — Discover yields

Call yields_get_all with the user's preferred network and token.

• Sort results: preferred validators/yields first, then by APY descending
• Show a table: Protocol, Type, APY, Network, Token
• Default to limit: 20 unless user asks for more
• Valid type values: staking, restaking, lending, vault, real_world_asset, concentrated_liquidity_pool, liquidity_pool

Step 3 — Inspect the yield

Call yields_get with the chosen yieldId. Read:

• mechanics.arguments.enter — exact fields required for this yield
• mechanics.entryLimits — min/max amounts
• inputTokens[] — what tokens are accepted
• mechanics.requiresValidatorSelection — if true, call yields_get_validators

Never skip this step. Each yield has a different schema.

Step 4 — Select validator (if required)

If mechanics.requiresValidatorSelection === true:

• Call yields_get_validators
• Show table: Validator, Commission, APY, TVL, Voting Power
• Preferred validators first, then APY descending
• Recommend the top preferred validator but always confirm with user
• Never pick autonomously

Step 5 — Build the transaction

Call actions_enter with:

• yieldId
• address — from MoonPay wallet (Step 1)
• arguments — exactly as defined in mechanics.arguments.enter
• Amounts are human-readable: "1" = 1 ETH, "100" = 100 USDC

The response contains transactions[] ordered by stepIndex.

Step 6 — Sign and broadcast via MoonPay

This step is critical. Read references/moonpay-tools.md in full before proceeding.

Mistakes here result in permanent loss of funds or a silent failure

You now have transactions[] from Step 5, ordered by stepIndex. Execute each transaction sequentially, never in parallel, never out of order. Do not begin transaction N+1 until transaction N is CONFIRMED.

Step 7 — Confirm

After all transactions are confirmed:

• Call yields_get_balances with the network and address
• Show the user their new position: balance, pending rewards, APY

Manage / Exit Flow

For claiming rewards, restaking, or exiting:

1. Call yields_get_balances — read pendingActions[]
2. Each action has type, passthrough, optional arguments
3. Call actions_manage or actions_exit with values from the response
4. Sign each transaction via MoonPay (same as Step 6)

Error Handling

References

Read these on demand when you need specifics:

• references/setup.md — installing both MCPs, auth flow, prerequisites
• references/key-rules.md — argument rules, amount formatting, tx ordering
• references/moonpay-tools.md — MoonPay MCP tool reference
• references/policies.md — API usage and policies
• references/output-formats.md — output formats for agent to follow to display the outputs to user