# Overview

The AEREDIUM RPC implements the full Ethereum JSON-RPC specification plus a small set of `aer_*` extensions for TEE attestations, ZK-STARK proofs, and Bitcoin anchoring.

If your client speaks Ethereum, it speaks AEREDIUM.

## Endpoints

| Transport  | URL                       |
| ---------- | ------------------------- |
| HTTPS POST | `https://rpc.aeredium.io` |
| WebSocket  | `wss://rpc.aeredium.io`   |

## Request format

Standard JSON-RPC 2.0:

```json
{ "jsonrpc": "2.0", "id": 1, "method": "eth_blockNumber", "params": [] }
```

Send a batch by posting an array of request objects:

```json
[
  { "jsonrpc": "2.0", "id": 1, "method": "eth_blockNumber", "params": [] },
  { "jsonrpc": "2.0", "id": 2, "method": "eth_chainId", "params": [] }
]
```

Responses come back in the same order in a JSON array.

## Method namespaces

| Namespace | Purpose                                                          | Reference                                                              |
| --------- | ---------------------------------------------------------------- | ---------------------------------------------------------------------- |
| `eth_*`   | Standard Ethereum methods                                        | [Ethereum methods](/developer.aeredium.io/json-rpc-api/ethereum.md)    |
| `net_*`   | Network status (`net_version`, `net_listening`, `net_peerCount`) | [Ethereum methods](/developer.aeredium.io/json-rpc-api/ethereum.md)    |
| `web3_*`  | Client info (`web3_clientVersion`, `web3_sha3`)                  | [Ethereum methods](/developer.aeredium.io/json-rpc-api/ethereum.md)    |
| `debug_*` | Tracing (`debug_traceTransaction`, `debug_traceCall`)            | [Ethereum methods](/developer.aeredium.io/json-rpc-api/ethereum.md)    |
| `aer_*`   | AEREDIUM extensions (TEE, ZK-STARK, Bitcoin anchoring)           | [AEREDIUM extensions](/developer.aeredium.io/json-rpc-api/aeredium.md) |

## Errors

Standard JSON-RPC error codes apply:

| Code     | Meaning                                                            |
| -------- | ------------------------------------------------------------------ |
| `-32700` | Parse error                                                        |
| `-32600` | Invalid request                                                    |
| `-32601` | Method not found                                                   |
| `-32602` | Invalid params                                                     |
| `-32603` | Internal error                                                     |
| `-32000` | Server error (e.g. nonce too low, insufficient funds, gas too low) |

Example:

```json
{ "jsonrpc": "2.0", "id": 1, "error": { "code": -32000, "message": "nonce too low" } }
```

## Rate limits

The public endpoint applies a token-bucket rate limit per IP. On exceeding it you'll get HTTP `429` with a `Retry-After` header. Methods are weighted — heavy methods (`eth_getLogs` over wide ranges, `debug_trace*`) cost more tokens than lightweight reads. For higher limits, request an API key and pass it via `X-API-Key`.

## Caching

The gateway caches deterministic responses (block lookups by hash, receipts, code, etc.) to reduce backend pressure. Mutating methods and `latest`-tag queries are never cached.


---

# 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://aeredium.gitbook.io/developer.aeredium.io/json-rpc-api/json-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.