Read protocol TVL, chain totals and pool APY per request

Five reads that answer the questions a DeFi agent actually asks. The protocols list ranks everything tracked by total value locked; the single-protocol read returns one protocol's TVL history broken down by chain; the chains read gives the TVL total per chain; the yields read returns every tracked pool with its current APY and size; and the prices read resolves token identifiers to a spot figure. Nothing needs an account, a key or a plan.

Two of the five take their argument as a path segment rather than a query parameter, which is the detail that trips a first integration: a protocol is addressed as protocol/{slug} and tokens as prices/{coins}, with the coin identifier carrying its own namespace. The parameter table on this page renders those from the same registry the router matches against, so the example beside each one is a request that resolves.

The yields read is deliberately unfiltered and large. It returns the whole pool set in one response so an agent can rank, filter and compare in its own process, rather than paging through a server-side filter that has to be learned first. That makes it the heaviest call in the family and the one worth caching on your side.

In Claude Code, Claude Desktop, Cursor, Windsurf, Cline and any other MCP host, this is the blockrun_defi tool of the BlockRun MCP server — the agent calls it like any other tool and the result comes back in the conversation. In OpenClaw, Codex and Hermes, ClawRouter exposes the same catalog. In your own code, the Python and TypeScript SDKs wrap the endpoint above with types; any HTTP client works too. Every harness, with its setup →

No account and no API key stand between an agent and the first call: the request is quoted in dollars and the agent's client pays it. A team that prefers keys gets one, with a monthly invoice.

DefiLlama publishes these numbers itself and is the source behind this endpoint, so the data is the same data. What differs is how an agent reaches it: one payment header instead of a separate base URL per product family, and one request shape that already sits beside the model, search and market endpoints the same agent is calling. If your service already talks to DefiLlama directly and is happy, there is nothing here to win.

Dune is the tool when the question is not on anyone's dashboard: you write SQL against indexed chain data and get exactly the cut you asked for, at the cost of writing and maintaining the query. Token Terminal sells curated financial metrics with a sales conversation attached. This is neither. It is the pre-computed TVL, yield and price reads, fetched per call, for an agent that wants a number now and has no seat, no query to maintain and no contract.

The honest limit: these are reads of someone else's index, at that index's refresh cadence, and the yields response is large enough that an agent calling it in a loop should cache. Nothing here writes, quotes or executes — for a swap price the DEX endpoint is the right neighbour, and for a spot close the market-data endpoint is free.