Skip to main content
Beyond raw prices, the API derives two analytics from the index history: price volatility and market utilization. Both need an API key and use the same GPU names and startDate / endDate parameters as the history endpoints.
analytics-volatility

Volatility

How much the price swings.
analytics-utilization

Utilization

How much capacity is rented.

​
Annualized volatility

rolling_volatility is the standard deviation of log returns over a rolling window, annualized. It is a decimal fraction, so 0.80 means roughly 80% annualized volatility. A higher number means the price moves more. Two parameters shape the result:
  • windowDays (default 30, range 1 to 365): the lookback for each point. A shorter window reacts faster, a longer one is smoother.
  • startDate and endDate (both required): the span to return.
Each row pairs the index value with its volatility:
See Get annualized price volatility for all seven language examples.

​
Market utilization

utilization_ratio is the share of tracked capacity that is currently rented, as a decimal fraction. 0.70 means about 70% utilized. Utilization often moves ahead of price, since tight supply tends to precede a price rise. GET /api/gpu/{gpuName}/volume-metrics?startDate=...&endDate=... returns a series:

​
Notes

  • Every analytics endpoint needs an API key. See Authentication.
  • Series come back most-recent-first. Sort ascending before you plot or compute returns.
  • Ranged analytics default to daily granularity, but hourly is available via the granularity parameter. The underlying index updates hourly. See The Price Index.