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

Redbelly mainnet is in the docs, including the methods its node does not have

Ankr Team
Docs Team

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.

Docs​

  • Redbelly is in the chain list. Redbelly carries the mainnet endpoint, the MetaMask settings (chain ID 151, RBNT), and the supported and unsupported method lists. The API reference documents 25 methods, each with a request you can run from the page against a demo key.
  • The gaps are written down rather than implied. Most EVM chain pages here describe the same method set. Redbelly's node does not serve all of it, so the page names what is missing instead of leaving you to discover it from an error code.

Worth checking on your side​

  • Redbelly is HTTPS only. A WebSocket connection upgrades and will answer plain calls, but eth_subscribe returns -32085, so there is no subscription path. Poll with eth_getLogs instead: the window is capped at 10,000 blocks per call and a larger range returns -32062. Block time runs roughly 30 to 50 seconds, so polling once a minute from lastProcessed + 1 keeps each window small.
  • Filter methods are blocked, and this is deliberate. eth_newFilter, eth_newBlockFilter, eth_newPendingTransactionFilter, eth_getFilterChanges, eth_getFilterLogs and eth_uninstallFilter are stateful and pin a client to one node, which does not survive our routing. eth_getLogs is the supported replacement.
  • net_version and net_listening are not implemented. The node answers -32601 for both, unlike every other EVM chain we serve. Read the chain ID with eth_chainId, which returns 0x97.
  • There is no debug_* and no trace_*, on any service plan. The node exposes the eth, rbn, rpc, txpool and web3 modules only, so tracing is not something an Enterprise plan can switch on here.
  • No RPC method limits, error codes, batch caps or range caps changed anywhere else in this window.