Short answer:
No, one credit doesn’t always equal one API call.
For some endpoints, especially in the Market Data API, credit usage depends on the volume of data returned, not just the number of requests.
How Credit Usage Works for the Market Data REST API
Endpoints such as historical trades, quotes, or OHLCV lists accept a limit parameter.
When this parameter is used, billing is based on data points, not per-call billing.
Rule:
Every 100 data points = 1 credit (rounded up).
Examples:
| Request | Data Points Returned | Credits Charged |
| GET /v1/ohlcv/BTC/USD/latest | 1 | 1 credit |
| GET /v1/trades/history?limit=100 | 100 | 1 credit |
| GET /v1/trades/history?limit=250 | 250 | 3 credits |
This approach ensures fairness between lightweight users and those performing heavy historical or multi-symbol queries.
Example Calculation
Let’s say you want to get 1-second interval OHLCV data for one symbol over one full day:
- Total seconds per day = 24 × 60 × 60 = 86,400 data points
- Credit cost = 86,400 ÷ 100 = 864 credits
- PAYG tier rate = $5.26/1,000 credits
- Approximate cost = $4.54 for that query
This transparent model makes it easy to forecast your data costs before running large-scale jobs.
How Credits Translate Into Pricing
REST API credits are priced on a tiered, daily reset structure, meaning that high-volume users automatically receive lower rates.
Credits are always billed per 1,000 units, with rates decreasing as your daily usage grows.
Pay As You Go example:
| Usage | Rate | Cost |
| First 1,000 credits | $5.26 / 1k | $5.26 |
| Next 1,500 credits | $2.63 / 1k | $3.95 |
| Total (2,500 credits) | $9.21 |
Professional Plan example:
| Usage | Rate | Cost |
| First 100,000 credits (quota) | Included | $0.00 |
| Next 50,000 credits | $0.20 / 1k | $10.00 |
| Total cost (150,000 credits) | $10.00 extra per day |
This tiered logic rewards active users and makes scaling predictable for enterprise teams.
REST vs. Streaming vs. FIX Pricing Models
| Protocol | Billing Metric | Notes |
| REST (Market Data) | 1 credit per 100 data points | Ideal for on-demand historical queries |
| WebSocket (Tier 1 Data) | Measured in GB (trade/quote/order book data) | Starts at $1.00/GB, decreasing with higher usage |
| WebSocket (Tier 2 Data) | Measured in MB (metadata, OHLCV, exchange rates) | Starts at $0.0625/MB, dropping with scale |
| FIX API | Per Connection-Hour (CH) | 1 FIX connection = 1 CH/hour; additional CH = $0.85 |
Each API type uses units that reflect resource intensity, data volume for WebSocket, query volume for REST, and connection time for FIX.
Why 1 Credit ≠ 1 Call
Flat credit-per-call pricing would be misleading for data-heavy workloads.
In practice, credit consumption varies with:
| Factor | Description | Example Impact |
| Data complexity | Level of granularity | Tick or L3 data > OHLCV |
| Time range | Historical depth | 1 month > 1 day |
| Exchange scope | Number of markets in one call | Multi-exchange query > single exchange |
So while a metadata query may only cost 1 credit, a full-depth order book or multi-year tick history request could consume dozens - even hundreds - of credits.
Tips to Optimize Credit Usage
- Batch requests efficiently: Avoid overlapping symbol/time ranges.
- Cache static data: Reuse metadata (symbols, assets, exchanges).
- Use streaming: Continuous WebSocket feeds are more credit-efficient for live updates.
- Schedule heavy jobs: Run large backfills during off-peak hours to improve performance.
Following these practices can reduce credit usage by 30–50% without sacrificing coverage.
Related FAQs
- API Rate Limits and Credit Consumption Guide. CoinAPI Usage and Billing Explained
- What you get with a free crypto API from CoinAPI ($25 credits)
- How to Use CoinAPI effectively Without Exceeding Free Credits
Summary
Credits are the currency of data access, but they don’t always map 1:1 with API calls.
CoinAPI’s pricing is transparent, whether you use REST, WebSocket, or FIX, aligning cost with the true volume of data processed rather than arbitrary call counts.
This ensures predictable scaling and fair billing for both small developers and enterprise-level trading systems.
