Use Case: REST Current Index Values for a Dashboard
A sample Indexes API pricing simulation for polling current index values using REST.
Use Case: REST Current Index Values for a Dashboard
This example estimates the cost of polling current index values for a dashboard or internal monitoring tool.
Assumptions
| Item | Value |
|---|---|
| Protocol | REST |
| Endpoint pattern | GET /v1/indexes/{index_id}/current |
| Indexes | IDX_REFRATE_PRIMKT_BTC_USD, IDX_REFRATE_PRIMKT_ETH_USD, IDX_REFRATE_PRIMKT_SOL_USD, IDX_REFRATE_PRIMKT_XRP_USD, IDX_REFRATE_PRIMKT_ADA_USD |
| Number of indexes | 5 |
| Polling frequency | Every 1 minute |
| Polling cycles per day | 1,440 |
| API call rule | Each request counts as 1 API call |
| Estimated usage | 7,200 calls/day |
Example requests:
| Index | Example endpoint |
|---|---|
| BTC | GET /v1/indexes/IDX_REFRATE_PRIMKT_BTC_USD/current |
| ETH | GET /v1/indexes/IDX_REFRATE_PRIMKT_ETH_USD/current |
| SOL | GET /v1/indexes/IDX_REFRATE_PRIMKT_SOL_USD/current |
| XRP | GET /v1/indexes/IDX_REFRATE_PRIMKT_XRP_USD/current |
| ADA | GET /v1/indexes/IDX_REFRATE_PRIMKT_ADA_USD/current |
Estimated usage
5 indexes × 1,440 polling cycles = 7,200 API calls/day
Pay As You Go estimate
API call pricing is tiered daily.
| Tier | Usage | Cost |
|---|---|---|
| First 50,000 calls/day | 7,200 | $4.32 |
| Total/day | 7,200 | $4.32 |
Calculation:
7,200 ÷ 1,000 × $0.60 = $4.32/day
Estimated 30-day usage:
$4.32 × 30 = $129.60/month
Plan comparison
| Plan | Price per Credit | Monthly cost | Included credits | Estimated monthly cost |
|---|---|---|---|---|
| Pay As You Go | $1.00/Credit | No commitment | N/A | $129.60 |
| Committed 64 | $0.85/Credit | $64 | ~75.29 credits | $118.31 |
| 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 sample, Committed 64 has the lowest estimated cost.
Pay As You Go may still be simpler for occasional or unpredictable polling. Larger committed plans are better suited for higher recurring usage.
Caveat
Actual usage depends on the number of indexes, polling frequency, and whether the integration also calls discovery or metadata endpoints such as GET /v1/indexes or GET /v1/metadata/periods.
Indexes API Pricing Use Cases
Sample pricing simulations to help estimate Indexes API usage across REST and WebSocket usage patterns.
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.