Whitechain Sepolia is in the docs
We serve the Whitechain Sepolia testnet on rpc.ankr.com/whitechain_testnet over HTTPS. Whitechain is an OP Stack Layer 2 with WBT as its gas token. The chain is now in the chain list, with its own API reference.
We serve the Whitechain Sepolia testnet on rpc.ankr.com/whitechain_testnet over HTTPS. Whitechain is an OP Stack Layer 2 with WBT as its gas token. The chain is now in the chain list, with its own API reference.
Harmony mainnet reaches end of support on Ankr RPC. The Harmony network stopped producing blocks on 10 September 2026, after the Harmony team sunset its Layer 1 and announced a migration of the ONE token to Ethereum. We retire the rpc.ankr.com/harmony endpoint and remove Harmony from the chain list. No method limits, error codes or rate limits changed on any other network.
We serve Robinhood Chain mainnet on rpc.ankr.com/robinhood_mainnet to Premium and Enterprise users, over HTTPS and WSS. The chain is now in the chain list, with its own API reference.
Filecoin's Calibration network activates network version 29 (Solstice) on 28 September at 12:59:30 UTC, and our Calibration nodes already run the release candidate that carries it. Sui mainnet moved to protocol 137, IOTA mainnet to protocol 36, and Ethereum mainnet and Sepolia to reth v2.6.0. We also corrected the 15 September end-of-support list: it now has eighteen endpoints, and one of the additions answered keyless calls.
Solana turned on Transaction V1 at the start of epoch 1035, on 15 September 2026 at about 01:00 UTC. Our nodes run Agave v4.2.2 and serve v1 blocks, so nothing changes on our side. Your side has one change to make: getBlock and getTransaction calls that still pass "maxSupportedTransactionVersion": 0 now fail with -32015 on almost every block, because almost every block already carries a v1 transaction.
Avalanche's Helicon upgrade activates on 22 September at 15:00 UTC, and our nodes already run the release that carries it. Core shipped an emergency hardfork, Sui moved to protocol 136, and Ethereum mainnet and Sepolia moved to reth v2.5.2. Separately, Solana activated Transaction V1 today, and that one needs a change in your client.
Eighteen endpoints reach end of support on Ankr RPC on 15 September 2026. Seven networks go entirely, testnets included, and six testnets and variants go while their network stays. Seventeen of the eighteen already require a Premium key. The vFlow Volta testnet also answered keyless calls, so a keyless or Freemium integration that used it needs to move. Xai, Syscoin and Rollux are not served on the Advanced API either. No method limits, error codes or rate limits changed on any network that stays.
From 15 September Kaia runs on full nodes, and how far back a call can reach changes. Tracing keeps working for recent history, roughly a day of blocks, and a state read at an explicit older block needs archive state that a full node does not hold. Everything else on Kaia stays as it is: the same endpoints on mainnet and testnet over HTTPS and WSS, the same rate limits, the same error codes, and the same method list apart from the five listed below.
Sixteen networks stopped answering keyless and Freemium calls on 31 August, 29 endpoints across mainnets and testnets. They need a Premium key from now on. Sui JSON-RPC moved off the keyless endpoint and stays free on Freemium. Swell reached end of support. No method limits, error codes or rate limits changed anywhere else.
Redbelly mainnet has been answering on rpc.ankr.com/redbelly_mainnet since late August, and it was missing from the chain list, so the only way to find the endpoint was to be told about it. It is documented now, with its own API reference, and the reference is explicit about the standard EVM methods this node does not implement.
Monad's MONAD_TEN activates on mainnet on 2 September at 14:30 UTC, and our nodes are already on the release that carries it. Sui moved to protocol 135 and Stellar to Protocol 28. On the docs side, the four Agentic RPC pages that moved to a top-level section now answer with a real 301 instead of a page that says 200 and redirects in the browser, and that includes the Markdown twin an agent fetches.
An agent that knows only rpc.ankr.com can now read what the deployment supports and who answers it, without a key and without a second hostname.
The agent-facing pages moved out of Node API into a top-level Agentic RPC section, and gained the two pages they were missing: a quickstart and a troubleshooting guide.
We published the TORPC specification and its reference implementation under open licenses, and the Agent RPC MCP server is now installable from npm.
Allora, Botanix, Corn, Horizen EON, Moonbeam and Tenet reach end of support on Ankr RPC and are gone from the chain list and the docs. Mantle Sepolia testnet is delisted too, while Mantle mainnet is unaffected. No method limits, error codes or rate limits changed anywhere else.
Nine of these upgrades tracked a hard activation, where a node left on the old version stops following the chain. Taiko's Unzen fork and Somnia's Jig fork both activated inside this window and we landed ahead of both. Monad testnet activated MONAD_TEN on 12 August, and our nodes were already on the release that carries it. Nothing changed in RPC method limits, error codes or rate limits.
Docs now cover the Ankr MCP servers: a read-only data plane that gives an AI agent chain data already decoded and compressed for a context window, and a control plane that manages your account, keys, usage, and notifications from an MCP client.
Two deprecations need your attention: Sui is retiring JSON-RPC network-wide, with the hard cutoff in mid-October, and Bahamut is no longer served. Alongside that, we rebuilt the Advanced API reference, split the per-chain RPC pages, and rolled node clients forward on roughly 25 chains. Eight of those tracked a network upgrade with a hard activation, where a node left on the old version stops following the chain.
Docs now cover Verifiable RPC (vRPC): cryptographically signed JSON-RPC and REST responses that prove they came from an approved, unmodified node running inside an Intel TDX hardware enclave. Your client verifies every response fail-closed, so you no longer have to take the operator's word that a reply is genuine.