Use Cases

Use Case: REST OHLCV Daily Backfill Cost Estimate

A sample Market Data API pricing simulation for daily REST OHLCV historical downloads.

Use Case: REST OHLCV Daily Backfill Cost Estimate

This example estimates the cost of using the Market Data API REST protocol to download 1MIN OHLCV history for multiple symbols each day.

Assumptions

ItemValue
ProtocolREST
Endpoint typeHistorical OHLCV
Symbols50 symbols
Period1MIN
Time range1 day per symbol
Data points per symbol1,440
Total data points per day72,000
REST credit rule100 data points = 1 REST Credit
Estimated REST Credits/day720 REST Credits

Estimated REST usage

72,000 data points รท 100 = 720 REST Credits/day

Plan comparison

PlanIncluded REST Credits/dayEstimated result
Pay As You GoMetered720 REST Credits/day billed as used
Startup1,000 REST Credits/dayCovered
Streamer10,000 REST Credits/dayCovered, but more than needed
Pro100,000 REST Credits/dayCovered, but more than needed

Pay As You Go estimate

REST Credits are priced using daily tiers. Since this example uses fewer than 1,000 REST Credits/day, the first tier applies:

720 รท 1,000 ร— $5.26 = $3.79/day

Estimated 30-day usage:

$3.79 ร— 30 = $113.70/month

Result

For this sample, Startup may be the best fit because the usage stays within the included 1,000 REST Credits/day.

Pay As You Go may still be simpler for occasional or irregular backfills. Streamer and Pro are better suited for customers with higher REST usage or WebSocket data needs.

Caveat

REST Credit usage depends on the endpoint and request parameters. When the limit parameter is used, each 100 data points returned is counted as one REST Credit. If limit is not used or not available, each API call is counted as one request.

Service StatusGitHub SDK