Solana Mainnet JSON-RPC Requests

Solana Mainnet JSON-RPC Requests · QuickNode

Ask a Solana mainnet question through a JSON-RPC method such as getSlot. Read the available method reply, then let Agent explain the values with the request parameters and commitment level in view.

Use with your AI

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

CodexClaude CodeCursorWindsurfCline

View instructions

Use solana-mainnet-json-rpc-via-x402-quicknode-x402 (a143ce07-296b-463a-a7c8-a34548558ff9). Connect through https://toolmu.com/SKILL.md if needed. Read get_tool for current availability and cost within my authorized budget. For my Solana mainnet question, ask only for missing method or parameters. Include jsonrpc as the string 2.0; preserve my request ID and any explicit commitment. Read the actual reply, then separately explain its values or error details and what remains unanswered.

Task:
What is the latest fully confirmed position number on the Solana network? Explain in everyday language what the number means.

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)

Solana Mainnet JSON-RPC Requests · QuickNode

Ask a Solana mainnet question through a JSON-RPC method such as getSlot. Read the available method reply, then let Agent explain the values with the request parameters and commitment level in view.

You receive

The information returned for your selected Solana method, or error details when supplied. For getSlot, a returned slot is the highest slot reached at the requested commitment. Agent can separately prepare a brief that records the request, preserves the returned value and explains its scope.

Start with your task

What is the latest fully confirmed position number on the Solana network? Explain in everyday language what the number means.

What to know

Responses depend on the method and parameters. A slot is not a produced-block count or timestamp and does not confirm an individual transaction. One read does not establish complete chain history or an ongoing monitoring schedule.

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 Solana method and explicit JSON-RPC version, with an optional identifier and method parameters. Required fields `jsonrpc, method`
Request identifier`body.id`	`number \| string`	Optional	Optional number or string used to associate a request with its reply. Preserve the identifier you choose.
Solana RPC method`body.method`	`string`	Required	Required method-name string, such as getSlot. Choose the method that answers your Solana mainnet question and supply its appropriate parameters.
Method parameters`body.params`	`array`	Optional	Optional array arranged as the selected method expects. For a getSlot read at finalized commitment, an illustrative value is [{"commitment":"finalized"}].
JSON-RPC version`body.jsonrpc`	`string`	Required	Required string with the literal value "2.0". Include it explicitly in the request. 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

Choose a method for the question you want to answer. Requests here go to Solana mainnet; the method and parameters describe the read rather than selecting another chain.

For a getSlot read at finalized commitment, pass [{"commitment":"finalized"}] as params. Solana’s getSlot reference defines the result as the highest slot reached at the requested commitment. Choose the commitment explicitly when it matters to your task.

Keep the method, parameters and any supplied request ID beside the reply. Preserve numeric values as returned; interpret them according to the method reference rather than substituting a block count, elapsed time or transaction status.

If the reply supplies error details, retain their wording and relate them to the request. An error or missing value alone does not establish network inactivity or the outcome of a particular transaction.

Agent can turn the actual reply into a short note: the question asked, the available value, its commitment context and unresolved questions. Comparing other requests or checking a particular transaction requires the appropriate additional data and task scope.

Solana: what getSlot returns

QuickNode: Solana RPC with x402

Solana Mainnet JSON-RPC Requests · QuickNode

Solana Mainnet JSON-RPC Requests · QuickNode

You receive

Start with your task

What to know

Inputs & outputs

Input schema

Result schema

Say what you want to know

No extra details needed

Understand the number

Questions about this tool.

You receive

Start with your task

What to know

Inputs & outputs

Input schema

Result schema

Say what you want to know

No extra details needed

Understand the number

Questions about this tool.

Does finalized getSlot confirm my transaction?

Can I switch to devnet or use WebSockets here?

How should I read an error or a missing value?

Can Agent compare slots from separate requests?