GetBlock RPC competitor monitor — 2026-09-14

GetBlock RPC competitor monitor — 2026-09-14

Criterion of the day: Developer experience: SDKs, dashboards, logs, request analytics, API-key management, onboarding and support workflow (developer-experience).

Executive summary

No decision-relevant market change can be established from hash changes alone. QuickNode home/pricing and Allnodes home/pricing changed at page level, but the captures contain substantial navigation, promotion and live-market-value noise; these diffs are not classified as product changes without narrower before/after evidence.

Today’s useful result is a stricter consolidation of the developer-experience evidence model across all 15 providers:

1. Infura’s pricing surface provides unusually concrete observability evidence: API-key limits/sharing, usage notifications and request visibility windows of up to 24 hours or 30 days, depending on plan.
2. NOWNodes publishes concrete workflow and support details: dashboard API-key generation, API Statistics, 24/7 support, account-manager channels/hours and response-time claims by plan.
3. QuickNode publishes a clear onboarding/support ladder (free trial/no card plus 24/12/8-hour support SLAs), but this pass did not directly substantiate the previously broad SDK and dashboard/key-management cells; those cells were conservatively reset to Not verified in monitored public evidence.

The living topic matrix was expanded to five uniform dimensions and now records 13/15 providers with at least one evidenced dimension and 4/15 with evidence across all five. This is evidence completeness, not a product-quality ranking.

Evidence and change assessment

Decision-relevant evidence confirmed today

• QuickNode: pricing explicitly shows a one-month free trial with no card, community support on free, and support-SLA tiers of 24 hours (Build), 12 hours (Accelerate) and 8 hours (Scale). The page changed versus the previous snapshot, but the exact cause of the diff is not isolated; treat these as current observed facts, not necessarily newly launched terms.
• Infura: pricing lists community forums, ticketed and prioritized ticket support, enterprise enhanced-support SLA, API-key limits/sharing, usage notifications and request visibility up to 24 hours/30 days. Docs exposes dashboard, API-key creation, first request, concepts, how-to guides and tutorials.
• Chainstack: home explicitly links open-source SDKs/tools/sample projects and a performance dashboard. Docs exposes account/organization/project/network/node management, statistics, node usage, release notes, status, Discord and Telegram.
• Ankr: RPC portal advertises projects, statistics and a multi-project statistics dashboard. Docs provides API reference, tutorials, “mint an API key, fire your first call,” support request and knowledge base. Enterprise says engineering support can run through a dedicated Slack or Telegram channel.
• Moralis: docs directly supports API-key onboarding, quickstarts, migration guides and product tutorials. Current monitored evidence does not establish request-level usage analytics or a support escalation commitment.
• NOWNodes: home provides a four-step key-generation/integration flow. Pricing lists API Statistics, plan-level API-key counts, 24/7 support, account-manager channels/hours and published response times. Exact entitlement by plan should be verified before sales use because the extracted comparison-table order is dense.
• dRPC: docs includes key creation, first request, teams and roles, JWT authentication and RPC/Data API quickstarts. Home describes NodeHaus as RPC management and monitoring for chains. This is not automatically equivalent to end-user request-history analytics, so the topic cell keeps that scope caveat.
• Blockdaemon, Tatum, Allnodes and Lava: their current docs/help surfaces evidence implementation guides/onboarding and support entry points, but not customer key/team controls or request-level usage analytics. Generic product analytics, status links and infrastructure monitoring were not promoted into stronger observability claims.

Lifecycle corrections

• Blast API: first-party notice says Blast products are deprecated and directs customers to Alchemy. The Alchemy documentation redirect is not evidence of a live Blast capability. Its living-matrix cells are now Not applicable for the discontinued active product.
• Pocket Network / Grove: Grove says Grove is winding down, while Pocket Network continues and advertises no-key public APIs. The matrix keeps these identities/lifecycles separate and does not infer a dedicated-endpoint dashboard from the public endpoint flow.

Noise and non-findings

• QuickNode page changes: the captured pages contain a new promotional banner and repeated global navigation. The hash change is not, by itself, a developer-experience launch.
• Allnodes page changes: the capture includes a bare-metal promotion plus volatile protocol/market-cap values. No new RPC dashboard, analytics or support workflow is established from the diff.
• No page-level change was detected for Alchemy, Infura, Chainstack, Ankr, Moralis, NOWNodes, dRPC, Blast API, Blockdaemon, Tatum or Lava Network. Stable pages can still supply current evidence; they do not represent launches today.
• Baseline/extraction artifacts: Grove docs and LlamaRPC docs/status appeared as baseline failures because DNS did not resolve. This is collection status, not proof that a capability is absent.

Provider evidence ledger

Topic-brief modifications

The living source /monitoring/topics/developer-experience.html was modified—not merely linked to this report:

• replaced the four-column matrix with five fixed dimensions;
• added direct source links within every positive claim;
• updated Infura, Chainstack, Ankr, NOWNodes and dRPC request/control-plane cells from current evidence;
• upgraded Blockdaemon, Tatum, Allnodes and Lava onboarding/support rows where docs explicitly support them;
• corrected Blast to a deprecated/Not applicable row;
• narrowed unsupported QuickNode SDK/dashboard claims;
• recalculated breadth/completeness and added row-specific research gaps.

GetBlock actions

Sales

• Use a five-step demo checklist in evaluations: create/rotate key, manage team access, inspect request usage/errors, configure alerting, and open/escalate a support case. Public evidence is weakest around keys/teams and request analytics.
• Counter broad “developer friendly” positioning with demonstrated workflow depth; do not claim competitive absence where the matrix says Not verified in monitored public evidence.

Product marketing

• Publish support response semantics as clearly as QuickNode/NOWNodes/Infura, including clock, severity, channel and plan—not only “priority support.”
• Package a verifiable control-plane story around key governance and request diagnostics, the two least-completely evidenced dimensions across the monitored set.

Content

• Build a buyer guide: “How to evaluate an RPC dashboard: key rotation, team roles, request logs, analytics retention and support escalation.” Link every criterion to an observable demo or documentation page.
• Refresh GetBlock comparison copy conservatively: Blast is deprecated; Grove is winding down but Pocket Network continues; LlamaRPC remains an availability/evidence gap, not a proven product-absence claim.

Research limitations and next priorities

1. Retrieve direct QuickNode SDK, key-management and request-analytics documentation before restoring those cells.
2. Verify Alchemy dashboard key/team controls and the exact retention/export behavior behind request/usage visibility.
3. Locate NOWNodes’ current documentation endpoint and confirm feature-to-plan mapping for API Statistics.
4. Establish whether LlamaRPC has a replacement domain/service surface.
5. Request product demos or contractual evidence for dashboard and request analytics gaps; navigation keywords are insufficient.
6. Re-check volatile support response and plan claims before external sales use.

Publication notes

• The pre-run publisher reported success (published_urls: 121, latest daily 2026-09-14), but publication must be rerun after this manual consolidation.
• The agentic-routing paper updater reported ok: true, paper_updated: true, with 61 candidate evidence items. Its generated note says QuickNode evidence touched agentic policy framing, cost/SLA constraints, enterprise-SLA metrics and incident simulation. Keyword-nominated evidence should still be reviewed before treating it as a strong implementation claim.