# RPC

## Overview

Chain.Love RPC offers three plans:

<table data-view="cards"><thead><tr><th></th><th></th><th></th><th data-hidden data-card-cover data-type="files"></th><th data-hidden data-card-target data-type="content-ref"></th></tr></thead><tbody><tr><td><strong>Free</strong></td><td>Free 10M Credits/month</td><td>For small projects and developers starting out.</td><td></td><td></td></tr><tr><td><strong>Growth</strong></td><td>Pay for requests</td><td>For dynamically scaling applications.</td><td></td><td></td></tr><tr><td><strong>Dedicated</strong></td><td>Pay for node hosting</td><td>For projects requiring exclusive access or customized configurations.</td><td></td><td></td></tr></tbody></table>

## Access Levels

### Unauthorized vs Free

For some blockchains we offer **public endpoints**, which do not require authorization, but have a **strict rate limit** of requests per minute.

In contrast, the **Free plan** grants access to the same endpoints at **no additional cost**, with **adjustable rate limits** and features such as **IP-based access control** and **Query key sharing** with collaborators.

### Growth vs Dedicated

The **Growth plan** and **Dedicated plan** differ in their pricing models:

* **Growth plan**: pay-per-use model, where you are charged for the number of [Credits](https://chain-love.gitbook.io/chain.loves-api-management-module/help-and-faq/glossary) used.
* **Dedicated plan**: fixed monthly fee for dedicated infrastructure hosting your node.

Growth plan is suitable for low to medium traffic projects, while Dedicated plan is more cost-effective for projects that make a lot of complex requests. Additionally, Growth plan may require an initial access fee for accessing archival data.

Dedicated plan provides dedicated infrastructure for optimal performance and reliability, with the option to request a specific node type or configuration. In contrast, Growth plan uses shared infrastructure with no configuration control.


---

# 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://chain-love.gitbook.io/chain.loves-api-management-module/billing/services-and-pricing/rpc.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.