GetBlock RPC opportunity backlog

GetBlock RPC competitive opportunities

2026-07-20 — AI/agent tooling and MCP/CLI/dev workflow support

• High priority: Build/publish GetBlock AI-agent workflow assets: llms.txt, markdown documentation, MCP recipe or server, and setup guides for Claude Code, Cursor, Codex and VS Code. QuickNode and Alchemy already have explicit MCP/agent messaging.
• High priority: Create a sales objection card for MCP/AI-agent workflow: QuickNode has /agents, MCP, x402/MPP and Agent Subscription API; Alchemy promotes MCP, CLI usage data and Claude Code setup.
• Medium priority: Evaluate x402 or similar wallet-paid RPC credit/API-key issuance. QuickNode is using x402/MPP as an autonomous-agent packaging wedge.
• Medium priority: Refresh GetBlock comparison and migration content with an "AI-ready RPC workflows" section, especially vs QuickNode, Alchemy and Chainstack.
• Low/medium priority: If full MCP server is not ready, ship interim low-cost assets: OpenAPI specs, LLM-readable docs index, copy-paste prompts, and examples for querying balances/transfers via GetBlock RPC in an AI coding assistant.

2026-07-21 — Solana / trading latency claims and low-latency infrastructure proof

• High priority: Run or commission a reproducible Solana RPC latency benchmark for GetBlock vs major competitors. Publish methodology with regions, p50/p95, dates, shared vs dedicated endpoints, and methods such as getLatestBlockhash, getProgramAccounts, sendTransaction, archival calls and WebSocket/gRPC stream behavior.
• High priority: Build a sales enablement card for vendor latency claims: QuickNode 83ms vs 1200ms, 2.5x faster, Supermission 2s to 50ms; Alchemy sub-50ms, 10x heavy calls, 20x archival, 2x throughput; Ankr 56ms, 24 metros, 25,000 RPS.
• Medium priority: Create a Solana trading infrastructure landing page if GetBlock supports dedicated Solana nodes, geo-routing, Yellowstone/gRPC, priority fees/Jito bundles, WebSocket stability or fast archival/heavy methods.
• Medium priority: Publish content cluster: Dedicated Solana RPC for trading bots, Solana RPC latency benchmark methodology, GetBlock vs QuickNode Solana RPC, GetBlock vs Alchemy Solana RPC, and Why Solana RPC latency is hard.

2026-07-22 — Dedicated node customization: regions, methods, binaries, archive/debug, private networking

• High priority: Publish a GetBlock dedicated/private node customization matrix: supported regions, archive mode, debug/trace methods, allowed method ranges, WebSocket/gRPC, node client/version, single-tenant isolation, private networking, failover, SLA and support channel.
• High priority: Create sales objection cards for Alchemy Dedicated Clusters (custom tracers/binaries, any region, single-tenant isolation, custom hardware, failover) and Chainstack Dedicated/Self-Hosted (self-hosted on customer infra, bare metal/cloud, archive, node-client/config controls).
• Medium priority: Build content around archive/debug workloads: debug_trace, trace_*, heavy eth_call, eth_getLogs ranges, historical state, backfills, simulations and indexers.

2026-07-23 — Enterprise security/compliance proof: SOC 2, ISO, SSO, RBAC, SLAs, support channels

• High priority: Ship a public GetBlock enterprise security/compliance matrix: SOC/ISO status, report access process, SSO/SAML, RBAC/custom roles, audit logs, IP/domain allowlisting, TLS/KMS, private networking, SLA/service credits and support channels.
• High priority: Add enterprise-proof rows to pricing/plan comparison if supported. QuickNode and Alchemy already surface SSO/RBAC/SLA/security controls in pricing.
• Medium priority: Create sales objection cards for QuickNode (SOC1/SOC2/ISO + SAML/RBAC + 24/7 engineering), Alchemy (SSO/KMS/TLS + RBAC/logs/signed SLAs), and Chainstack (SOC2 + SSO/MFA/granular permissions/TLS/KMS/private networking).

2026-07-28 — Attack-surface synthesis: toxic workloads, failure containment, appchain/agent migration

