Market coins

Price, market cap, volume and all-time extremes for the ranked coin universe, with 24h / 7d / 30d change already computed.

1,300+ranked coins

price and rank are on every record; market_cap on 98% and volume on 99%. The percentage-change fields are precomputed across three windows, so a mover list needs no history calls.

What's in a record

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

id
name
ticker
slug
icon
rank
price
market_cap
volume
price_percent_change_24h
price_percent_change_7d
price_percent_change_30d
high_24h
low_24h
ath
atl
updated_at

{
  "id": 1,
  "name": "Bitcoin",
  "ticker": "BTC",
  "slug": "bitcoin",
  "rank": 1,
  "price": 80433.2310665514,
  "market_cap": 1611653315762.6667,
  "volume": 20546803091.92952,
  "price_percent_change_24h": -1.1334662209728525,
  "price_percent_change_7d": 2.853303977829609,
  "price_percent_change_30d": 4.361915472905906,
  "high_24h": 81937.95,
  "low_24h": 80131.51333333332,
  "ath": 126192.65666666666,
  "atl": 67.81,
  "updated_at": "2026-09-20T12:07:16Z"
}

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/market/coins/?limit=5

MCP tools

get_market_coinsget_market_coins_detailget_market_coins_historyget_market_trendingget_market_trending_detail

What it's for

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

A movers board with no arithmetic: price_percent_change_24h, _7d and _30d are already on the row, so ranking by momentum is a sort rather than a history walk.
Drawdown and recovery framing: ath and atl sit beside price on 86% of rows, so "how far off the high" is one subtraction and needs no separate endpoint.
Coin resolution for every other endpoint here: slug is the join key that /kasandra/patterns/{coin}/ and the tag filters expect — bitcoin, never BTC.

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.

updated_at is per coin, and the spread is months.

Walked all 1,321 rows on 20 Sep 2026: updated_at spans 2026-05-25 to 2026-09-20 across 69 distinct days. The top of the book is fresh; the long tail is not. Read updated_at before treating a row as current, and do not present the set as a single market snapshot.

ath and atl are missing on 14% of rows.

1,138 of 1,321 carry ath, 1,134 carry atl — newer listings mostly. A drawdown view has to tolerate nulls rather than assuming the pair is always present.

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.

All 22 capabilities Cookbook: worked use cases

The crypto data layer for humans, apps, and AI agents.

Product

Launch app Dashboards API & MCP Docs Pulse Recipes

Company

Blog Contact Give Feedback Terms of Use Privacy Policy

Crypto 101

What is Bitcoin?What Is Ethereum?What is Wrapped Crypto?What is Arbitrum?What is zkSync?

Learn

Making Money with Cryptocurrency How to Build a Cryptocurrency Dashboard What Is Crypto Halving: A Bitcoin Story How To Set Up Ethereum Wallet How to Read Crypto Charts Crypto Asset Management Guide Staking vs. Liquidity Mining (Yield Farming)