For AI agents: an LLM-friendly Markdown version of every page is available by appending .md to its URL or by sending an Accept: text/markdown request header. The full documentation index is at https://www.ankr.com/docs/llms.txt
Skip to main content

Nine chains leave the Public plan, and Swell and Fuel reach end of support

Ankr Team
Docs Team

Nine chains no longer answer keyless requests on rpc.ankr.com. Six of them need a Premium key from now on, three stay free once you sign in. Swell and Fuel reach end of support and are gone from the chain list. No method limits, error codes or rate limits changed anywhere else.

Deprecations and end-of-support​

Premium key required​

These six chains left both the Public and the Freemium plan. A keyless call now returns HTTP 403 with -32052, the same code you get for a chain that is not enabled on your key, and a Freemium key does not cover them either.

ChainWhat to do
AtletaUse a Premium key.
AvailUse a Premium key.
BitlayerUse a Premium key.
GravityUse a Premium key.
XaiUse a Premium key.
zkSync EraUse a Premium key.

Sign in, still free​

These three left the Public plan and stayed on Freemium, which is free. Sign in, create a project, and use the key it gives you.

ChainWhat to do
0GSign in and use your own key.
B2 NetworkSign in and use your own key.
SuiSign in and use your own key.

The service plans page now says 30+ chains on Public and 45+ on Freemium. Premium is unchanged at 80+.

Swell and Fuel​

Swell and Fuel reached end of support, mainnet and testnet in both cases. We removed them from the chain list and deleted their API reference pages; inbound links resolve to the chain list instead of returning a 404. If you still have a Swell or Fuel endpoint configured on Ankr, move off it. The Fuel network runs its own public endpoints, and the Fuel docs name them.

Worth checking on your side​

  • A keyless endpoint that used to work is the thing to look for. If you copied an endpoint without a key from a chain page or from one of the per-chain sites, that is what returns 403 now. The fix is a key, not a retry: -32052 does not clear on its own.
  • Nothing changed for the chains that stayed on Public. Same rate limits, same batch size, same block range.
  • No method changed. No method moved between plans, no error code changed meaning, and no rate limit moved on any plan.