Skip to main content
All Moralis plans come with generous monthly request limits. The number of included requests depends on your plan - see the product pricing page for details. Moralis uses Compute Units (CUs) as a standard way to measure and bill for usage across all products - including Data API, Streams, and RPC Nodes. CUs provide a unified way to account for computational complexity across every product, so usage is metered consistently regardless of which product you’re using.

​
Plan Overview

Prices shown are for monthly billing. Annual billing is also available - see the pricing page for current rates.

​
What is a Compute Unit?

A Compute Unit (CU) represents the relative computational cost of a request, task, or operation within the Moralis platform. Simple operations consume fewer CUs, while more complex or resource-intensive ones consume more. For example:
  • A basic wallet balance check may consume a small number of CUs.
  • A multi-chain portfolio aggregation, or a high-frequency stream of on-chain events, may consume significantly more.
CUs ensure you’re only billed for the resources you actually use - and that high-load workloads are fairly metered across the system.

​
CU Cost

Each product applies CU-based billing differently. Generally:
  • CUs are deducted from your plan’s included quota.
  • Usage beyond your quota is billed as overage, at the per-million rate for your plan.

​
Overage Rates

Overage applies once you exceed the CUs included in your plan. Higher plans carry a lower per-million rate, so sustained overage is usually a signal to upgrade. Visit the individual pricing pages to see how CUs apply to each product:

​
Dynamic Endpoints

Some API endpoints have dynamic CU costs that scale based on the scope of the request. Instead of a fixed cost per call, these endpoints charge a base CU amount multiplied by a variable factor such as the number of chains, wallets, or addresses involved. For example:
  • An endpoint costing 50 CUs per chain that queries 3 chains will consume 150 CUs total.
  • An endpoint costing 250 CUs per chain that queries 5 chains will consume 1,250 CUs total.
Dynamic endpoints are clearly marked on their respective documentation pages. You can find CU costs for all endpoints on the individual product pricing pages listed above.

​
RPS Throughput

Rate limits are enforced as requests per second (RPS), separately from CU consumption. CUs meter how much you use, RPS caps how fast you can call. Each plan defines a maximum request rate, evaluated over a rolling 4-second window. This allows short bursts as long as your total request count stays within the limit across that window. Exceeding it returns a 429 Too Many Requests response. See Rate Limits for the full breakdown. Different products may apply throughput differently. Check the respective documentation for details.