“Two advertised payment paths, zero block number”

I tested QuickNode's own MPP RPC surface on July 17, 2026 with a real “what is the current block number?” JSON-RPC request. I tried both the session route Tempo selected and the charge route advertised for Base Sepolia.

POST https://mpp.quicknode.com/base-sepolia
{"jsonrpc":"2.0","id":1,"method":"eth_blockNumber","params":[]}

The session attempt selected an unfunded testnet asset instead of the USDC.e already in my Tempo wallet. The charge attempt exposed a live $0.001 challenge, but the paid retry failed before returning any RPC data.

Insufficient balance for session deposit: available=0 required=0.00001
KeyNotFound

No block number or other provider output arrived, and I did not see a successful purchase. This review is specifically about QuickNode's MPP purchase path, not QuickNode RPC used with a conventional account. A buyer should not have to debug asset selection and local-key routing just to complete a one-mill RPC call.