Methodology · source-gated claims
How to use the Proof Hub without overclaiming.
The purpose is not to declare GetBlock “cheapest.” The purpose is to create buyer-specific proof that translates usage models into production risk, cost, and architecture decisions.
Claim discipline
| Claim type | Allowed phrasing | Do not say |
|---|---|---|
| Vendor pricing/details | “Provider page states…” or “as of the latest source-gated review…” | “Guaranteed cheapest/best” |
| Cost comparison | “For this method mix, estimated unit burn is…” | “X is cheaper for everyone” |
| SLA/reliability | “Benchmark observed…” and “contract terms must confirm…” | “99.99% is always better than 99.9%” |
| AI-agent demand | “Pilot signal; vendor-led category motion” | “Proven 2026 revenue pool” |
Minimum data to collect from a prospect
- 7–14 days of request volume by method and chain.
- Peak RPS by hour and region, not only monthly total.
- Archive/log/debug share and failed range/backfill examples.
- Current provider plan, limits hit, support incidents, and procurement blockers.
- Business impact of failure: launch delay, stale balances, failed payments, broken analytics, compliance exposure.
Proof output template
- Workload summary.
- Provider-unit translation table.
- Latency/error benchmark.
- Recommended GetBlock package.
- Open caveats and required contract checks.