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

TORPC is open source, and Agent RPC MCP is on npm

Ankr Team
Docs Team

We published the TORPC specification and its reference implementation under open licenses, and the Agent RPC MCP server is now installable from npm.

Docs​

  • TORPC now points at the normative document. The specification is in w3tech/torpc under CC0-1.0, so you can implement it without asking us, and the machine readable descriptor .well-known/torpc.json sits in the server's public repository. The reference decoder, the typed transform rules, and the benchmark harness are in w3tech/torpc-js under Apache-2.0.
  • Agent RPC MCP gained a local option. The hosted endpoint at https://mcp.ankr.com/rpc is unchanged, and the same server is on npm as @w3tech.io/agent-rpc-mcp if you would rather run it yourself over stdio. The page carries the client config, and the source is in w3tech/agent-rpc-mcp-public.

Worth checking on your side​

  • Nothing changed on the RPC service, and nothing changed in the hosted MCP server. No method limits, error codes, or rate limits moved. It is the same seventeen read tools, and the local package calls the same endpoints with your key, so your plan's limits and charging apply exactly as they did. One difference when you run it locally: the key travels in ANKR_API_KEY instead of a header.
  • The specification is a draft, and conformance is not a claim yet. The EVM tier 1 and tier 2 rules are normative, tiers 3 and above are reserved, and the conformance suite is a scaffold holding a single golden case. No implementation, ours included, calls itself TORPC conformant today.
  • The tier is still negotiated per call. Publishing the spec does not change that. A response above the proxy's compression budget comes back at tier 0, and _meta.tier reports the tier actually applied, so keep reading it before you look for decoded fields.