Agentic-RPC positioning: RPC for autonomous agents, MCP servers, tool calling, agent wallets and machine customers

Comparison updated: 2026-11-02

Coverage: 7/15 providers have at least one directly evidenced dimension; 1/15 has evidence in all four dimensions. No decision-relevant page change was detected in the 2026-11-02 snapshot; this consolidation tightens prior over-broad classifications and refreshes source dates.

> Evidence semantics: “Publicly evidenced” means a direct vendor source explicitly supports the stated positioning. Not verified in monitored public evidence means the monitored sources are insufficient; it does not mean the capability is absent. Navigation labels, AI-readable documentation, and generic “AI-ready” language do not by themselves prove an agent product.

Comparison dimensions

  • Agent-facing RPC / data: an explicit product or positioning statement for autonomous agents, not merely generic AI marketing.
  • MCP / agent tools: an MCP server, agent skills, or callable agent-service/tool surface.
  • Agent wallet / execution: a wallet or transaction-execution stack explicitly positioned for agents.
  • Machine payments: an explicit machine-customer, pay-per-call, x402, or equivalent agent-payment proposition.
ProviderAgent-facing RPC / dataMCP / agent toolsAgent wallet / executionMachine paymentsDirect sourcesCoverage
QuickNodeNot verified in monitored public evidenceNot verified in monitored public evidenceNot verified in monitored public evidenceNot verified in monitored public evidenceHome, blog0/4
AlchemyPublicly evidenced — AI agents are a named solutionPublicly evidenced — Agent Skills and MCP serverPublicly evidenced — AI build surface is paired with wallet and transaction APIs; exact autonomous-control model requires buyer validationNot verified in monitored public evidenceHome, docs3/4
InfuraNot verified in monitored public evidenceNot verified in monitored public evidenceNot verified in monitored public evidenceNot verified in monitored public evidenceInfura docs, MetaMask developer news0/4
ChainstackPublicly evidenced — “AI-ready infrastructure” positioningPublicly evidenced — Chainstack MCP is a named developer resourceNot verified in monitored public evidenceNot verified in monitored public evidenceHome, docs2/4
AnkrPublicly evidenced — Agentic RPC is a documented product areaPublicly evidenced — docs explicitly mention MCP servers and TORPCNot verified in monitored public evidencePublicly evidenced — current vendor blog lists an x402 launch; commercial scope needs validationDocs, blog3/4
MoralisNot verified in monitored public evidenceNot verified in monitored public evidenceNot verified in monitored public evidenceNot verified in monitored public evidenceDocs0/4
NOWNodesNot verified in monitored public evidencePublicly evidenced — MCP Servers appear in the plan feature matrixNot verified in monitored public evidenceNot verified in monitored public evidencePricing1/4
dRPCPublicly evidenced — AI Agents is a named product areaPublicly evidenced — onchain skills for AI agents and MCPNot verified in monitored public evidenceNot verified in monitored public evidenceHome, blog2/4
Blast APINot applicable — vendor states the service is deprecatedNot applicable — vendor states the service is deprecatedNot applicable — vendor states the service is deprecatedNot applicable — vendor states the service is deprecatedDeprecation notice0/4 active offering
BlockdaemonNot verified in monitored public evidenceNot verified in monitored public evidenceNot verified in monitored public evidenceNot verified in monitored public evidenceHome, docs0/4
TatumNot verified in monitored public evidenceNot verified in monitored public evidenceNot verified in monitored public evidenceNot verified in monitored public evidenceHome, docs0/4
Pocket Network / GrovePublicly evidenced — Pocket positions data services for AI agentsPublicly evidenced — Agentic Portal exposes callable servicesNot verified in monitored public evidencePublicly evidenced — agent-paid API calls and onchain per-request payment are explicitPocket Network, Grove wind-down notice3/4
LlamaRPCNot verified in monitored public evidenceNot verified in monitored public evidenceNot verified in monitored public evidenceNot verified in monitored public evidenceNo reachable monitored first-party page on 2026-11-020/4
AllnodesNot verified in monitored public evidenceNot verified in monitored public evidenceNot verified in monitored public evidenceNot verified in monitored public evidenceMonitored pages blocked automated retrieval on 2026-11-020/4
Lava NetworkPublicly evidenced — vendor explicitly positions routing for AI-agent trafficNot verified in monitored public evidenceNot verified in monitored public evidenceNot verified in monitored public evidenceHome1/4

Cross-provider readout

  • Breadth: 7 of 15 tracked providers have at least one directly evidenced dimension: Alchemy, Chainstack, Ankr, NOWNodes, dRPC, Pocket Network / Grove, and Lava Network.
  • Completeness: none has four active dimensions fully evidenced. Ankr and Pocket each cover three; Alchemy covers three with agent-wallet execution scope still requiring procurement validation.
  • Most evidenced dimension: agent-facing positioning and MCP/agent tools are the emerging competitive surface. Explicit agent wallets and machine-payment mechanics remain much less commonly documented.
  • No current monitored evidence: QuickNode, Infura, Moralis, Blockdaemon, Tatum, LlamaRPC, and Allnodes. This is an evidence gap, not a negative product claim.
  • Lifecycle caveats: Blast API is deprecated and redirects users toward Alchemy. Grove says it is winding down, while Pocket Network continues separately; buyers should not treat Grove and Pocket as one current commercial offering without validation.

Buyer guidance

  1. Ask vendors to demonstrate the exact MCP server or skill manifest, supported methods, authentication boundary, rate limits, and write-transaction controls.
  2. Separate coding-assistant tooling from runtime infrastructure for autonomous agents; “AI-ready docs” alone is not agentic RPC.
  3. For wallets, verify key custody, policy controls, spend limits, simulation, approval escalation, gas sponsorship, and recovery.
  4. For x402 or pay-per-call claims, verify settlement asset, replay protection, refunds, pricing discovery, service identity, and production availability.
  5. Require an explicit SLA and observability model for bursty machine traffic; do not infer it from generic enterprise RPC claims.

GetBlock positioning implications

  • Package an Agent Gateway around auditable tool schemas, scoped keys, deterministic policy controls, and read/write separation rather than relying on a generic “AI-ready” label.
  • Publish a first-party MCP/skills catalog with chain and method coverage, transaction safeguards, and machine-readable limits.
  • Treat machine payments as an optional settlement layer, not a substitute for authentication, quotas, abuse controls, or contractual service quality.
  • Differentiate with clear agent-wallet integrations and human-in-the-loop policy hooks; this is less publicly evidenced than generic MCP availability.

Research priorities

  1. Locate dedicated first-party agent product pages for QuickNode, Infura, Moralis, Blockdaemon, and Tatum rather than classifying navigation or generic AI wording.
  2. Validate Alchemy’s autonomous wallet-control model and Ankr’s x402 production/commercial scope.
  3. Obtain accessible first-party evidence for LlamaRPC and Allnodes.
  4. Determine whether Chainstack MCP and NOWNodes MCP are production services, their method coverage, and plan-specific limits.
  5. Track Pocket’s Agentic Portal separately from the winding-down Grove commercial entity.
Research log (audit trail)