All capabilities

Stablecoins

Every tracked stablecoin with what it pegs to, how the peg is held, its circulating supply and its current price.

420+stablecoins

peg_type, peg_mechanism and symbol are on 100% of records, circulating_usd on all but two. The peg fields are the reason to use this rather than a price feed.

What's in a record

Every field the corpus returns for one record. Real shape — walked corpus-wide, not sampled.

  • id
  • stablecoin_id
  • name
  • symbol
  • peg_type
  • peg_mechanism
  • circulating_usd
  • price
  • date
{ "id": 1, "stablecoin_id": "1", "name": "Tether", "symbol": "USDT", "peg_type": "peggedUSD", "peg_mechanism": "fiat-backed", "circulating_usd": 182097304516.19, "price": 1.0, "date": "2026-09-19T09:07:21.416687Z" }

Get it

A curl that runs against the live API right now, plus the MCP tool names for the same data.

curl https://api.alphaday.com/tvl/stablecoins/?peg_type=peggedUSD

MCP tools

get_tvl_stablecoinsget_tvl_stablecoins_detail

What it's for

Three concrete questions this capability answers that a general crypto API does not.

  • Peg-risk screening as a filter rather than a research project: 253 of 428 are crypto-backed, 147 fiat-backed and 27 algorithmic — the mechanism that determines how a depeg behaves is a field, not a footnote.
  • Non-USD stablecoin discovery: ?peg_type=peggedUSD returns 339, which leaves 89 pegged to EUR (26), a basket (10), BRL (5), JPY (5) and others. Most dashboards never show these.
  • Depeg monitoring: price beside peg_type makes deviation computable directly, with no separate oracle call.

Known limits

Required, not optional. Coverage gaps, staleness and parameter traps that were observed by running the curl above against the live server on 2026-09-18.

peg_mechanism contains a misspelled value.

One record reads crytpo-backed rather than crypto-backed. An equality filter on the correct spelling silently drops it. Normalise before grouping, or match on both — the value set is otherwise crypto-backed (253), fiat-backed (147) and algorithmic (27).

price is missing on 28% of records.

308 of 428 carry one. Depeg detection therefore covers roughly three-quarters of the corpus, and the gaps skew toward the smaller and more obscure coins — which are the ones most likely to depeg.

date is the record's own reading.

Each row carries its own timestamp rather than sharing a snapshot time. Compare circulating_usd across coins only when their dates agree.

Figures and payloads verified against the live API on 2026-09-18. The API needs no key and no signup — see the full endpoint reference and the MCP server.