Lava Network
- Confirmed general context: Lava describes an open network of independent RPC providers with routing and failover.
- Schema decision: that protocol-level provider ecosystem does not by itself prove a buyer-facing marketplace, add-on, integration catalog or paid expansion surface.
- Source: home, docs, blog.
- Extraction gaps: old developers and network paths returned 404.
Cross-provider implication
The market mostly competes through proprietary suite expansion—data APIs, streams, webhooks, wallets, routing and dedicated infrastructure—not through a clearly open add-on marketplace. “Marketplace” must therefore be disambiguated in sales collateral: Chainstack’s node marketplace/add-ons, Alchemy’s Dapp Store and Pocket’s Agentic Portal serve different buyer jobs and should not be presented as like-for-like.
Research limitations and next checks
- Revalidate Allnodes with an access method that can pass the current protection; keep today’s status as an extraction gap.
- Locate accessible first-party LlamaRPC materials.
- Verify QuickNode’s current marketplace status rather than carrying forward older market memory.
- Capture add-on-level price, chain scope, quota interaction and SLA inheritance for Chainstack and NOWNodes.
- Determine whether Alchemy Dapp Store listings create infrastructure attach/billing opportunities or function only as a directory.
- Determine whether Lava exposes buyer-selectable provider/add-on packaging beyond decentralized routing.
Publishing and related artifacts
- The pre-run encyclopedia publication succeeded (
published_urls: 145), but this report and the consolidated brief still require the mandated post-write republish and HTTPS QA.
- The agentic-routing paper updater reported ok=true and paper_updated=true, with 11 evidence items; today’s routing-paper note primarily concerns QuickNode/Chainstack latency, SLA, archive and routing-adjacent language rather than a marketplace-specific architecture claim.
- Living paper: Agentic Routing for RPC.
Lava Network
Home retains provider scoring, routing and automatic failover claims. Routing in real time is not evidence of client WebSocket/gRPC streaming. No new gaming product event established.
GetBlock implication and next research
Package isolation, regional p95/p99, sustained/burst method-specific limits, websocket fan-out and contractual service credits rather than generic gaming or unlimited language. Distinguish shared endpoints, dedicated gateways, managed nodes and HA clusters before comparing prices. No justified new quote band or self-host total can be derived without a specified chain, retention, region, method mix and operational scope. Do not claim GetBlock gRPC/archive parity without chain-specific evidence.
Prioritize QuickNode burst/enterprise scope, Blockdaemon tenancy contract, Pocket current dedicated endpoint terms, and Allnodes managed-node operations. Seek named gaming/consumer/social references for all vendors. Preserve historical evidence until disproven; flag freshness rather than silently deleting it.
Collection limitations and provenance
- QuickNode changelog: 404. Alchemy legacy chain docs and customer-stories URLs: 404; navigation-heavy pricing/enterprise excerpts do not support missing plan details.
- NOWNodes legacy Postman docs: 404. Blockdaemon legacy blockchain-api and pricing: 404. Tatum legacy supported-blockchains: 404.
- Lava developers/network paths: 404; docs extraction is title-only.
- LlamaRPC home/chains: 526; docs/status DNS unresolved. Grove docs DNS unresolved.
- Allnodes home, pricing, nodes, blog and help: 403; historical claims are not freshly verified.
- Infura blog redirects to MetaMask and docs to docs.infura.io; dRPC blog redirects to blog.drpc.org. Redirects do not establish product changes.
- Raw captures remain under
/root/getblock-rpc-competitive-research/monitoring/raw/2026-11-17/. No raw snippets or collection telemetry are used as the living comparison.
- CompareNodes SOC/ISO reference was collected but marked irrelevant to today's criterion. It is a reference, not a sixteenth RPC provider; no compliance conclusion inferred.
Publication and routing paper
Pre-run encyclopedia publisher reported success, 162 URLs. That did not establish topic freshness: the topic brief still had September 20 consolidation and has now been substantively updated.
agentic_routing_paper_update.ok=true, paper_updated=true, evidence_count=14, publisher exit_code=0 in the supplied script result. The automation appended a routing-evidence review note; it is not proof that all proposed paper analyses or benchmarks were completed. Paper: agentic routing RPC.
Public verification: PASS after rebuilding 162 URLs. HTTPS topic, daily and paper returned 200. Topic has Current consolidated view, exactly 15 provider matrix rows, 2026-11-17, and a closed Research log below the comparison. Updated direct sources for Infura, its docs and Blockdaemon returned 200. QuickNode home/enterprise initially returned 403 to urllib, then both returned 200 to curl with a browser user-agent; the supplied same-day captures remain the claim evidence. Table wrapper, per-cell labels and responsive overflow/card CSS were checked structurally; no visual mobile inspection claimed.