Skip to main content
The CoinStats API uses a flexible credit system that can dynamically adjust costs based on the complexity and scale of your requests.

​
How Credits Work

Every API endpoint has a base credit cost, but some endpoints use multipliers to scale costs based on the parameters you provide. This ensures fair pricing - simple requests cost less, while complex requests that require more resources cost proportionally more.

Fixed Credits

Simple endpoints with constant resource usage have fixed credit costs

Dynamic Credits

Advanced endpoints scale costs based on request complexity using multipliers

​
Understanding Multipliers

Multipliers allow endpoints to calculate credits based on:
Parameters in the URL query string (e.g., ?networks=ethereum,polygon)
Data sent in POST/PATCH request bodies, including nested objects

​
How Multiplier Calculation Works

The total credit cost is calculated by applying multipliers to each parameter individually:
Total Credits = Sum of (Base Credits × Multiplier for each parameter)
Important: Multipliers can be applied multiple times within the same request. Example: 
"body":{
  "wallets": [
    {"address":"0x123...", "connectionId": "ethereum"},
    {"address":"0x456...", "connectionId": "all"}
    ]
}
In this scenario, if the base credit is 4, the total credits will be calculated as follows:
  • Wallet 1: connectionId: "ethereum" → 4 × 1 = 4 credits
  • Wallet 2: connectionId: "all" → 4 × 10 = 40 credits
  • Total: 4 + 40 = 44 credits
Each wallet is processed independently with its own multiplier based on the connectionId value. Here’s a visual breakdown of how the system processes requests with multipliers:

​
Multiplier Values

Different parameters have different multiplier effects: (Base cost: 40 credits)
  • Query
  • 'all' value
  • Nested Body
When you provide multiple values (comma-separated or as arrays):
# Single network = base credits
?networks=ethereum

# Multiple networks = base credits × count
?networks=ethereum,polygon,binance_smart  # 3× multiplier

​
Cost Optimization Tips

🎯 Avoid 'all' Values When Possible

The "all" value applies a 10× multiplier. Be specific instead:
# ❌ Expensive (10× multiplier = 400 credits)
?connectionId=all

# ✅ Much cheaper (1× multiplier = 40 credits each)  
?connectionId=ethereum  # or specify only what you need
Savings: Using specific values instead of "all" can reduce costs by 90%

🔄 Understand Array Multipliers

Each item in arrays gets its own multiplier. Plan your requests accordingly:
// Example: Base cost = 40 credits
{
  "wallets": [
    {"address": "0x123...", "connectionId": "ethereum"},  // 40 × 1 = 40 credits
    {"address": "0x456...", "connectionId": "all"}        // 40 × 10 = 400 credits
  ]
}
// Total: 440 credits (not 80 credits!)
Key insight: Mixed multipliers within the same array can create unexpected costs.

⚡ Separate High-Cost Items

Consider splitting requests when mixing standard and high-multiplier values:
# ❌ Mixed request (440 credits total)
POST /endpoint
{
  "wallets": [
    {"connectionId": "ethereum", "address": "0x123..."},  // 40 credits
    {"connectionId": "all", "address": "0x123..."}        // 400 credits  
  ]
}

# ✅ Separate requests (80 credits total if you don't actually need "all")
POST /endpoint {"wallets": [{"connectionId": "ethereum", "address": "0x123..."}]}  // 40 credits
POST /endpoint {"wallets": [{"connectionId": "polygon", "address": "0x123..."}]}   // 40 credits

📊 Monitor Usage Patterns

Track your credit usage in the CoinStats API Dashboard to:
  • Identify unexpectedly expensive requests
  • Find patterns where "all" multipliers are driving costs
  • Optimize requests with high multiplier combinations

​
Frequently Asked Questions

Multipliers ensure fair pricing based on actual resource consumption. Requesting data for 1 wallet requires fewer resources than requesting data for 100 wallets, so the pricing reflects this difference.
Yes! Use endpoints with fixed pricing when possible, or make multiple smaller requests instead of one large request with many parameters.
No, only specific parameters on certain endpoints use multipliers. Check each endpoint’s documentation for details about which parameters are multiplied.
Your requests will be rejected with a 429 Too Many Requests error. You can upgrade your plan or wait for your credits to reset based on your plan’s terms.
Pro Tip: Start with smaller requests to understand costs, then optimize based on your actual usage patterns. The API dashboard provides detailed insights to help you optimize your credit usage.
Important: Always test with small parameter sets first to understand the credit impact before making large batch requests. Multipliers can significantly increase costs for large parameter sets.
⌘I