Skip to main content

Overview

Moralis uses Compute Units (CUs) to track API usage. Rate limits ensure fair usage and system stability across all users.

Rate Limits by Plan

All plans include archive request support. For current plan pricing, see moralis.com/pricing.

Understanding Throughput

  • CUs Included - Total Compute Units available on your plan before overage applies. CU cost per method is listed on the RPC Pricing page.
  • API Throughput - Maximum requests per second across all your requests, evaluated over a rolling 4-second window. This limit is shared across all Moralis products. See Rate Limits.
  • Node Throughput - Maximum Compute Units per second on each individual RPC node, applied on top of your account-wide request rate.
  • Nodes - Number of dedicated node endpoints available

Avoiding Rate Limits

To stay within limits:
  1. Monitor your CU consumption in the Moralis Dashboard
  2. Keep your request rate below your plan’s throughput
  3. Implement exponential backoff for retries
  4. Cache responses when possible
  5. Use batch requests to reduce HTTP overhead (not CU cost)

Rate Limit Response

When rate limited, you’ll receive an HTTP 429 response:

Need Higher Limits?

Contact Moralis for Enterprise plans with custom limits tailored to your needs.