yield-xyz-agentkit-builder

Yield.xyz AgentKit — Builder Skill

This skill helps developers build applications that integrate with the Yield.xyz API. It generates integration code, guides architecture decisions, and helps ensure correct API usage across all supported chains and protocols.

Scope: this skill builds Yield integrations — staking, lending, vaults, and RWA across 80+ networks.

What ships vs. what's build-time: the integration you ship always calls https://api.yield.xyz directly — via the @yieldxyz/sdk or REST/curl. Nothing the user ships calls the MCP. The MCP's doc tools are only a build-time reference for you (the builder) — they let you ground field names against the live spec/docs while generating code. The MCP is not a runtime dependency and not a hard prerequisite; if it's unavailable, fetch https://api.yield.xyz/docs.json directly.

Quickstart — minimal end-to-end (Yield)

The shortest happy path from nothing to a confirmed position. Language-agnostic REST; swap curl for fetch/requests/etc. Always confirm exact field names against the live spec (yield_get_api_spec or https://api.yield.xyz/docs.json) before generating code — the shapes below are a map, not a contract.

1. Discover — GET /v1/yields?network=<network>&token=<token> to find a yield id.
2. Read the schema — GET /v1/yields/{id} and read mechanics.arguments.enter.fields[] to learn exactly which arguments the enter action requires (e.g. amount, sometimes a validator address).
3. Build the action — POST /v1/actions/enter with { yieldId, address, arguments } (amounts are human-readable strings, not wei). Returns HTTP 201 with a transactions[] array.
4. Sign + broadcast each transaction — iterate transactions[] in stepIndex order; for each, parse and sign its unsignedTransaction with the wallet for that chain, then broadcast. Never modify unsignedTransaction (Critical Rule #5).
5. Report the hash — PUT /v1/transactions/{id}/submit-hash with the broadcast hash so Yield.xyz can track it.
6. Poll to confirm — GET /v1/transactions/{id} until status is CONFIRMED (there are no webhooks — poll with backoff).