Skip to main content

Get Yield Info

Retrieve comprehensive details about a specific yield opportunity, including APY/APR rates, token metadata, validator information, protocol details, cooldown periods, and action requirements.

When to Use

Activate this skill when the user asks to:
  • Get details about a specific yield (e.g., “Tell me about Lido ETH staking”)
  • Check the current APY/APR for a yield
  • View validators available for a staking yield
  • Understand the requirements or arguments needed to enter/exit a yield
  • Check if a yield supports certain actions (enter, exit, manage)
  • View cooldown or warmup periods for a yield

Authentication

All requests require an API key in the x-api-key header:

Base URL

Step-by-Step Instructions

Step 1: Get Yield Metadata

Endpoint: GET /v1/yields/{yieldId} Path Parameters: Example Request:
Example Response:

Step 2: Get Validators (for Staking Yields)

Endpoint: GET /v1/yields/{yieldId}/validators Query Parameters: Example Request:
Example Response:

Step 3: Get Provider Details

Endpoint: GET /v1/providers/{providerId}

Step 4: Determine Yield ID

If the user provides a token and protocol name rather than a yield ID, use the search endpoint:
Yield IDs follow the pattern: {network}-{token}-{provider}-{type} Common examples:
  • ethereum-eth-lido-staking — Lido ETH liquid staking
  • ethereum-usdc-aave-v3-lending — Aave V3 USDC lending on Ethereum
  • cosmos-atom-native-staking — Cosmos ATOM native staking
  • solana-sol-native-staking — Solana SOL native staking
  • ethereum-usde-ethena-staking — Ethena USDe staking

Key Response Fields

Presenting Information

When presenting yield info to the user, format it clearly:
  1. Name and type (e.g., “Lido ETH Staking on Ethereum”)
  2. Current rate (e.g., “3.5% APY”)
  3. Token and network
  4. Status (accepting deposits / withdrawals)
  5. Cooldown/warmup periods if applicable
  6. Validators (for staking yields — show top preferred validators)

Error Handling

Edge Cases

  • Yield not found: If a 404 is returned, the yield ID may be incorrect or the yield may have been deprecated. Search using GET /v1/yields?search=... to find the correct ID.
  • Validators not available: Not all yields have validators. Lending and vault yields typically do not. Only staking and restaking yields have validators.
  • Deprecated yields: Some yields may exist but have status.enter: false, meaning no new deposits are accepted.
  • Multi-token yields: Some yields (e.g., LP positions) may have multiple canonical tokens. Check the canonicalTokens field if present.
  • Rate fluctuations: Yield rates change frequently. Always present rates as “current” and note they may change.