Skip to main content

Overview

ChainStream uses a Unit-based billing model. Different APIs consume different amounts of Units, and you can choose a plan that fits your business needs.

Billing Model

Plan Types

Free

$0 / month
  • 30K Units/month
  • No overage
  • For development, POC

Starter

$199 / month
  • 10M Units/month
  • Overage: $12.9/M
  • For small projects, MVP

Pro

$699 / month
  • 50M Units/month
  • Overage: $9.9/M
  • For production, medium traffic

Enterprise

$1,699 / month
  • 200M Units/month
  • Overage: $6.9/M
  • For large enterprises, high concurrency

Custom

Custom pricing
  • Custom Units quota
  • Custom overage rate
  • Private deployment, dedicated SLA
All plans will be blocked (return 403 error) when quota is exhausted. Paid plans can purchase additional quota in Dashboard to restore service.

Plan Selection Guide

Use cases:
  • Local development and debugging
  • Feature validation and demos
  • Learning and evaluating ChainStream API
Typical usage estimate:
  • 300 price queries per day → ~9,000 Units/month
Limitations:
  • Data may have 1-2 second delay
  • No SLA guarantee
  • Cannot continue calling after quota exhaustion
Use cases:
  • Individual developer’s small dApps
  • Trading bot prototypes
  • Small market display websites
Typical usage estimate:
  • Market dashboard (10 tokens, refresh every minute) → ~43,200 Units/month
  • Small trading bot (1 query/second) → ~86,400 Units/month (single token)
Example scenario: Building a Solana token market website showing 20 popular tokens, refreshing every 30 seconds:
20 tokens × 2 times/min × 60 min × 24 hours × 30 days = 1,728,000 requests
At 1 Unit/request = 1,728,000 Units/month
This scenario recommends Pro plan.
Use cases:
  • Small/medium exchange or wallet data needs
  • Professional trading tools
  • Businesses requiring KYT/KYA risk control
Typical usage estimate:
  • Medium market platform (100 tokens, real-time WebSocket) → ~500,000 Units/month
  • Deposit risk control (1000 KYT checks/day) → ~150,000 Units/month
Example scenario: Running a small exchange that needs:
  • Market data: 50 trading pairs, WebSocket real-time push
  • Deposit risk control: 500 deposits/day, each with KYT check
WebSocket: 50 × 0.1 Unit/message × 86400 sec × 30 days ≈ 12,960,000 messages = 1,296,000 Units
KYT: 500 × 5 Units × 30 days = 75,000 Units
Total: ~1,371,000 Units/month
This scenario recommends Pro plan + overage budget, or contact sales for Enterprise quote.
Use cases:
  • Large exchanges
  • Institutional quantitative trading
  • Private deployment or custom SLA requirements
Includes:
  • Unlimited API calls
  • Dedicated technical support
  • Custom SLA (99.99%+)
  • Optional private deployment
Contact sales for pricing.

Units Calculation

What is a Unit

Unit is ChainStream’s billing unit. Different APIs consume different amounts of Units - more complex APIs consume more.

Data API Consumption

