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:
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
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.

CU Pricing Tiers


WebSocket Real-time Subscription Billing

WebSocket real-time data subscriptions are billed separately, charged by data bytes:

Supported Subscription Channels

WebSocket Usage Estimation Examples

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.

Cost Estimation Examples

Scenario: A DeFi market website showing 50 token prices, refreshing every 10 seconds

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:
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.

Purchase Additional Quota

Paid plan users can purchase additional quota in Dashboard, priced according to the plan’s overage rate:
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

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.
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.

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