> For the complete documentation index, see [llms.txt](https://docs.rpcfast.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.rpcfast.com/rpc-fast-saas-evm/introduction.md).

# Introduction

Blockchains: Ethereum, Base, Polygon, BSC, Arbitrum.

## **RPC Fast API Access**

The RPC Fast API gives instant access over HTTPS and WebSockets to **Ethereum** and a few selected EVM blockchains, such as **Base, BSC, Arbitrum,** and **Polygon**.

We provide a high level of security, stable connection, and an intuitive control panel.

* **Standard Interface:** Get access to our JSON-RPC endpoint and 100% healthy nodes on production.
* **Stable Connection:** Geo-distributed infrastructure makes it run smoothly without harming the UX. The software updates automatically and saves your time.
* **High-level Security:** JSON Web Token application is available for the Enterprise plan. The architecture is error-proofed and consistent. Great for smart contracts.
* **Auto-scaling Infrastructure:** AI-based PredictKube mechanism autoscales the node pool to get your project ready for any traffic amount.
* **Control Panel:** RPC Fast dashboard is intuitive. Here you will find automatically-built reports about your blockchain hosting state.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

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

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.rpcfast.com/rpc-fast-saas-evm/introduction.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.