GetBlock / rpc.run free tools

Free RPC planning tools for Web3 infrastructure teams.

Calculators and decision helpers for teams choosing between shared RPC, dedicated nodes, archive/debug access, failover, and enterprise reliability controls.

Start with archive estimator

live

Archive Node vs Managed RPC Requirement Estimator

Estimate whether a workload needs archive access, a dedicated node, or a managed RPC plan based on method mix, history depth, and reliability needs.

Open tool

live

Web3 RPC Cost & Plan-Fit Calculator

Translate request volume, compute-unit assumptions, failover needs, and workload criticality into a practical RPC plan-fit recommendation.

Open tool

live

RPC SLA / Reliability Risk Calculator

Estimate monthly downtime exposure, revenue-at-risk, and the reliability tier a production blockchain workload should consider.

Open tool

live

RPC Migration Effort Estimator

Estimate calendar and engineering weeks to migrate off a current RPC provider, and generate a copyable migration plan for procurement and delivery leads.

Open tool

live

Indexer vs RPC Decision Tree

Decide when raw RPC, an indexer, or both are needed based on read patterns, latency, joins, and real-time state — with a copyable vendor question list.

Open tool

live

Web3 Infra RFP Checklist Generator

Generate a copyable Web3 RPC/infrastructure RFP checklist tailored to workload, chains, SLA, compliance, and support tier for enterprise procurement.

Open tool

planned

RPC Error Decoder

Decode common JSON-RPC and provider errors.

Planned

planned

Chain API Compatibility Checker

Compare required RPC methods across chains/providers.

Planned

planned

Agent-Safe RPC Readiness Checker

Check whether an RPC setup is safe for AI agents touching crypto.

Planned

security-gated

Endpoint Health & Latency Checker

Security-sensitive live endpoint checker; requires SSRF, private-IP, rate-limit and log-redaction controls before public launch.

Planned

Acceptance status

The first three Batch 1 tools are live with unique pages and browser-side interactions. Security-sensitive endpoint testing remains gated until a hardened backend exists: deny private IPs, rate limit, short timeouts, cache, and redact logs.