• Highest priority: Build a Toxic Workload Suite: RPC Cost Profiler plus dedicated SLO/SKUs for eth_getLogs, archive/backfill, websocket, polling-heavy workloads and stream/webhook alternatives. This is the strongest evidence-backed attack surface from the full report.
• High priority: Build a failure-containment layer: method-level status, private health API, endpoint diagnostics, incident RCA, synthetic monitoring and optional multi-provider routing recommendations.
• Medium/high priority: Reframe multichain breadth as a governance/control plane: scoped keys, instant rotation, per-chain/method quotas, anomaly alerts, invoice/VAT hygiene and overage guardrails.
• Timing play: Explore L2/appchain/AI-agent migration layer: New Chain RPC Launch Kit, sequencer/RPC divergence monitoring, archive/indexing bundles and agent-safe API keys/limits. Evidence is lower-confidence and needs independent discovery calls.
• Credibility rule: Treat vendor pages and this internal monitor as interested/derivative. Use daily monitoring to route sources into hypotheses, then corroborate load-bearing claims with primary operational artifacts, customer-side evidence or independent benchmarks.

2026-08-08 — X read-only signals: benchmarks, status proof, AI/MCP, x402, new-chain demand

• High priority: Add a public RPC reliability report lane: Base / Robinhood / Sonic / HyperEVM / Cosmos with latency, TLS/cert hygiene, stale-height checks, archive/debug availability and incident notes. X-visible CompareNodes-style benchmarking is becoming a public battlefield.
• High priority: Turn status/SLA transparency into a competitive proof asset. NOWNodes-style status-page messaging and public endpoint failure callouts show that buyers increasingly expect per-chain reliability visibility.
• High priority: Package archive/debug/trace/beacon/bundler workloads as enterprise dedicated-node offers for account-abstraction wallets, MEV/searchers, auditors, RWA apps and analytics/indexing teams.
• Medium/high priority: Build AI-agent RPC assets: GetBlock MCP or MCP-lite recipe, LLM-readable docs, function-calling templates, scoped keys and budget/rate-limit guardrails. QuickNode’s visible AI/MCP/x402 motion makes this a near-term battlecard requirement.
• Medium priority: Explore x402/stablecoin-paid API access as a demo/partnership wedge with CoinbaseDev/x402 ecosystem; keep it experimental until buyer demand is validated.
• Medium priority: Create a real-time event infrastructure cluster: WebSockets, streams, webhooks, alerts, and “polling to stream/webhook” migration for wallets, trading apps, bots, analytics and payment apps.
• Medium priority: Add new-chain launch ABM pages and lead lists for Base, Robinhood Chain, World Chain, Stable, Sonic and HyperEVM builders, with chain-specific benchmark/status proof.
• Messaging update: For institutional/RWA accounts, translate GetBlock from “RPC provider” into “network access + transaction visibility + historical/debug data + operational records for controlled onchain operations.”
• Evidence rule: Treat X-visible competitor/provider posts as directional demand and positioning signals, not as independent proof. Corroborate load-bearing performance or outage claims before external sales use.

2026-09-15 — Ecosystem partnerships, foundation offers, credits and startup programs

• High priority: Publish a concrete GetBlock for Startups program with eligibility, duration, credit value, included networks, support and post-credit pricing; QuickNode and Alchemy visibly merchandise named startup programs.
• High priority: Package a Foundation RPC Launch Kit with sponsored public endpoints, launch-day capacity, archive/debug options, faucet/docs support and public status/SLA proof. Pocket Foundation’s F-Chains offer makes foundation-funded RPC economics unusually visible.
• High priority: Run migration plays for Blast API and Grove users: credits, endpoint/method compatibility checks, dual-running and named cutover support. State clearly that Pocket Network continues even though Grove is winding down.
• Medium priority: Enforce partnership taxonomy in CRM and public copy: official/preferred provider, day-one supported, foundation-sponsored and commercially available. Do not convert chain-list inclusion into “official partner” language.
• Medium priority: Record deal metadata—counterparty, source/date, exclusivity, funding or credits, chains, term, SLA/support and redemption constraints—to prevent recurring keyword-based overclaims.