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

11 posts tagged with "rpc"

View All Tags

Roundup: MONAD_TEN, Sui protocol 135, and the moved Agentic RPC paths now answer 301

Docs Team

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.

Roundup: Taiko Unzen, Arbitrum Nitro 3.11.3, and clients rolled forward on 30 chains

Docs Team

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.

New section: MCP servers for AI agents

Docs Team

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.

Roundup: Sui is retiring JSON-RPC, Bahamut end of support, and a rebuilt API reference

Docs Team

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.

New section — Verifiable RPC (vRPC)

Docs Team

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.