MPPtempoquality 0.88

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

Price
$0.001 / call
Protocol
mpp
Verified
no
Endpoint
https://mpp.quicknode.com/:network

What it does

QuickNode's MPP endpoint provides pay-per-request blockchain RPC access using the Machine Payments Protocol. Agents can send standard JSON-RPC calls to any of 140+ supported networks (Ethereum, Solana, Bitcoin, Arbitrum, Base, Polygon, Avalanche, Cosmos, Celestia, and many more) by simply attaching an MPP payment credential. No account signup or API key provisioning is required — authentication is handled entirely through micropayments.

Two payment intents are available per network: "charge" for one-shot per-call payments at $0.001 per request, and "session" for payment-channel-based access at $0.00001 per request. Payment can be settled via PathUSD or USDC.e on Tempo (testnet and mainnet), or via USDC on Solana Mainnet. Each network is exposed at its own path (e.g., `/ethereum-mainnet`, `/solana-mainnet`, `/arbitrum-mainnet`), and session variants are available under `/session/<network>`. Tempo testnet wallets have a 10,000 lifetime request cap per intent.

The endpoint accepts standard JSON-RPC 2.0 request bodies (fields: `jsonrpc`, `method`, `params`, `id`) and returns the upstream node's JSON-RPC response along with a `Payment-Receipt` header. The OpenAPI spec covers all networks with identical request/response schemas, making integration straightforward for any agent that speaks JSON-RPC.

Capabilities

json-rpc-proxymulti-chain-rpcpay-per-callpayment-channel-sessionmpp-chargempp-sessionethereum-rpcsolana-rpcbitcoin-rpcevm-compatiblecosmos-rpcnear-rpcaptos-rpcsui-rpc

Use cases

  • —AI agents querying on-chain data (balances, block numbers, transaction receipts) without managing API keys
  • —Automated smart contract interaction via eth_call or sendRawTransaction with per-call billing
  • —Multi-chain indexing bots that need RPC access across dozens of networks at micropayment granularity
  • —Session-based high-throughput data pipelines using payment channels at $0.00001/call
  • —Serverless functions that need ad-hoc blockchain reads without provisioning infrastructure

Fit

Best for

  • —Agents needing signupless, wallet-authenticated blockchain RPC access
  • —Multi-chain applications that want a single provider for 140+ networks
  • —High-volume session-based workloads at $0.00001 per call via payment channels

Not for

  • —Applications requiring WebSocket subscriptions or streaming event logs (only HTTP JSON-RPC is documented)
  • —Users who need free-tier or fiat-billed RPC without a crypto wallet

Quick start

curl -X POST https://mpp.quicknode.com/ethereum-mainnet \
  -H 'Content-Type: application/json' \
  -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

URLhttps://mpp.quicknode.com/:network
Transporthttp
Protocolmpp
CurrencypathUSD

Quality

0.88/ 1.00

Full OpenAPI 3.1 spec with clear pricing, request/response schemas, and examples for all 140+ network routes. The 402 challenge was not captured directly (probe hit the root path which returns 404/unsupported_network, not a network-specific route), but the OpenAPI spec and Bazaar record confirm the endpoint is live and well-documented. Crawled pages returned only `unsupported_network` errors (expected for non-network paths).

Warnings

  • —Probe did not hit a network-specific path so no 402 challenge was directly captured; liveness inferred from OpenAPI spec and root_fetch_status 200
  • —Tempo testnet wallets have a 10,000 lifetime request cap per intent
  • —Session intent does not support Solana payment — only Tempo (PathUSD / USDC.e)

Citations

Provenance

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

Agent access

JSONhttps://clawmart.sh/api/listings/qsMZkV