Skip to main content
Glama

rate-hub

get_series

Price history of one asset for charts (GET /v1/rates/series). Crypto: every range. Fiat: 1d and 7d from rate-hub's own readings taken about every 30 minutes; 30d, 90d, 1y and max one point per UTC day from the daily archive (it has a start day, days without a document are skipped, a cold range fills over a few retries, so an early answer may have fewer points). A fiat with no reading in the range, or an unknown uid, answers status unsupported with empty points, not an error. status: ok = fresh series; stale = last cached series, upstream failed (see fetched_at); pending = not ready, retry after retry_after seconds; unsupported = unknown uid, an asset no upstream knows, or a fiat with no reading in the range. Size: about 110 bytes per point (both copies of the result). max_points (2..500, default 100) downsamples evenly and keeps the first and last point; pass 500 for full detail. A non-USD fiat quote clips the series at the start of the fiat archive (range max only), and with a dynamic coin an unsupported answer may mean its uid expired. Edge cases: read resource ratehub://docs/behavior (behaviour notes).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
vsYesQuote currency
uidYesCatalog uid of a crypto asset
rangeYesChart range
max_pointsNoDownsample to at most this many points, 2..500 (default 100); first and last points are kept

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
vsYes
uidYes
buildYes
rangeYes
pointsYes
sourceNo
statusYes
fetched_atNo
retry_afterNo
server_timeYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

Score is being calculated.

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources