MPPtempoquality 0.88

Pay-per-call blockchain JSON-RPC access across 80+ networks via MPP — no signup, no API keys.

Price
$1.00e-5 / call
Protocol
mpp
Verified
no

What it does

QuickNode's MPP endpoint provides pay-per-request blockchain JSON-RPC access powered by the Machine Payments Protocol. It proxies standard JSON-RPC calls to QuickNode's node infrastructure across a wide range of blockchains and networks including Ethereum, Solana, Bitcoin, Arbitrum, Base, Polygon, Avalanche, BSC, Optimism, Cosmos, Celestia, Near, Sui, Aptos, and many more — over 80 chains with both mainnet and testnet coverage.

Two payment intents are supported: "charge" (one-shot payment per call at $0.001) and "session" (payment channel at $0.00001 per call). Payment can be settled via Tempo (PathUSD or USDC.e on Tempo Testnet or Mainnet) or via Solana (USDC on Solana Mainnet, charge intent only). The endpoint URL pattern is `https://mpp.quicknode.com/session/{network}` for session-based calls or `https://mpp.quicknode.com/{network}` for charge-based calls. No API key or account signup is required — authentication is handled entirely through MPP micropayment credentials attached to each request.

The OpenAPI spec defines a full schema for every supported network. Tempo testnet wallets have a 10,000 lifetime request cap per intent. The request body is a standard JSON-RPC 2.0 payload (method, params, id). Responses include a Payment-Receipt header with the settlement transaction hash or channel ID.

Capabilities

json-rpc-proxymulti-chain-rpcpay-per-callsession-payment-channelmpp-tempo-settlementmpp-solana-settlementno-api-keyblockchain-node-access

Use cases

  • AI agents autonomously querying blockchain state (block numbers, balances, contract calls) without pre-provisioned API keys
  • Automated trading bots making on-chain reads across multiple chains with micropayment settlement
  • Backend services that need occasional RPC calls without committing to a subscription plan
  • Multi-chain indexers or analytics pipelines that pay per request at sub-cent costs
  • Prototyping and testing dApps against many networks with no signup friction

Fit

Best for

  • Agents needing keyless, pay-as-you-go blockchain RPC across 80+ chains
  • High-volume session-based RPC at $0.00001 per call
  • Multi-chain applications that want a single provider with uniform pricing

Not for

  • Use cases requiring WebSocket subscriptions or streaming event logs (only JSON-RPC POST is exposed)
  • Applications that need free-tier access with no payment at all
  • Workloads requiring custom QuickNode add-ons or marketplace plugins

Quick start

curl -X POST https://mpp.quicknode.com/session/ethereum-mainnet \
  -H 'Content-Type: application/json' \
  -H 'Authorization: Payment <mpp-credential>' \
  -d '{"jsonrpc":"2.0","method":"eth_blockNumber","params":[],"id":1}'

Example

Request

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

Response

{
  "id": 1,
  "result": "0x1234567",
  "jsonrpc": "2.0"
}

Endpoint

Transporthttp
Protocolmpp
CurrencypathUSD

Quality

0.88/ 1.00

Full OpenAPI 3.1 schema with detailed x-payment-info for every network, clear pricing, request/response examples, and well-defined 402/403 behavior. The probe returned 404 because HEAD/GET were used on a POST-only endpoint with a :network path param, but the schema and root_fetch_status 200 confirm the service is live. Docked slightly because no external docs were crawlable (all returned 'unsupported_network').

Warnings

  • Probe returned 404 because HEAD/GET were tried on a POST-only parameterized path; the endpoint is live per the OpenAPI spec and root 200 response.
  • Tempo testnet wallets have a 10,000 lifetime request cap per intent.
  • Session intent does not support Solana USDC settlement — only Tempo methods are available for sessions.
  • Crawled pages (/docs, /api, /pricing, /README) all returned 'unsupported_network' — no external documentation was retrievable.

Citations

Provenance

Indexed frommpp_dev
Enriched2026-04-19 16:06:34Z · anthropic/claude-opus-4.6 · v2
First seen2026-04-18
Last seen2026-04-22

Agent access