Fastest free Fetch.ai RPC, live no-key endpoint latency
HTTP round-trip latency for Tendermint /status queries against every available public Fetch.ai (FetchHub-4) endpoint, audited every 60 seconds from 3 regions.
TL;DR. As of , PublicNode posts the lowest rpc latency at 147 ms (p50, 24h) on Fastest free Fetch.ai RPC, live no-key endpoint latency. Source: OpenChainBench, https://openchainbench.com/benchmarks/fetchhub-rpc.
Companion page
Comparing free RPC endpoints across every chain we measure? Open the cross-chain RPC matrix →
Fetch.ai is a Cosmos SDK blockchain (fetchhub-4 mainnet) focused on AI agents, autonomous economic agents, and the ASI Alliance (the merger of Fetch.ai, SingularityNET, and Ocean Protocol under the FET/ASI token). It uses the standard Cosmos Tendermint RPC interface; block height is fetched via the /status endpoint. Public keyless RPC nodes are provided by the Fetch.ai official team (rpc-fetchhub.fetch.ai), PublicNode, and Cosmos Directory. Every provider was live-verified with consecutive block-height probes at launch.
Methodology
Per-chain member of the RPC latency cluster, extended to Fetch.ai (FetchHub-4). We measure the round-trip latency of a Tendermint /status query against every available public Fetch.ai endpoint that sustains continuous probing: 3 providers at launch, every 60 seconds, from us-east, eu-west and Singapore. Each provider is probed via a GET /status request from which the block number is extracted. The harness classifies every response (ok / http_err / jsonrpc_err / stale / timeout) with a Cosmos-scaled staleness gap (20 blocks, around 120 s at 6 s/block). The cross-chain view lives on the parent rpc-capabilities benchmark; this page is the Fetch.ai-scoped answer with per-region breakdowns as a first-class dimension.
Frequently asked
What is the fastest free Fetch.ai RPC right now?
PublicNode currently leads at 147 ms (Fetch.ai block height p50 over the last 24h), measured against 3 providers probed every 60 seconds from us-east, eu-west and Singapore. The leaderboard re-sorts continuously against fresh Prometheus samples.
Which Fetch.ai RPC endpoints work without an API key?
3 endpoints sustain continuous keyless probing at launch: Fetch.ai official (rpc-fetchhub.fetch.ai), PublicNode (fetch-rpc.publicnode.com), and Cosmos Directory (rpc.cosmos.directory/fetchhub). Every listed endpoint was live-verified before inclusion.
What is Fetch.ai and why does its RPC latency matter?
Fetch.ai is a Cosmos SDK blockchain enabling autonomous AI agents to transact, negotiate, and execute tasks on-chain. The FET token (rebranded as ASI following the ASI Alliance merger with SingularityNET and Ocean Protocol) powers agent services and staking. Developers building AI agent frameworks, DeFi integrations, or on-chain governance tools need reliable low-latency RPC access to query agent registrations, transactions, and network state.
Does the fastest Fetch.ai RPC change by region?
Often. The official Fetch.ai node infrastructure is concentrated in specific regions while PublicNode distributes globally. The region tabs re-scope every number to a single probe origin.
What is the ASI Alliance and how does it relate to FetchHub?
The ASI Alliance is a merger of Fetch.ai, SingularityNET, and Ocean Protocol into a unified AI blockchain project. FetchHub-4 remains the underlying Cosmos SDK chain; the FET token migrated to the ASI token name while the technical RPC infrastructure and chain ID are unchanged.
Source code github.com/ChainBench/OpenChainBench/tree/main/harnesses/rpc-capabilities