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.

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

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.