Use Cases

Use Case: REST Historical Daily Exchange Rates for Reporting

A sample Exchange Rates API pricing simulation for downloading one year of historical daily rates for multiple asset pairs.

Use Case: REST Historical Daily Exchange Rates for Reporting

This example estimates the cost of downloading historical daily exchange rates for reporting, accounting, or reconciliation.

Assumptions

ItemValue
ProtocolREST
Endpoint patternGET /v1/exchangerate/{asset_id_base}/{asset_id_quote}/history
Asset pairsBTC/USD, ETH/USD, SOL/USD, XRP/USD, ADA/USD
Period1DAY
Time range2025-01-01 to 2025-12-31
Rates per pair365
Estimated usage1,825 rates

Example requests:

PairExample endpoint
BTC/USDGET /v1/exchangerate/BTC/USD/history?period_id=1DAY&time_start=2025-01-01&time_end=2026-01-01
ETH/USDGET /v1/exchangerate/ETH/USD/history?period_id=1DAY&time_start=2025-01-01&time_end=2026-01-01
SOL/USDGET /v1/exchangerate/SOL/USD/history?period_id=1DAY&time_start=2025-01-01&time_end=2026-01-01
XRP/USDGET /v1/exchangerate/XRP/USD/history?period_id=1DAY&time_start=2025-01-01&time_end=2026-01-01
ADA/USDGET /v1/exchangerate/ADA/USD/history?period_id=1DAY&time_start=2025-01-01&time_end=2026-01-01

Rate usage

Historical daily data is billed by rate count.

For this example:

365 daily rates per pair × 5 pairs = 1,825 rates

Pay As You Go estimate

Using the daily tiered rate pricing:

TierUsageCost
First 100 rates/day100$0.50
Next 100 rates/day100$0.40
Next 100 rates/day100$0.30
Next 100 rates/day100$0.20
Next 600 rates/day600$0.60
Remaining rates825$0.41
Total1,825$2.41

Plan comparison

PlanPrice per CreditMonthly costIncluded creditsEstimated cost
Pay As You Go$1.00/CreditNo commitmentN/A$2.41
Committed 64$0.85/Credit$64~75.29 credits$64.00
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 one-time historical download sample, Pay As You Go is the simplest and lowest-cost option.

Committed plans are better suited when the customer expects recurring monthly usage across REST, WebSocket, or larger historical downloads.

Caveat

This example assumes the historical data is downloaded in one day. Daily pricing tiers reset each day, so splitting downloads across multiple days can affect the total estimate.

Service StatusGitHub SDK