Indexes API Pricing Use Cases
Sample pricing simulations to help estimate Indexes API usage across REST and WebSocket usage patterns.
Indexes API Pricing Use Cases
These use cases show how Indexes API pricing can be estimated across common REST and WebSocket usage patterns.
Each example is based on a specific scenario to help customers understand API calls, WebSocket data transfer, Usage Credits, Pay As You Go pricing, committed plans, and overages.
These examples are pricing simulations only. Actual usage may vary depending on the number of indexes, endpoint used, polling frequency, WebSocket subscriptions, transferred data volume, reconnect behavior, and daily usage volume.
Before using these estimates
Indexes API usage may include:
- API calls, based on REST requests, WebSocket subscribe messages, or other actions sent to the API.
- WebSocket data transfer, based on the amount of data sent from our servers to the client.
API call and data transfer pricing tiers reset daily. Usage paid with committed usage credits is counted toward the daily tiers.
How to read the examples
Each use case includes:
- The protocol used, such as REST or WebSocket
- Example index symbols and endpoints
- Estimated daily or monthly usage
- A Pay As You Go estimate
- A comparison across committed usage plans
- Caveats that may affect real-world usage
For a general explanation of Usage Credits, committed plans, and overage billing, see the Usage Credits billing guide.