Skip to main content
These guides are how-to: wiring a coding agent or editor to yield.xyz for one concrete job. For what AgentKit, the MCP server, and agent skills are and how they fit together, see AI & Agents.
Not sure which fits? Most people building an integration want one of the first two: an agent that writes the code (AgentKit builder), or an editor that answers accurately while you write it yourself (editor setup). Reach for AgentKit for Claude Code only once you want to run yields conversationally rather than ship code.

Pick your task

The first three guides are build-time: they ground a coding agent in accurate docs and specs while you write an integration. Editor setup needs no API key; the builder asks for yours before it writes code. The fourth is runtime: it connects a live agent to real yield data and wallet actions.

AgentKit builder

Generate a working yield.xyz integration from a description of your app.

Set up your editor

Give Cursor, Claude Code, or another MCP client live docs and spec access.

Prompting patterns

Prompts that produce reviewable, correct output, and how to check it.

AgentKit for Claude Code

Discover yields and build transactions conversationally, inside Claude Code.

The safety rule

Every transaction an agent produces, whether it’s generated code calling the API directly or the MCP server’s action tools, comes back unsigned. Inspect it before signing; never sign or broadcast on an agent’s say-so alone. yield.xyz never signs user transactions and never holds keys. See Guardrails for the full set of rules an agent should follow before it builds or submits anything.