Supported venues

List venues is the live registry of where the auction can allocate:

curl "https://meadow.example.com/v1/venues?chain=84532" -H "api-key: $EDITH_API_KEY"

Each venue entry:

{
  "id": "usdc-vault-1",
  "name": "USDC Yield Vault",
  "protocol": "erc4626",
  "chain": 84532,
  "asset": "0xUSDC…",
  "vault": "0xVault…",
  "apyBps": 520,
  "riskTier": "balanced",
  "healthy": true
}

Field	Meaning
protocol	The venue type — ERC-4626 vaults and protocol receipt-token venues.
vault	The on-chain contract your shares live in. This is where your position actually sits.
apyBps	Current indicative gross APY in basis points (auction bids are the binding number).
riskTier	The tier this venue counts as when your intent filters by risk.
healthy	Live health check. Unhealthy venues receive no allocations.

Discovery endpoints

• List chains — chains that currently have at least one venue.
• List assets — depositable assets per chain.
• Get rates — best indicative APY per asset (query: asset, chain, and optional risk_tier — note the snake_case parameter on this endpoint).

Hyperliquid Core venues

On HyperCore chains (10200000 / 10200001) the registry can include Core-native venues:

Protocol	What it is	Intent asset
hypercore-vault	HLP-style vault deposits (vaultTransfer)	0x0000…0000 (Core USD; amounts in micro-USD)
hypercore-staking	HYPE staking delegation (tokenDelegate)	0x2222…2222 (HYPE; amounts in 8-decimal units)

These settle with a single signTypedData signature — no gas, no EIP-7702 — see Core concepts. The staking venue delegates HYPE you already hold staked; the vault field of a staking venue holds the validator address.

Info

Venue coverage is a deployment property and grows over time. Query the registry rather than hardcoding venue ids — and remember allowedVenues on Request a quote if you need to pin an allow-list.