Skip to main content

​
Compute Unit (CU) Pricing Model

BlockDB uses a Compute Unit (CU) pricing model that charges based on the computational complexity of each API endpoint. This ensures you only pay for what you use, without being forced into expensive plans for simple queries.

​
How Compute Units Work

Each API request consumes a certain number of Compute Units based on the dataset level and endpoint complexity:
Dataset LevelEndpoint FamilyCompute Units (CU)Examples
00xxReference & Catalog1 CUPrice catalog discovery, enumerations
01xxLedger & Execution1 CUBlocks, Transactions, Logs, Contracts, Function Results
02xxTokens & Pools2 CUERC-20 tokens, ERC-721 tokens, Pools
03xxReserves3 CUPool reserves snapshots
04xxPricing Layers4 CUCatalog, Depth, Impact Grid, OHLC
05xxPricing Analytics5 CUVWAP, LWAP calculations
LineageData Provenance1 CULineage record, genesis, parents
VerificationIntegrity Checks1 CUReceipt root, logs bloom verification
CU consumption is calculated per request. Pagination and result size do not affect CU costs—only the endpoint type determines the CU value.

​
CU Billing & Tracking

​
How CU Consumption is Tracked

Query the GET /usage endpoint to retrieve your current CU consumption, remaining quota, and detailed usage statistics. This endpoint is free to use and does not consume Compute Units.
The /usage endpoint provides comprehensive usage data including consumption by dataset, billing period information, and rate limits.

​
Monthly CU Allowances

Plans include monthly CU allowances that reset each billing cycle:
  • Testing Plan: Base CU allowance for development and testing
  • Production Plan: Higher CU allowance for production workloads
  • Enterprise Plan: Custom CU allowances tailored to your needs
CU consumption is tracked per API key. You can distribute your total CU allowance across multiple API keys for different applications or environments.

​
Overage Handling

When you exceed your monthly CU allowance:
  • Hard limits: API requests are blocked once your CU allowance is exhausted
  • Additional packages: Purchase additional CU packages to continue using the API
  • No automatic overage charges: You control when to purchase additional CUs—no unexpected charges
  • Package options: Additional CU packages are available in various sizes to match your needs
Monitor your CU consumption through the GET /usage endpoint or the BlockDB Admin Panel to plan ahead and purchase additional packages before reaching your limit.
Once your CU allowance is exhausted, API requests will return 429 Too Many Requests until you purchase an additional CU package. Plan your usage accordingly to avoid service interruptions.

​
Pricing Examples

​
Example 1: Simple Block Query

Request: POST /evm/blocks (query latest block)
CU Cost: 1 CU

​
Example 2: Token Price Analysis

Request: POST /evm/prices/spot/fiat/vwap (1-hour window)
CU Cost: 5 CU

​
Example 3: Complex Analysis Workflow

- POST /evm/blocks (find block range) → 1 CU
- POST /evm/logs (filter events) → 1 CU
- POST /evm/prices/spot/fiat/ohlc (get OHLC) → 4 CU
Total: 6 CU
The CU model ensures you pay proportionally to the computational cost of each request. Simple lookups cost less than complex analytics, making it economical to use BlockDB for both simple and advanced use cases.

​
See Also