Base Mainnet JSON-RPC Requests · QuickNode

Use with your AI

For tasks with several steps, continue in the AI you already use.

CodexClaude CodeCursorWindsurfCline

View instructions

Use quicknode-json-rpc-via-x402-quicknode-x402 (ec8bbff0-b3b2-46d8-a9b1-8c212a160f62). Connect through https://toolmu.com/SKILL.md if needed; read get_tool for current availability and cost within my authorized budget. Clarify only the method and parameters needed for my Base mainnet question. Include jsonrpc as the string 2.0 and preserve any request ID I supply. Read the actual reply, then separately explain its returned values or error information, keeping original values and any supplied block context visible.

Task:
What is the latest block number recorded on the Base blockchain? Explain it simply and show the original number.

Paste into your connected AI's conversation.

Connection guide

The final charge is based on confirmed usage. Unused reserved credits return to your available balance.

QuickNode (x402)

Base mainnet JSON-RPC requests · QuickNode (x402)

Call a JSON-RPC method on Base mainnet with its parameters. Read the method’s reply, then ask your Agent to explain the returned values or arrange them for your task.

You receive

Receive the available reply to your Base mainnet JSON-RPC request. Its content depends on the method and parameters and may contain returned values or an error. Your Agent can separately explain the reply and prepare a concise reading note.

Start with your task

What is the latest block number recorded on the Base blockchain? Explain it simply and show the original number.

What to know

This Tool targets Base mainnet. Method support and data coverage depend on the request; a reply alone does not establish complete historical coverage or a transaction’s final settlement.

Inputs & outputs

Inspect the current inputs, availability, and maximum charge before starting.

Input schema

Input schema
Field / Path	Type	Requirement	Meaning
JSON-RPC request`body`	`object`	Required	Required request payload containing the method name and JSON-RPC version, with an optional ID and parameters. Required fields `jsonrpc, method`
Request identifier`body.id`	`number \| string`	Optional	Optional number or string used to associate a reply with its request.
Base mainnet method`body.method`	`string`	Required	Required method-name string, for example eth_blockNumber or eth_call. Choose the method appropriate to your task and supply its parameters when needed.
Method parameters`body.params`	`array`	Optional	Optional array of parameters for the chosen method. Use values appropriate to that method.
JSON-RPC version`body.jsonrpc`	`string`	Required	Required literal string 2.0. Include this value explicitly. Fixed value `2.0`

View raw JSON

{
  "type": "object",
  "required": [
    "body"
  ],
  "properties": {
    "body": {
      "required": [
        "jsonrpc",
        "method"
      ],
      "properties": {
        "id": {
          "type": [
            "number",
            "string"
          ],
          "description": "Request identifier"
        },
        "method": {
          "type": "string",
          "description": "JSON-RPC method name (e.g., eth_blockNumber, eth_call)"
        },
        "params": {
          "type": "array",
          "description": "Method parameters"
        },
        "jsonrpc": {
          "type": "string",
          "const": "2.0"
        }
      }
    }
  },
  "additionalProperties": false
}

Result schema

Output fields have not been documented yet.

Additional notes

The target is Base mainnet. Choose a method that answers your question on that network; changing the method or its parameters does not select another blockchain.

QuickNode’s x402 guide illustrates eth_blockNumber on the Base mainnet route with JSON-RPC 2.0 and an empty params array. Other methods need parameters appropriate to their own operation. Use the method’s requirements rather than treating that empty array as a general default.

Keep the original returned value next to any explanation or conversion. Your Agent can make a reply easier to read, but that formatting is separate from the data supplied by the method.

If the reply contains an error, read that information before interpreting the request as successful. Review the method and parameters in light of the returned explanation; do not replace an error or missing value with an assumed chain value.

When your Agent compares replies, keep the method, parameters and any supplied block references associated with each reply. Interpretation and comparison are additional Agent work; a single request does not establish a historical series or set up ongoing monitoring.

QuickNode: x402 guide with a Base mainnet RPC example

Base mainnet JSON-RPC requests · QuickNode (x402)

Base mainnet JSON-RPC requests · QuickNode (x402)

You receive

Start with your task

What to know

Inputs & outputs

Input schema

Result schema

Write your question

Add a block number if needed

Read the answer

Questions about this tool.

You receive

Start with your task

What to know

Inputs & outputs

Input schema

Result schema

Write your question

Add a block number if needed

Read the answer

Questions about this tool.

Can I choose another blockchain with this Tool?

What does the request ID do?

How should I read an RPC error?

Does a reply prove that a transaction is complete?