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

# RPC addon

> Use SQD Cloud's built-in RPC proxy as a managed RPC source for squid processors — bundled rate limits, supported networks, and configuration options.

[List of available networks](/en/cloud/reference/rpc-proxy-networks) and their aliases is available on the reference page.

SQD Cloud provides a built-in RPC service. The service is available as an addon to all squids deployed to the Cloud, although [playground](/en/cloud/resources/organizations/#playgrounds) squids only have access to a limited number of calls.

[Professional organizations](/en/cloud/resources/organizations/#professional-organizations) do not have that limitation and [can access](#external-access) their RPC endpoints from outside of the Cloud.

Enable the RPC add-on in the [manifest](/en/cloud/reference/manifest) like this:

```yaml theme={"system"}
deploy:
  addons:
    rpc:
      - eth-goerli.http
```

## Processor configuration

With the add-on successfully enabled, your squid will get a unique proxied endpoint to the requested network. SQD Cloud will make its URL available to the deployed squid at the `RPC_$\{Upper(network)\}_$\{Upper(protocol)\}` environment variable. Assert it to avoid compilation errors. We also recommend rate limiting RPC addon requests on the processor side to the same rate as was used in the manifest:

```typescript theme={"system"}
import \{assertNotNull\} from '@subsquid/util-internal'

processor.setRpcEndpoint({
  // dash in "eth-goerli" becomes an underscore
  url: assertNotNull(process.env.RPC_ETH_GOERLI_HTTP),
  rateLimit: 10
})
```

## External access

[Professional organizations](/en/cloud/resources/organizations/#professional-organizations) can [access their RPC proxies from outside](https://app.subsquid.io/rpc) of the SQD Cloud.

Among other things, this enables a development process that uses the service for both local and Cloud runs transparently. Here an example configuration for Ethereum Mainnet:

<details>
  <summary>Here is an example configuration for Ethereum Mainnet</summary>

  1. Add the following variable to `.env`:
     ```bash theme={"system"}
     # get the url from https://app.subsquid.io/rpc/chains/eth
     RPC_ETH_HTTP=<your_rpc_url_for_external_use>
     ```

  2. Enable the RPC addon in squid.yaml:
     ```yaml theme={"system"}
     deploy:
       addons:
         rpc:
           - eth.http
     ```
     This will add and populate the `RPC_ETH_HTTP` variable for Cloud deployments.

  3. Configure the processor to use the URL from `RPC_ETH_HTTP`:
     ```typescript theme={"system"}
     import \{EvmBatchProcessor\} from '@subsquid/evm-processor'
     import \{assertNotNull\} from '@subsquid/util-internal'

     export const processor = new EvmBatchProcessor()
       .setRpcEndpoint(assertNotNull(process.env.RPC_ETH_HTTP))
       // ...the rest of the processor configuration
     ```
</details>

## Pricing

RPC addon requests are priced [at a flat rate](/en/cloud/pricing/#rpc-requests), with substantial packages included for free for all [organization types](/en/cloud/resources/organizations). Pricing does not depend on the call method.

**Current Pricing (Until March 31, 2026):**

* Free tier: 2M requests/month
* Overage: \$2.00 per 1M requests

**New Pricing (From April 1, 2026):**

* Free tier: 2M requests/month (unchanged)
* Overage: \$5.00 per 1M requests

See the [pricing announcement](/en/other/pricing-update-april-2026) for more details about upcoming changes.