Use Case: Mixed REST, WebSocket, and FIX API Cost Estimate
A sample Market Data API pricing simulation for customers using REST, WebSocket Tier 1, WebSocket Tier 2, and FIX API.
Use Case: Mixed REST, WebSocket, and FIX API Cost Estimate
This example estimates a higher-volume Market Data API use case with REST requests, WebSocket Tier 1 Data, WebSocket Tier 2 Data, and FIX API access.
Assumptions
| Item | Value |
|---|---|
| REST usage | 80,000 REST Credits/day |
| Tier 1 WebSocket usage | 400 GiB/day |
| Tier 2 WebSocket usage | 40 GiB/day |
| FIX API usage | 1 single connection, 24 hours/day |
| Usage pattern | Daily production usage |
Included usage by plan
| Plan | REST Credits/day | Tier 1 Data/day | Tier 2 Data/day | FIX API |
|---|---|---|---|---|
| Startup | 1,000 | 32 GiB | Not included | Not included |
| Streamer | 10,000 | 128 GiB | 1 GiB | Not included |
| Pro | 100,000 | 512 GiB | 64 GiB | Single connection included |
Plan comparison
| Plan | Estimated result |
|---|---|
| Pay As You Go | All usage billed as metered usage |
| Startup | Significant REST and WebSocket overage |
| Streamer | Significant REST, Tier 1, and Tier 2 overage |
| Pro | Usage covered within included daily limits |
Why Pro fits this use case
The estimated daily usage is:
| Usage type | Estimated usage | Pro included limit |
|---|---|---|
| REST Credits | 80,000/day | 100,000/day |
| Tier 1 Data | 400 GiB/day | 512 GiB/day |
| Tier 2 Data | 40 GiB/day | 64 GiB/day |
| FIX API | 1 connection, 24 CH/day | Single connection included |
Since each usage type stays within the Pro plan limits, this sample is covered by the Pro plan.
Streamer overage example
Streamer includes:
- 10,000 REST Credits/day
- 128 GiB Tier 1 Data/day
- 1 GiB Tier 2 Data/day
Estimated overage:
| Usage type | Estimated usage | Streamer included | Overage |
|---|---|---|---|
| REST Credits | 80,000/day | 10,000/day | 70,000/day |
| Tier 1 Data | 400 GiB/day | 128 GiB/day | 272 GiB/day |
| Tier 2 Data | 40 GiB/day | 1 GiB/day | 39 GiB/day |
For this sample, Streamer would have recurring overage, while Pro covers the usage within the included limits.
FIX API note
The Pro plan includes a Single Connection for FIX API with a daily allowance of 24 Connection-Hours (CH).
A single FIX connection running continuously for 24 hours uses:
1 connection × 24 hours = 24 CH/day
This is covered by the Pro plan.
Additional FIX connection usage above the included 24 CH/day is billed at:
$0.85 per Connection-Hour
Result
For this sample, Pro is the best fit because it covers the estimated REST, Tier 1, Tier 2, and single-connection FIX usage within the included daily limits.
Streamer may be suitable for lower-volume streaming use cases, but this scenario exceeds Streamer’s REST, Tier 1, and Tier 2 allowances.
Caveat
Actual usage can vary depending on REST endpoint parameters, WebSocket subscriptions, number of symbols, exchange activity, message volume, and FIX connection duration or concurrency.