Unit costs are tiered by computational complexity. Simple lookups cost less; aggregation-heavy and on-chain execution endpoints cost more.
APICUEndpoint
Token Search0.25GET /v2/token/search
Token Detail1.00GET /v2/token/{chain}/{tokenAddress}
Batch Detail0.75GET /v2/token/{chain}/multi
Token Metadata0.05GET /v2/token/{chain}/{tokenAddress}/metadata
Batch Metadata0.05GET /v2/token/{chain}/metadata/multi
Token Price0.10GET /v2/token/{chain}/{tokenAddress}/price
Price History0.10GET /v2/token/{chain}/{tokenAddress}/prices
Market Data0.10GET /v2/token/{chain}/{tokenAddress}/marketData
Batch Market Data0.10GET /v2/token/{chain}/marketData/multi
Token Stats2.50GET /v2/token/{chain}/{tokenAddress}/stats
Batch Stats2.50GET /v2/token/{chain}/stats/multi
Candles (OHLCV)0.25GET /v2/token/{chain}/{tokenAddress}/candles
Pair Candles0.25GET /v2/token/{chain}/pair/{pair}/candles
Pool Candles0.25GET /v2/token/{chain}/pool/{poolAddress}/candles
Holders0.50GET /v2/token/{chain}/{tokenAddress}/holders
Batch Holders0.50GET /v2/token/{chain}/{tokenAddress}/holders/multi
Top Holders0.50GET /v2/token/{chain}/{tokenAddress}/topHolders
Pools2.50GET /v2/token/{chain}/{tokenAddress}/pools
Security0.50GET /v2/token/{chain}/{tokenAddress}/security
Creation Info0.10GET /v2/token/{chain}/{tokenAddress}/creation
Mint/Burn0.50GET /v2/token/{chain}/{tokenAddress}/mintAndBurn
Traders by Tag0.50GET /v2/token/{chain}/{tokenAddress}/traders/{tag}
Liquidity Snapshots0.50GET /v2/token/{chain}/{tokenAddress}/liquiditySnapshots
Token List0.05GET /v2/token/{chain}/list
Dev Tokens0.50GET /v2/token/{chain}/dev/{devAddress}/tokens
Transfer Total0.25GET /v2/token/{chain}/{tokenAddress}/transfer-total
Transfers0.25GET /v2/token/{chain}/{tokenAddress}/transfers

CU Pricing Tiers

TierCU CostDescriptionExamples
Tier 10.05Metadata, list, simple lookupsToken list, blockchain info, webhook CRUD, job status
Tier 20.10Single-field queriesPrice, market data, creation info, gas price
Tier 30.25Search, trades, rankings, candlesToken search, OHLCV, trade activities, rankings
Tier 40.50Holders, security, snapshotsHolders, security audit, pool snapshots, top traders
Tier 51.00Full profile, PnL, net worthToken detail, wallet PnL, net worth
Tier 61.50Compute-heavy analyticsPnL details, calculate PnL
Tier 72.50Aggregation-heavyToken stats, pools (multi-source aggregation)
Tier 85.00On-chain executionSwap, token creation, send transaction

WebSocket Real-time Subscription Billing

WebSocket real-time data subscriptions are billed separately, charged by data bytes:
ItemRateDescription
WebSocket Data0.005 Unit/byteCharged by push data bytes
WebSocket ConnectionFreeNo charge for establishing connection
Heartbeat MessagesFreeHeartbeat packets not charged

Supported Subscription Channels

ChannelDescription
dex-candle:{chain}_{tokenAddress}_{resolution}Real-time candle data

WebSocket Usage Estimation Examples

Scenario: Monitor 10 tokens' real-time candles (1-minute resolution)

Calculation:
- Candle message ~200 bytes each
- Each token ~1 candle message per minute
- 10 tokens × 1 msg/min × 60 min × 24 hrs × 30 days = 432,000 messages
- Total data: 432,000 × 200 = 86,400,000 bytes
- Monthly: 86,400,000 × 0.005 = 432,000 Units

Scenario: Monitor 50 tokens' stats (real-time, ~1 update/second)

Calculation:
- Token stats message ~500 bytes each
- 50 tokens × 1 msg/sec × 86,400 sec × 30 days = 129,600,000 messages
- Total data: 129,600,000 × 500 = 64,800,000,000 bytes (~64.8 GB)
- Monthly: 64,800,000,000 × 0.005 = 324,000,000 Units (~324M)
Batch APIs typically have discounts. Refer to API Reference for exact consumption. WebSocket message frequency depends on market activity; high volatility periods will increase message volume.

KYT/KYA Service Billing

KYT/KYA APIs do not consume plan Units. They are charged from a separate KYT account balance (in USD). Please top up at Dashboard → KYT Service.
APICostEndpoint
Register Transfer$0.25/callPOST /v2/kyt/transfer
Register Withdrawal$0.25/callPOST /v2/kyt/withdrawal
Register Address$1.25/callPOST /v2/kyt/address
Query Risk / Alerts / ExposuresIncludedGET /v2/kyt/addresses/*/risk, GET /v2/kyt/transfers/*/summary, etc.

Cost Estimation Examples

