# RPC Service

bloXroute RPC services offer a wide range of functionality tailored to different user needs — from protecting transactions against MEV attacks to optimizing for fast inclusion and reliable data access. Instead of broadcasting transactions through the public mempool, bloXroute routes them through a private, high-performance relay network.

When using a standard RPC, transactions are broadcast across peer‑to‑peer nodes and become immediately visible to MEV bots. This exposure opens the door to frontrunning, sandwiching, and other value-extracting behaviors that degrade execution quality.

bloXroute RPC keeps transactions private until they are ready for inclusion in a block, significantly reducing the risk of MEV exploitation and improving the performance of latency-sensitive workflows.

bloXroute currently offers three types of RPC endpoints, each designed for a specific use case:

| RPC Type            | Description                                                                                                   |
| ------------------- | ------------------------------------------------------------------------------------------------------------- |
| **Protect RPC**     | Protects transactions from frontrunning and sandwich attacks by keeping them private until included on-chain. |
| **Gas Protect RPC** | Adds gas-revert protection using Flashbots bundles, preventing wasted gas on failed transactions.             |
| **Fast RPC**        | Optimized for fast landing and block inclusion in latency-sensitive workflows.                                |


---

# 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.bloxroute.com/core-solutions/rpc-service.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.