> ## Documentation Index
> Fetch the complete documentation index at: https://docs.moralis.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Pricing

> Pricing information about our products.

All Moralis plans come with generous monthly request limits. The number of included requests depends on your plan - check the [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](/data-api/overview), [Streams](/streams/overview), [Datashare](/datashare/overview), and [RPC Nodes](/rpc-nodes/overview).

CUs provide a unified way to account for **computational complexity** and **rate limits**, regardless of the product you're using.

## 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 may incur overage charges**, depending on your plan and product.

Visit the individual pricing pages to see how CUs apply to each product:

* [Data API Pricing](/data-api/pricing)
* [Streams Pricing](/streams/pricing)
* [Datashare Pricing](#)
* [Nodes Pricing](/rpc-nodes/pricing)

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

## CU Throughput (CU/s)

CUs are also used to enforce **rate limits**, measured in **CUs per second (CU/s)**.

This helps manage request throughput and protect system performance - allowing heavier requests to be made less frequently, while lightweight calls remain fast and responsive.

Different products may enforce CU/s limits differently. Check the respective documentation for details.