CoinSpectrum ← the ranking

The CoinSpectrum API

The same once-per-asset counting the site is built on, as JSON. No signup, no key, no query language — one file per thing, served straight from the CDN.

curl https://coin-spectrum.com/api/v1/assets/xrp.json
Live · 5,981 assets · 527 cryptocurrencies

Design

Every endpoint is a plain JSON file. There are no query parameters and no auth on the free tier. Download the file, filter in the client. That is deliberate: it keeps the free tier truly free, and it keeps the surface small enough that a version bump is a real event.

Wrapped, staked and pegged assets are not mixed into the cryptocurrency ranking. If you want them, ask for them explicitly by category. Most crypto APIs cannot answer that question at all.

Base URL

https://coin-spectrum.com/api/v1/

Versioned from day one. Adding a field is a minor change and lands silently; renaming, removing, or changing a shape opens v2/, and v1/ is frozen for at least twelve months.

Endpoints

A worked example

Chain jq for a pure Bash pipeline that names every SHA-256 chain in the ranking:

curl -s https://coin-spectrum.com/api/v1/categories/cryptocurrencies.json \
  | jq -r '.assets[] | select(.consensus == "SHA-256") | .name'

Asset schema

Every asset — cryptocurrency, stablecoin, wrapped, token, memecoin — uses the same shape. Fields that don't apply stay null, never omitted.

{
  "slug":            "bitcoin",
  "symbol":          "BTC",
  "name":            "Bitcoin",
  "category":        "cryptocurrency",
  "consensus":       "SHA-256",
  "hashrate":        8.9e20,
  "price_usd":       77401,
  "market_cap_usd":  1553734997147,
  "rank":            1,
  "supply": { "circulating": 20076428, "max": 21000000 },
  "ledger":          "overlay",
  "nature":          "commodity",
  "nature_basis":    "Named a digital commodity in the joint SEC-CFTC interpretation.",
  "nature_tags":     ["commodity"],
  "chains":          null,
  "image":           "https://..."
}

Update cadence

Rebuilt roughly every ten minutes. Every response includes a generated_at ISO-8601 timestamp; a caller who wants the freshest snapshot should read that field rather than trust HTTP dates. The CDN serves cached copies for 60 s at the edge and 300 s upstream, with a one-hour stale-while-revalidate window.

Rate limits

The free tier has no per-key limit — every response is a static file behind a CDN, so throughput is effectively bounded by the CDN itself. Please cache. Aggressive polling of a file that only changes every ten minutes is wasteful for both sides.

Paid tiers preview

For higher throughput, historical snapshots, webhooks and per-key identification, a paid API lives at api.coin-spectrum.com. Prices are quoted in USD and invoices settle in Bitcoin Cash only, locked at the spot rate for fifteen minutes.

Starter

$5 / mo

~0.015 BCH

  • 300 requests / minute
  • 1 M requests / month
  • Every free-tier endpoint
  • Activates on mempool sighting
Pay in BCH →

Pro

$29 / mo

~0.09 BCH

  • 1 500 requests / minute
  • 10 M requests / month
  • Historical snapshots
  • Webhooks
Pay in BCH →

Business

$149 / mo

~0.45 BCH

  • Unlimited requests / minute
  • Soft cap 100 M / month
  • Priority routing
  • SLA on request
Pay in BCH →

Annual plans pay ten monthly invoices in one BCH transaction and get two months free. No card processor, no chargebacks, no KYC — payment is a single on-chain transaction and the API key activates on the first confirmation.

Attribution

Licensed under CC BY 4.0. Use the data anywhere, commercial use included. In return, please link back to coin-spectrum.com — a footer credit or a note in your project's README is enough. The API exists to be reused; a link is how it stays sustainable.

No warranty

The data is derived from public sources — see methodology. It is provided as-is, without warranty of any kind. If you use it to decide whether to spend money, that is entirely your call and entirely your risk.

Contact

Questions, bug reports, or a request for an endpoint that isn't here yet: open an issue or write to api@coin-spectrum.com.

Common questions

Is the API free?

The /api/v1/ tier is free and unmetered — every file is served straight from the CDN, no signup, no key. Paid tiers on api.coin-spectrum.com add higher throughput, historical endpoints and per-key limits; they are priced in BCH.

Do I need an API key?

Not for /api/v1/. Files are served without authentication and without rate-limiting beyond the CDN's own DDoS protection. Paid tiers issue a key for the proxy endpoint.

How often does the data refresh?

Every ten minutes. Every response carries a generated_at ISO-8601 timestamp so a consumer can decide whether to re-fetch. Prices lag behind the site's own live feed by that window; use the live feed for tickers and the API for structural fields — rank, family, supply, classification.

What does the CC BY 4.0 license mean for my project?

Use the data anywhere — a chart, a screener, an app, a research paper, a commercial product. The only requirement is credit somewhere reasonable: a byline, a data-source line, or a link to coin-spectrum.com. Commercial use is included.

What's the difference between /api/v1/assets/xrp.json and /assets/xrp/?

Same data, two consumers. The JSON is for machines; the HTML page is for readers. Both use the same canonical slug so the two URLs shape-match — one can be derived from the other with a trivial string replacement.

What happens on breaking changes?

v1/ is frozen for at least twelve months from launch. Adding a field is a minor change and lands silently; renaming, removing, or reshaping a field opens v2/, and v1/ keeps serving unchanged until deprecation is announced.