WAX RPC endpoints: free public URLs by latency
HTTP round-trip latency for GET /v1/chain/get_info against every available public WAX (Antelope) node, audited every 60 seconds from 3 regions.
TL;DR. As of , Greymass has the lowest median latency of the 3 free public WAX RPC endpoints measured, 129 ms (p50, 24h, 3 regions). Source: OpenChainBench, https://openchainbench.com/benchmarks/wax-rpc. 3 public endpoints, no key: wax.greymass.com, wax.eosusa.io, api.waxsweden.org. 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 →
WAX (Worldwide Asset eXchange) is a delegated proof-of-stake blockchain built on the Antelope protocol, specialising in NFTs and gaming assets. It produces one block every 0.5 seconds and operates the same /v1/chain/get_info REST endpoint as EOS. Public endpoints are available without an API key from Greymass, EOSUSA and WAX Sweden. Every provider was live-verified with consecutive get_info probes at launch.
Methodology
WAX: 3 free public RPC endpoints answering `GET /v1/chain/get_info` every 60 seconds from us-east, eu-west and Singapore, ranked by 24h median. Greymass leads at 129 ms. We measure the round-trip latency of a single REST call (GET /v1/chain/get_info) against every available public WAX node that sustains continuous probing: 3 providers live today, every 60 seconds, from us-east, eu-west and Singapore. The harness classifies every response (ok / http_err / jsonrpc_err / stale / timeout) with a WAX-scaled staleness gap (600 blocks, around 5 min at 0.5 s/block). The cross-chain view lives on the parent rpc-capabilities benchmark; this page is the WAX-scoped answer with per-region breakdowns as a first-class dimension.
- Cadence: every 60 seconds per provider, from each of 3 probe regions (us-east Virginia, eu-west Amsterdam, sgp Singapore). Headline p50/p90/p99 aggregate across all 3 regions via Prometheus avg(quantile_over_time(...)); per-region breakdowns are first-class on this page via the region tabs.
- Payload: HTTP GET /v1/chain/get_info. Plain REST call. The response carries head_block_num as a plain integer.
- Latency measurement, call-result classification (`ok`, `http_err`, `jsonrpc_err`, `stale`, `timeout`) and the archive-depth audit follow the cluster method documented on [rpc-capabilities](openchainbench.com/benchmarks/rpc-capabilities#methodology); this page is the WAX-scoped view of the same harness, with the same exclusion rules.
- Chain scope: every query on this page is pinned to chain=wax. Provider coverage today: 3 endpoints.
Results: 3 free public WAX RPC endpoints ranked by p50 latency (24h, 3 regions)
| № | Providers | p50 | p90 | p99 | Success |
|---|---|---|---|---|---|
| 1 | GreymassGreymass public WAX Antelope API, keyless | 129 ms | 147 ms | 249 ms | 99.58% (n=4325) |
| 2 | EOSUSAEOSUSA public WAX Antelope API, keyless | 212 ms | 489 ms | 1.03 s | 98.84% (n=4323) |
| 3 | WAX SwedenWAX Sweden public Antelope API, keyless | 291 ms | 386 ms | 1.02 s | 100.00% (n=4318) |
Public WAX 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.
Greymasshttps://wax.greymass.com129 ms99.6%
EOSUSAhttps://wax.eosusa.io212 ms98.8%
WAX Swedenhttps://api.waxsweden.org291 ms100.0%
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 WAX RPC endpoints work without an API key?
3 endpoints are probed on this chain: Greymass (wax.greymass.com), EOSUSA (wax.eosusa.io) and WAX Sweden (api.waxsweden.org). Every listed endpoint was live-verified with a get_info call returning a parsable head_block_num before inclusion.
Source code github.com/ChainBench/OpenChainBench/tree/main/harnesses/rpc-capabilities