# What's CUs/CUPS

### CU

Compute Unit serves as a metric for tracking your RPC request usage. Users are allotted a monthly usage quota, and each method incurs a cost corresponding to the resources needed for execution. Conceptualize this as maintaining a balance in your account, with each method having its own individual price. 

Upon submission of RPC requests, the applicable cost is deducted from your account. This cost is denoted as the Compute Unit price for each RPC method. Through this approach, we empower our users to optimize their monthly request quota more effectively.

In essence, you are solely charged for your actual usage.

## CUs of RPC Method

Below are the CUs for each method. We define the CUs based on the resource required for execution.

### Supported Method

#### **BSC, Ethereum, Polygon, Optimism, opBNB**

| Method                                   | CUs  |
| ---------------------------------------- | ---- |
| eth\_accounts                            | 5    |
| eth\_blockNumber                         | 5    |
| eth\_chainId                             | 5    |
| eth\_syncing                             | 5    |
| net\_listening                           | 5    |
| net\_version                             | 5    |
| web3\_clientVersion                      | 5    |
| eth\_subscribe                           | 10   |
| eth\_uninstallFilter                     | 10   |
| eth\_unsubscribe                         | 10   |
| web3\_sha3                               | 10   |
| eth\_signTransaction                     | 10   |
| net\_peerCount                           | 10   |
| eth\_gasPrice                            | 15   |
| eth\_getBalance                          | 15   |
| eth\_getBlockByNumber                    | 15   |
| eth\_getCode                             | 15   |
| eth\_getStorageAt                        | 15   |
| eth\_getTransactionByBlockHashAndIndex   | 15   |
| eth\_getTransactionByBlockNumberAndIndex | 15   |
| eth\_getTransactionByHash                | 15   |
| eth\_getTransactionReceipt               | 15   |
| eth\_getBlockByHash                      | 18   |
| eth\_getBlockTransactionCountByHash      | 18   |
| eth\_getBlockTransactionCountByNumber    | 18   |
| eth\_getFilterChanges                    | 18   |
| eth\_newBlockFilter                      | 18   |
| eth\_newFilter                           | 18   |
| eth\_newPendingTransactionFilter         | 18   |
| eth\_call                                | 20   |
| eth\_getTransactionCount                 | 25   |
| eth\_getFilterLogs                       | 50   |
| eth\_getLogs                             | 50   |
| eth\_estimateGas                         | 75   |
| eth\_sendRawTransaction                  | 150  |
| debug\_traceTransaction                  | 280  |
| debug\_traceCall                         | 280  |
| debug\_traceBlockByNumber                | 1800 |
| debug\_traceBlockByHash                  | 1800 |

#### **Ethereum only**

| Method                             | CUs |
| ---------------------------------- | --- |
| eth\_protocolVersion               | 5   |
| eth\_createAccessList              | 10  |
| eth\_feeHistory                    | 10  |
| eth\_maxPriorityFeePerGas          | 10  |
| eth\_getUncleByBlockHashAndIndex   | 15  |
| eth\_getUncleByBlockNumberAndIndex | 15  |
| eth\_getUncleCountByBlockHash      | 15  |
| eth\_getUncleCountByBlockNumber    | 15  |

#### **Polygon API**

| Method                             | CUs |
| ---------------------------------- | --- |
| bor\_getAuthor                     | 15  |
| bor\_getCurrentProposer            | 15  |
| bor\_getCurrentValidators          | 15  |
| bor\_getRootHash                   | 15  |
| bor\_getSignersAtHash              | 15  |
| eth\_getTransactionReceiptsByBlock | 250 |

## CUPS (Rate Limit)

The Compute Unit Per Second (CUPS) indicates the amount of CU consumed per second during requests. Each RPC method carries a distinct weight, ensuring more efficient calculations than simply tallying the number of requests sent within a second across different use cases.

See below the CUPS for different tiers of users:

| Key Type      | CUPS |
| ------------- | ---- |
| Free Key      | 150  |
| Pay As You Go | 1000 |

{% hint style="info" %}
If you have any questions, please join our [Discord server](https://discord.com/invite/Cun2VpsdjF), or send us an email at <contact@4everland.org>.
{% endhint %}


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.4everland.org/rpc/whats-cus-cups.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.