Use Cases

Use Case: REST Historical Index Timeseries for Multi-Asset Analytics

A sample Indexes API pricing simulation for downloading high-volume historical index timeseries using REST.

Use Case: REST Historical Index Timeseries for Multi-Asset Analytics

This example estimates the cost of downloading historical index timeseries for a multi-asset analytics platform.

Assumptions

ItemValue
ProtocolREST
Endpoint patternGET /v1/indexes/{index_id}/timeseries
Indexes25 indexes
Example indexesIDX_REFRATE_PRIMKT_BTC_USD, IDX_REFRATE_PRIMKT_ETH_USD, IDX_REFRATE_PRIMKT_SOL_USD, IDX_REFRATE_PRIMKT_XRP_USD, IDX_REFRATE_PRIMKT_ADA_USD
Period1MIN
Time range30 days
Data points per index43,200
API call ruleWith limit, every 100 output items count as 1 request
Estimated usage10,800 API calls

Example request:

Example endpoint
GET /v1/indexes/IDX_REFRATE_PRIMKT_BTC_USD/timeseries?period_id=1MIN&time_start=2026-05-01T00:00:00Z&time_end=2026-05-31T00:00:00Z&limit=100000

Estimated usage

Each index returns:

30 days ร— 1,440 minutes/day = 43,200 data points

With the limit parameter, every 100 output items count as one request:

43,200 รท 100 = 432 API calls per index

For 25 indexes:

432 calls ร— 25 indexes = 10,800 API calls

Pay As You Go estimate

API call pricing is tiered daily.

TierUsageCost
First 50,000 calls/day10,800$6.48
Total10,800$6.48

Calculation:

10,800 รท 1,000 ร— $0.60 = $6.48

Monthly recurring estimate

If this same workload is run daily for rolling analytics or daily backfills:

$6.48/day ร— 30 days = $194.40/month

Plan comparison

PlanPrice per CreditMonthly costIncluded creditsEstimated monthly cost
Pay As You Go$1.00/CreditNo commitmentN/A$194.40
Committed 64$0.85/Credit$64~75.29 credits$183.11
Committed 256$0.75/Credit$256~341.33 credits$256.00
Committed 512$0.70/Credit$512~731.43 credits$512.00
Committed 1024$0.65/Credit$1,024~1,575.38 credits$1,024.00

Result

For this recurring monthly sample, Committed 64 has the lowest estimated cost.

Pay As You Go may still be better for one-time historical downloads. Committed plans become more useful when the customer runs similar historical timeseries jobs repeatedly or combines this workflow with other Indexes API usage.

Caveat

This estimate assumes the limit parameter is used. If limit is not used or not available for an endpoint, each API call is counted as one request. Daily pricing tiers reset each day, so usage patterns and batching can affect the final estimate.

Service StatusGitHub SDK