GetBlock RPC competitor monitor — 2026-11-11
Criterion: Developer experience: SDKs, dashboards, logs, request analytics, API-key management, onboarding and support workflow (developer-experience).
Decision summary
Confirmed new market/product changes: 0. Evidence-classification upgrades: 1. Source-attribution corrections: 1. The living five-dimension, 15-provider comparison has been re-consolidated as of 2026-11-11; old supported claims are preserved unless contradicted. A changed snapshot/hash is not proof of a launch. Published descriptions are vendor claims, not tests of actual dashboard access, analytics export or support response.
- Alchemy — one narrow matrix upgrade (newly confirmed evidence, not a newly launched capability). First-party documentation directly displays a dashboard entry point and “Create an API key” workflow. Dashboard/key cell moves from
Not verified in monitored public evidenceto evidenced key creation only. Team permissions, restriction, rotation, request-level retention/export are not established. The pre-run home/pricing/enterprise snippets were dominated by repeated navigation; direct docs were checked separately and returned 200. - Pocket Network / Grove — source correction, not feature launch. Pocket's scoped public-RPC page explicitly says copy an endpoint, no account/API key; this replaces an overly broad homepage citation. Dedicated-gateway key/team management remains
Not verified in monitored public evidence. Grove's farewell still states Grove is winding down; do not attribute this to the continuing Pocket Network. - Unchanged developer-experience evidence retained: QuickNode pricing documents onboarding/support tiers; Chainstack docs list project/node management and statistics; Ankr RPC describes multi-project statistics; NOWNodes pricing lists API Statistics/support; dRPC docs list key creation, roles and quickstarts; Infura docs, Moralis docs, Blockdaemon docs, Tatum docs and Lava home continue to supply the narrower cited workflows. No basis in today's capture to infer newly shipped customer-facing request logs, dashboard controls, or SDKs. Blast's notice continues to say its products are deprecated and points to Alchemy; Alchemy's docs are not a Blast product claim.
Snapshot changes versus decision-relevant changes
The collector marked QuickNode home/blog, Chainstack docs, dRPC pricing/chainlist, Tatum blog and Pocket Network homepage as changed (plus first-baseline failures for certain docs/status hosts). These are page-level signals; the available text shows repeated navigation, chain announcements, pricing/chainlist context or redirected pages, not a confirmed new developer-experience capability. The QuickNode blog has new dated content, but book/chain announcements are not evidence for any of the five developer-experience cells. dRPC pricing mentions CU units and a plan; that is pricing context, not proof of request-level analytics. Chainstack docs lists existing workflow categories; hash differences alone do not indicate feature launch. Tatum blog did not provide a new qualifying developer-workflow fact in the extract. Pocket homepage now emphasizes agent data services, not proof that the former Grove Portal is an active RPC product.
Source/access gaps to preserve
- 404 on QuickNode changelog, Alchemy legacy chains docs and customer stories, NOWNodes legacy Postman docs, Blockdaemon legacy RPC and pricing, Tatum legacy chains, Lava legacy developers and network. These paths do not prove missing capabilities; locate replacements before making negative assertions.
- LlamaRPC homepage and
/chainsreturned 526; docs/status hostnames could not be resolved. No product-absence claim. All five cells stay unverified. - Allnodes homepage, pricing, nodes, blog and help root returned 403 access protection. Earlier help-center observations are retained provisionally in the living brief; today's run did not revalidate those details. Grove docs did not resolve; the other Grove routes repeated its farewell notice. Lava docs yielded only a thin title in the collector, not new feature evidence.
- Infura blog redirects to MetaMask developer news; Blast docs redirect to Alchemy. Neither redirect transfers product claims to the original brand. Vendor chain counts, prices and support/SLA wording are volatile: verify before sales use. No generic GetBlock gRPC/archive parity is inferred.
Buyer and GetBlock action
Prioritize hands-on demos of create/restrict/rotate API key, team/role access, RPC request error/latency drill-down and export, plus ticket escalation and response guarantees. A general docs index, infrastructure monitoring or status page is not request-level observability. GetBlock should publish one verifiable end-to-end developer workflow rather than rely on broad developer-friendly language.
Source ledger and automation
Collector evidence is retained internally at /root/getblock-rpc-competitive-research/monitoring/raw/2026-11-11/; the matrix contains direct first-party links per positive cell. The independent CompareNodes SOC/ISO directory was available but not used for this developer-experience comparison (reserve for compliance/procurement and do not count it as a provider). Pre-run encyclopedia publisher reported success (156 URLs), but this does not substitute for publishing and checking today's consolidated brief. The pre-run agentic_routing_paper_update.ok was true and paper_updated was true; paper URL: https://rpc.run.beinginfuture.com/papers/agentic-routing-rpc.html . The paper updater appended a QuickNode routing/SLA evidence note, which is not counted as a developer-experience market change. Post-consolidation publisher and HTTPS checks are tracked in the cron verification run, not inferred from the pre-run success.