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

# JSON-RPC

MegaETH JSON-RPC endpoints, shared protocol conventions, operational limits, and method reference.

MegaETH exposes Ethereum-compatible JSON-RPC over HTTP and WebSocket, with additional methods and real-time behavior. Start with the shared guides below, then use the RPC Reference for individual method contracts.

## Get started

* [Quickstart](/developer-docs/rpc/quickstart.md) — make a read-only request and verify the connected network.
* [JSON-RPC basics](/developer-docs/rpc/json-rpc-basics.md) — request envelopes, notifications, batches, and response handling.
* [Type reference](/developer-docs/rpc/types.md) — hexadecimal quantities, byte strings, addresses, hashes, and selectors.
* [Error reference](/developer-docs/rpc/error-codes.md) — standard, Ethereum, MegaETH, and public-gateway errors.
* [Operations and limits](/developer-docs/rpc/operations-and-limits.md) — rate limits, payload caps, caching, and WebSocket limits.

## RPC Reference

Use the [RPC Reference](/developer-docs/rpc/reference.md) for method availability and individual request, response, error, and example documentation.


---

# 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.megaeth.com/developer-docs/rpc.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.