API Overview

The CLOBr API provides programmatic access to market depth, liquidity data, and token scores for on-chain tokens.

Note: Premium membership is required to use the API.

Base URL

https://clobr.io/api/v1

API Access Tiers

CLOBr offers two API access tiers to meet different use cases:

Premium API

Included with Premium subscription

Includes:
  • ✓ 2,000,000 calls/month
  • ✓ Live market depth (60 requests/minute)
  • ✓ Single token score lookups - live
  • ✓ Top 50 tokens - live (CLOBr Top Scores)
  • ✓ DCA pressure rankings (6 requests/minute)
  • ✓ DCA orders with flow projections
  • ✓ Limit orders with price range filters

Perfect for trading bots, terminals, and personal automation

RECOMMENDED

Developer API

For apps and production workloads

From $99/month
10M calls a month and higher limits than Premium
Includes:
  • ✓ 10,000,000 calls/month
  • ✓ 3x the Premium rate limits on every endpoint
  • ✓ Real-time market depth (180 requests/minute)
  • ✓ Batch score queries (50 tokens)
  • ✓ DCA orders & limit orders
  • ✓ Advanced filtering options
  • ✓ Custom limits and quotas available
  • ✓ Dedicated support
Contact Sales

Multi-chain

The API covers Solana (solana), Robinhood Chain (robinhood), Base (base), Ethereum (ethereum) and HyperEVM (hyperevm), plus crypto majors by key (for example crypto:BTC on /market-depth and /replay). Every token object carries a chain field, and every endpoint takes an optional chain parameter. Address-keyed endpoints derive the chain from the address itself — a base58 mint is Solana, a 0x contract address is an EVM chain — so you never have to send it. List endpoints default to solana, which keeps every existing integration byte-for-byte unchanged; pass chain=all to opt in to the rest.

Full details in the Chains section of the endpoint reference, and the version history in the API changelog.

Rate Limits & Quotas

Premium: 2,000,000 calls per month. Developer: 10,000,000 calls per month. Each endpoint has its own rate limit, listed below.

EndpointPremium rate limitDeveloper rate limit
GET /market-depth/:address
rolling 60-second window
60 requests per minute180 requests per minute
GET /market-depth/bulk
up to 20 majors per call
6 requests per minute (bulk)30 requests per minute (bulk)
GET /score/:address1 request per second3 requests per second
POST /score (batch)
Developer only
Not available3 requests per second
GET /top-scores1 request per second3 requests per second
GET /dca-orders1 request per second3 requests per second
GET /limit-orders1 request per second3 requests per second
GET /whale-activity1 request per second3 requests per second
GET /dlmm/:address1 request per second3 requests per second
GET /dlmm-pools1 request per second3 requests per second
GET /lp-cheat-sheet1 request per second3 requests per second
GET /dca-pressure6 requests per minute30 requests per minute
POST /whale-activity (bulk)6 requests per minute (bulk)30 requests per minute (bulk)
GET /replay/:address
per API key, across all tokens
1 request per 10 seconds10 requests per second

Custom Developer limits: a Developer contract can set a custom rate limit (requests per minute) and a custom monthly quota. A custom rate limit applies only where it is higher than the Developer limit above; Replay always stays at 10 requests per second. A custom monthly quota is never below the Premium ,000,000 calls.

All API responses include headers for tracking usage:

  • X-RateLimit-Limit, X-RateLimit-Remaining, X-RateLimit-Reset
  • X-Quota-Limit, X-Quota-Used, X-Quota-Remaining, X-Quota-Reset
  • X-API-Tier (premium, or enterprise for the Developer tier) and X-API-Tier-Display (Premium or Developer)

Quick Links

Pro Tips

  • Developer users: Use the POST /score endpoint to batch query up to 50 tokens at once for maximum efficiency.
  • The /top-scores endpoint is perfect for discovering high-quality tokens ranked by liquidity.
  • Premium users: Get live depth chart data at 60 requests per minute. Use the /dca-orders and /limit-orders endpoints to feed trading bots and terminals.
  • Monitor your quota usage via the X-Quota-* response headers to avoid hitting limits.
API Overview | CLOBr Docs