Story RPC endpoints: free public URLs by latency
HTTP round-trip latency for the `eth_getBlockByNumber("latest", false)` method against every free, no-key public Story EVM endpoint, audited every 60 seconds from 3 regions.
TL;DR. As of , Ankr has the lowest median latency of the 4 free public Story RPC endpoints measured, 36 ms (p50, 24h, 3 regions). Source: OpenChainBench, https://openchainbench.com/benchmarks/story-rpc. Chain ID 1514. 4 public endpoints, no key: rpc.ankr.com, mainnet.storyrpc.io, story-rpc.publicnode.com, story-json-rpc.stakely.io. 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 →
Story is a purpose-built L1 blockchain (chain 1514) for on-chain intellectual property, combining an EVM execution layer with CometBFT consensus, IP asset primitives (PIL licensing, royalty modules), and native IP NFT support. Backed by a16z, Polychain Capital, and Samsung NEXT, Story mainnet launched February 2025. The 2026-08-04 audit confirms 4 clean keyless providers: the Story Foundation official endpoint (mainnet.storyrpc.io), Ankr (rpc.ankr.com/story_mainnet), Stakely (story-json-rpc.stakely.io), and PublicNode (story-rpc.publicnode.com). Excluded: Alchemy (key required), Infura (no story route), QuickNode (key required).
Methodology
Story: 4 free public RPC endpoints answering `eth_getBlockByNumber` every 60 seconds from us-east, eu-west and Singapore, ranked by 24h median. Ankr leads at 36 ms; the chain-official endpoint measures 39 ms. We measure the round-trip latency of a single, identical JSON-RPC call (`eth_getBlockByNumber("latest", false)`) against every no-key public Story endpoint that sustains continuous probing, 4 providers measured, every 60 seconds, from us-east, eu-west and Singapore. The harness classifies every response (ok / http_err / jsonrpc_err / stale / timeout) with a Story-scaled staleness gap (20 blocks at Story's ~2 s block time). The cross-chain view lives on the parent `rpc-capabilities` benchmark; this page is the Story-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: `{"jsonrpc":"2.0","id":<rotating>,"method":"eth_getBlockByNumber","params":["latest", false]}`. Plain HTTP POST, identical for every endpoint, no API key in any request. The request id rotates, but that does not guarantee a cache miss: many caches normalise `id` away. Measured 2026-10-08, fixed and rotating ids answer within 2 to 4 percent of each other.
- 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 Story-scoped view of the same harness, with the same exclusion rules.
- Chain scope: every query on this page is pinned to `chain="story"`. Provider coverage: 4 no-key endpoints.
Results: 4 free public Story RPC endpoints ranked by p50 latency (24h, 3 regions)
| № | Providers | p50 | p90 | p99 | Success |
|---|---|---|---|---|---|
| 1 | Ankr | 36 ms | 69 ms | 121 ms | 100.00% (n=4322) |
| 2 | Story Foundation | 39 ms | 49 ms | 74 ms | 100.00% (n=4316) |
| 3 | PublicNode | 68 ms | 117 ms | 301 ms | 100.00% (n=4316) |
| 4 | Stakely | 211 ms | 314 ms | 798 ms | 100.00% (n=4312) |
Public Story RPC endpoints measured
Chain ID 1514, currency IP. The 4 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.
Ankrhttps://rpc.ankr.com/story_mainnet36 ms100.0%
Story Foundationhttps://mainnet.storyrpc.io39 ms100.0%
PublicNodehttps://story-rpc.publicnode.com68 ms100.0%
Stakelyhttps://story-json-rpc.stakely.io211 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 Story RPCs work without an API key?
4 endpoints are probed on this chain: Story Foundation (https://mainnet.storyrpc.io), Ankr (https://rpc.ankr.com/story_mainnet), Stakely (https://story-json-rpc.stakely.io), and PublicNode (https://story-rpc.publicnode.com). Every listed endpoint was live-verified with a `eth_getBlockByNumber` POST returning a parsable response before inclusion.
How is Story RPC latency measured here, technically?
One identical `eth_getBlockByNumber("latest", false)` POST every 60 seconds against each provider from each of 3 regions, using the same plain HTTP client the rest of the RPC cluster uses. Wall-clock round-trip is recorded at millisecond precision; p50/p90/p99 are computed via Prometheus `quantile_over_time` over 24 hours. Responses are classified (`ok` / `http_err` / `jsonrpc_err` / `stale` / `timeout`) so an endpoint stuck on an old head or returning errors behind HTTP 200 is never ranked as fastest.
Source code github.com/ChainBench/OpenChainBench/tree/main/harnesses/rpc-capabilities