Agentic Portal

NEAR JSON-RPC

blockchain
Serving

Read-only JSON-RPC access to NEAR Protocol mainnet, served by the Pocket Network decentralised supplier set. Pay per request in USDC; no account, no API key.

Endpoint
POST https://agent.pocket.network/v1/near
Price per call
$0.005 USD
Networks payable on
Base (eip155:8453)
Protocol
jsonrpc

Calling it

The first call returns 402 Payment Required with the terms. Sign for those terms and retry the same request with the payment attached.

Example request

Derived from the published request schema.

curl -X POST https://agent.pocket.network/v1/near \
  -H 'content-type: application/json' \
  -d '{"method":"EXPERIMENTAL_changes","params":null}'
Example response

Derived from the published response schema.

{
  "jsonrpc": "2.0",
  "id": "dontcare",
  "result": {
    "gas_price": "100000000"
  }
}

Try it

Make one real paid call from your own wallet — about $0.005 on Base (eip155:8453). The wallet signs; nothing here holds a key. You'll see exactly what the service answers.

No browser wallet found. Install MetaMask, Rabby, or Coinbase Wallet to try a call here.

Supported methods

Methods the registry lists for this service. The portal forwards any call as sent; the supplier decides what it answers, and a delivered answer is settled.

Methods NEAR JSON-RPC accepts, and whether each reads or writes.
MethodEffect
EXPERIMENTAL_changesread
EXPERIMENTAL_changes_in_blockread
EXPERIMENTAL_congestion_levelread
EXPERIMENTAL_genesis_configread
EXPERIMENTAL_light_client_block_proofread
EXPERIMENTAL_light_client_proofread
EXPERIMENTAL_maintenance_windowsread
EXPERIMENTAL_protocol_configread
EXPERIMENTAL_receiptread
EXPERIMENTAL_split_storage_inforead
EXPERIMENTAL_tx_statusread
EXPERIMENTAL_validators_orderedread
blockread
changesread
chunkread
client_configread
gas_priceread
genesis_configread
healthread
light_client_proofread
maintenance_windowsread
network_inforead
next_light_client_blockread
queryread
statusread
txread
validatorsread

Schemas

Published by the service itself. The example above is generated from these.

Request schema
{
  "type": "object",
  "properties": {
    "method": {
      "type": "string",
      "description": "JSON-RPC read method, e.g. query",
      "examples": [
        "EXPERIMENTAL_changes",
        "EXPERIMENTAL_changes_in_block",
        "EXPERIMENTAL_congestion_level",
        "EXPERIMENTAL_genesis_config",
        "EXPERIMENTAL_light_client_block_proof",
        "EXPERIMENTAL_light_client_proof",
        "EXPERIMENTAL_maintenance_windows",
        "EXPERIMENTAL_protocol_config",
        "EXPERIMENTAL_receipt",
        "EXPERIMENTAL_split_storage_info",
        "EXPERIMENTAL_tx_status",
        "EXPERIMENTAL_validators_ordered",
        "block",
        "changes",
        "chunk",
        "client_config",
        "gas_price",
        "genesis_config",
        "health",
        "light_client_proof",
        "maintenance_windows",
        "network_info",
        "next_light_client_block",
        "query",
        "status",
        "tx",
        "validators"
      ]
    },
    "params": {
      "description": "Parameters per the NEAR RPC spec (positional or named)"
    }
  },
  "required": [
    "method"
  ]
}
Response schema
{
  "type": "object",
  "description": "JSON-RPC 2.0 response envelope. Exactly one of `result` or `error` is present. `result` takes the shape the called method defines per the NEAR RPC specification; NEAR conventionally echoes a string id.",
  "properties": {
    "jsonrpc": {
      "type": "string",
      "description": "The protocol version, always \"2.0\""
    },
    "id": {
      "type": [
        "string",
        "number",
        "null"
      ],
      "description": "The request id, echoed back"
    },
    "result": {
      "description": "The method's result, in the shape the called method defines. Present when the call succeeded; absent when `error` is."
    },
    "error": {
      "type": "object",
      "description": "Present instead of `result` when the call failed",
      "properties": {
        "code": {
          "type": "integer",
          "description": "A JSON-RPC 2.0 error code"
        },
        "message": {
          "type": "string"
        },
        "data": {
          "description": "Method-specific detail, when the node supplies it"
        }
      }
    }
  },
  "examples": [
    {
      "jsonrpc": "2.0",
      "id": "dontcare",
      "result": {
        "gas_price": "100000000"
      }
    }
  ]
}

Request body used in the example: { "method": "EXPERIMENTAL_changes", "params": null }