Scenario: A DeFi market website showing 50 token prices, refreshing every 10 seconds
Calculation:
- Request frequency: 50 tokens × 6 times/min = 300 requests/min
- Monthly requests: 300 × 60 × 24 × 30 = 12,960,000 requests
- CU per request: 0.10 (Token Price endpoint)
- Monthly CU: 12,960,000 × 0.10 = 1,296,000 CU

Recommended: Starter plan (10M CU)

Quota Management

View Usage in Dashboard

1

Login to Dashboard

2

View Usage

Check current month usage, remaining quota, and historical trends on the Usage page

Quota Alert Settings

You can set quota alerts to receive notifications when usage reaches thresholds:
Alert LevelTrigger ConditionNotification Method
Reminder50% usageEmail
Warning80% usageEmail + Dashboard alert
Critical100% usageEmail + Dashboard alert
We recommend enabling at least the 80% alert to avoid unexpected service interruption.

Quota Exhaustion Handling

What Happens When Quota Runs Out

When monthly quota is exhausted, API will return 403 error and cannot continue to be called. Paid plan users can manually purchase additional quota to restore service.
PlanHandling Method
FreeAPI returns 403 error, wait for next month’s quota reset
Starter / Pro / EnterpriseAPI returns 403 error, can purchase additional quota to restore service
CustomPer contract terms

Purchase Additional Quota

Paid plan users can purchase additional quota in Dashboard, priced according to the plan’s overage rate:
PlanAdditional Quota Price
Starter$12.9 / 1M Units
Pro$9.9 / 1M Units
Enterprise$6.9 / 1M Units
Service is interrupted immediately when quota is exhausted (returns 403 error). We recommend setting 80% usage alerts and purchasing additional quota in advance to avoid business impact.

Payment Methods

Supported Payment Methods

MethodDescriptionApplicable Plans
Credit CardVisa, MasterCard, AMEXAll plans
CryptocurrencyUSDT, USDC (ERC-20 / TRC-20)Starter and above
Bank TransferContact salesEnterprise

Billing Cycle

  • Monthly plans: Invoice generated on the 1st for the previous month
  • Annual plans: Get 2 months free (equivalent to 16.7% discount)

AI Agent Payment (x402 / MPP)

For AI agents that need programmatic access without dashboard signup, ChainStream supports two on-chain payment protocols:

x402 (Base / Solana USDC)

The x402 protocol enables HTTP-native micropayments. When an API call returns 402, the agent’s wallet signs a USDC transfer and retries — no account registration required.
PropertyValue
NetworksBase (chain ID 8453), Solana
CurrencyUSDC
StandardEIP-3009 (Base), native transfer (Solana)
Gas FeeFree — ChainStream’s facilitator covers all gas costs
You only pay the subscription price in USDC. ChainStream operates its own x402 facilitator that submits the on-chain transaction and pays the gas fee on your behalf — the agent wallet does not need ETH or SOL for gas.

MPP (Tempo USDC.e)

MPP uses the Tempo network for payments. Gas is paid in USDC.e directly — no ETH needed.
PropertyValue
NetworkTempo (chain ID 4217)
CurrencyUSDC.e

How It Works

  1. Agent calls any ChainStream API
  2. Server returns 402 (no active subscription)
  3. Agent fetches available plans from /x402/pricing
  4. Agent purchases a plan via x402 or MPP
  5. Server returns an API Key — agent saves it for all future calls

x402 Payment Guide

Full details on x402 and MPP payment flows

FAQ

We recommend starting with the Free plan to evaluate actual usage, then choose based on monthly consumption:
  • < 30K Units: Free
  • 30K - 10M Units: Starter
  • 10M - 50M Units: Pro
  • > 50M Units: Enterprise
Yes. Upgrades take effect immediately with prorated charges. Downgrades take effect in the next billing cycle.
No. Monthly quotas reset at the end of each month and do not roll over.
Download historical invoices from Dashboard → Billing → Invoices. Enterprise customers can contact sales for custom invoices.

Next Steps

FAQ

Common questions

API Security

Understand API security configuration

API Reference

Start calling APIs