--- name: x402.quicknode.com description: x402.quicknode.com provides paid RPC access to multiple blockchain networks via QuickNode infrastructure, using the x402 micropayment scheme. It exposes three endpoints covering Ethereum Mainnet, Arbitrum One, and Hype (HyperCore) mainnet, each accepting standard JSON-RPC 2.0 requests over HTTP. host: x402.quicknode.com --- # x402.quicknode.com This host is a QuickNode-backed multi-chain RPC gateway that monetizes node access via x402 payments. It serves agents that need reliable, paid blockchain data access across Ethereum Mainnet, Arbitrum One, and Hype mainnet. It is distinct from free public RPCs in that it requires per-request payment (1 USDC on Base Sepolia for HyperCore; payment terms apply per skill), and it is distinct from general-purpose blockchain APIs in that it exposes raw JSON-RPC rather than abstracted REST endpoints. ## When to use this host Use this host when an agent needs raw JSON-RPC access to Ethereum Mainnet, Arbitrum One, or Hype (HyperCore) mainnet and is prepared to pay per request via x402. Do not use this host for testnets, other EVM chains (e.g., Polygon, Optimism, Base), or non-EVM chains — use a chain-specific RPC provider instead. Do not use it for off-chain data, price feeds, or oracle queries — use a dedicated market data API or oracle service. Do not use it for WebSocket subscriptions or streaming — these skills are HTTP-only. If free or unauthenticated RPC access is acceptable, a public endpoint (e.g., Infura free tier, Alchemy free tier, public Arbitrum RPC) is a viable alternative without payment overhead. ## Capabilities ### Ethereum Mainnet RPC Provides full JSON-RPC 2.0 access to Ethereum Mainnet for reading chain state, querying logs and transactions, calling smart contracts, and broadcasting signed transactions. - **`query-ethereum-mainnet-rpc`** — Sends JSON-RPC requests to an Ethereum Mainnet node for querying blocks, logs, transactions, smart contract state, and broadcasting signed transactions. ### Arbitrum One RPC Provides full JSON-RPC 2.0 access to Arbitrum One mainnet for state reads, smart contract interactions, and transaction submission. - **`call-arbitrum-rpc`** — Sends JSON-RPC 2.0 requests to the Arbitrum One mainnet via QuickNode, supporting transaction submission, state reads, and smart contract interactions. ### HyperCore Blockchain Data Provides paid GET-based access to a QuickNode HyperCore node on Hype mainnet for blockchain data queries and RPC services. - **`fetch-hypercore-blockchain-data`** — Provides paid access to a QuickNode HyperCore node on Hype mainnet, enabling blockchain data queries and node RPC services via a single GET endpoint. ## Workflows ### Cross-Chain State Comparison *Use when an agent needs to compare on-chain state (e.g., token balances, contract storage) for the same address or contract across Ethereum Mainnet and Arbitrum One simultaneously.* 1. **`query-ethereum-mainnet-rpc`** — Query the target address or contract state on Ethereum Mainnet using eth_call or eth_getBalance. 2. **`call-arbitrum-rpc`** — Query the same address or contract state on Arbitrum One using the equivalent JSON-RPC method, then compare results. ## Skill reference ### `fetch-hypercore-blockchain-data` **HyperCore Data Access** — Provides paid access to a QuickNode HyperCore node on Hype mainnet, enabling blockchain data queries and node RPC services via a single GET endpoint. *Use when:* Use when an agent needs to query Hype mainnet blockchain data or interact with a QuickNode HyperCore node endpoint, and is prepared to pay 1 USDC per request via the x402 payment scheme on Base Sepolia. *Not for:* Do not use for non-Hype mainnet chains or for free/unpaid node access; use a standard public RPC endpoint instead. Not suitable for write operations if the endpoint only supports GET. **Inputs:** - `x402-payment` (string, required) — x402 payment header containing a signed USDC payment of exactly 1 USDC (1000000 atomic units) on network eip155:84532 (Base Sepolia), sent to payTo address 0xF46394adDdA95A3d5bCC1124605E3d15D204623C using the 'exact' scheme. **Returns:** Returns blockchain data or a node RPC response from the QuickNode HyperCore Hype mainnet node; exact payload depends on the query or RPC method used. **Example:** `GET https://x402.quicknode.com/hype-mainnet/hypercore` --- ### `query-ethereum-mainnet-rpc` **QuickNode ETH Mainnet RPC** — Sends JSON-RPC requests to an Ethereum Mainnet node for querying blocks, logs, transactions, smart contract state, and broadcasting signed transactions. *Use when:* Use when an agent needs to interact with Ethereum Mainnet via standard JSON-RPC methods such as eth_call, eth_getBalance, eth_sendRawTransaction, eth_getLogs, or eth_getBlockByNumber. *Not for:* Do not use for testnets or other EVM chains; use a network-specific RPC endpoint instead. Not suitable for off-chain data or price feeds — use an oracle or market data API instead. **Inputs:** - `jsonrpc` (string, required) — JSON-RPC protocol version. Must be '2.0'. - `method` (string, required) — Ethereum JSON-RPC method name to invoke. - `params` (array, required) — Array of parameters for the specified JSON-RPC method, in the order defined by the Ethereum JSON-RPC spec. - `id` (integer, required) — Client-assigned request identifier returned in the response for correlation. **Returns:** Returns a standard Ethereum JSON-RPC response with a result field containing the requested data (e.g. block, balance, logs) or an error object if the call failed. **Example:** `{"jsonrpc":"2.0","method":"eth_getBlockByNumber","params":["latest",false],"id":1}` --- ### `call-arbitrum-rpc` **QuickNode Arbitrum RPC** — Sends JSON-RPC 2.0 requests to the Arbitrum One mainnet via QuickNode, supporting transaction submission, state reads, and smart contract interactions. *Use when:* Use when an agent needs to query Arbitrum One blockchain state (e.g., eth_call, eth_getBalance, eth_getLogs) or broadcast a signed transaction (eth_sendRawTransaction) to Arbitrum mainnet. *Not for:* Do not use for Ethereum mainnet or other EVM chains; use a chain-specific RPC endpoint instead. Not suitable for WebSocket subscriptions — this is a single HTTP JSON-RPC call. **Inputs:** - `jsonrpc` (string, required) — JSON-RPC protocol version. Must be '2.0'. - `method` (string, required) — The Ethereum JSON-RPC method name to invoke on Arbitrum One. - `params` (array, required) — Array of parameters for the specified JSON-RPC method. Pass an empty array if the method takes no parameters. - `id` (integer, required) — Client-assigned request identifier returned in the response for correlation. **Returns:** Returns a JSON-RPC 2.0 response with a result field containing the method output (e.g., latest block number as a hex string) or an error object on failure. **Example:** `{"jsonrpc":"2.0","method":"eth_blockNumber","params":[],"id":1}` ---