RPCFast
Main PageChainsPricingBlog
  • Welcome to RPC Fast
  • 🐇RPC Fast API
    • Introduction
    • Getting Started
    • Pricing Plan
    • Growth Plan
    • Compute Units (CUs)
    • CUPS (Rate Limit)
    • Archive Node
    • JSON Web Token (JWT)
    • Ethereum API
      • eth_accounts - Ethereum
      • eth_blockNumber - Ethereum
      • eth_call - Ethereum
      • eth_chainId - Ethereum
      • eth_estimateGas - Ethereum
      • eth_gasPrice - Ethereum
      • eth_getBalance - Ethereum
      • eth_getBlockByHash - Ethereum
      • eth_getBlockByNumber - Ethereum
      • eth_getBlockTransactionCountByHash - Ethereum
      • eth_getBlockTransactionCountByNumber - Ethereum
      • eth_getCode - Ethereum
      • eth_getFilterChanges - Ethereum
      • eth_getFilterLogs - Ethereum
      • eth_getLogs - Ethereum
      • eth_getProof - Ethereum
      • eth_getStorageAt - Ethereum
      • eth_getTransactionByBlockHashAndIndex - Ethereum
      • eth_getTransactionByBlockNumberAndIndex - Ethereum
      • eth_getTransactionByHash - Ethereum
      • eth_getTransactionCount - Ethereum
      • eth_getTransactionReceipt - Ethereum
      • eth_getUncleByBlockHashAndIndex - Ethereum
      • eth_getUncleByBlockNumberAndIndex - Ethereum
      • eth_getUncleCountByBlockNumber - Ethereum
      • eth_getUncleCountByBlockHash - Ethereum
      • eth_newBlockFilter - Ethereum
      • eth_newFilter - Ethereum
      • eth_newPendingTransactionFilter - Ethereum
      • eth_sendRawTransaction - Ethereum
      • eth_subscribe - Ethereum
      • eth_syncing - Ethereum
      • eth_uninstallFilter - Ethereum
      • eth_unsubscribe - Ethereum
      • net_listening - Ethereum
      • net_version - Ethereum
      • web3_clientVersion - Ethereum
      • web3_sha3 - Ethereum
    • Yellowstone gRPC
    • Solana node benefits
  • Solana Trader API
    • Websocket endpoints
  • 🧩GUIDES
    • Intro
    • How to Add RPC Fast Endpoints to MetaMask
    • How to Add Polygon to MetaMask
    • How to check Solana RPC latency
  • Community
  • Use of Cookies
  • Support
  • Transaction Simulation
Powered by GitBook
On this page
  • How CUPS Works and Why We Use It as Rate Limit
  • What Is CUPS?
  • Why Do We Apply Rate Limits?
  1. RPC Fast API

CUPS (Rate Limit)

We count Compute Units per second instead of counting requests. It is our way to achieve stable connection and keep costs low without affecting the UX

How CUPS Works and Why We Use It as Rate Limit

What Is CUPS?

The way of measuring CUs we apply is called CUPS (Compute Unit Per Second). CUPS helps us to measure the rate limit and implement suitable algorithms. As we explained in the Compute Units article, each method costs a different number of CUs. It makes the CUPS limitation system more efficient than counting requests per second. There are various limitations to different pricing plans.

Why Do We Apply Rate Limits?

They allow us to ensure that clients use our services fairly and make connections stable and sustainable. We set speed limitations per second. For example, if the API returns the ‘rate limits error’ during retries, it will handle your request the next second. In general, it ultimately doesn’t affect the UX but makes the service accessible for everyone.

PreviousCompute Units (CUs)NextArchive Node

Last updated 2 years ago

🐇