> For the complete documentation index, see [llms.txt](https://docs.novarpc.xyz/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.novarpc.xyz/nova-rpc/overview.md).

# Overview

**Enterprise Grade MEV Protection**

Nova is a SOC 2 compliant partner allowing transaction originators to consume public blockspace, without exposing transaction intent publicly to MEV bots and other market participants.

**The Perfect Fee for Inclusion**&#x20;

On Ethereum, every transaction competes in a blind auction for blockspace. **Mispriced inclusion destroys value** either through unnecessary overpayment or costly execution failure.<br>

* You don’t know the exact block composition
* You don’t know competing orderflow
* You don’t know builder behavior
* You don’t know short-term demand spikes

Nova minimizes execution uncertainty by dynamically optimising priority fees in real-time. Precision is the edge.

**Live on Ethereum, Base, Arbitrum, and BSC.**&#x20;

To start using Nova, simply switch out your existing RPC endpoint to the following:  `eth.novarpc.xyz`

&#x20;Please contact us at **<onboard@novarpc.xyz>** to start benefiting from MEV and gas refunds today.


---

# 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.novarpc.xyz/nova-rpc/overview.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.
