Fetch.ai RPC endpoints: free public URLs by 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 has the lowest median latency of the 3 free public Fetch.ai RPC endpoints measured, 83 ms (p50, 24h, 3 regions). Source: OpenChainBench, https://openchainbench.com/benchmarks/fetchhub-rpc. 3 public endpoints, no key: fetch-rpc.publicnode.com, rpc-fetchhub.fetch.ai, rpc.cosmos.directory. Full URLs with their 24h median are listed below.
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
Fetch.ai: 3 free public RPC endpoints answering `GET /status` every 60 seconds from us-east, eu-west and Singapore, ranked by 24h median. PublicNode leads at 83 ms; the chain-official endpoint measures 166 ms. We measure the round-trip latency of a Tendermint /status query against every available public Fetch.ai endpoint that sustains continuous probing: 3 providers live today, 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.
Results: 3 free public Fetch.ai RPC endpoints ranked by p50 latency (24h, 3 regions)
| № | Providers | p50 | p90 | p99 | Success |
|---|---|---|---|---|---|
| 1 | PublicNode | 83 ms | 177 ms | 497 ms | 100.00% |
| 2 | Fetch.ai | 166 ms | 191 ms | 547 ms | 99.91% |
| 3 | Cosmos Directory | 199 ms | 331 ms | 852 ms | 98.91% |
Public Fetch.ai RPC endpoints measured
The 3 no-key endpoints answering our probes today, with their current 24h median. Paste one into a wallet or a client as is: no signup, no key. Private providers (API key) are never listed with a URL.
PublicNodehttps://fetch-rpc.publicnode.com83 ms100.0%
Fetch.aihttps://rpc-fetchhub.fetch.ai166 ms99.9%
Cosmos Directoryhttps://rpc.cosmos.directory/fetchhub199 ms98.9%
Median round-trip and success rate over the last 24 hours across the probe regions; the ranked table above carries p90, p99 and the per-region split.
Frequently asked
Which Fetch.ai RPC endpoints work without an API key?
3 endpoints are probed on this chain: 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.
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