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

Roundup: NEAR key lists page at 100, Avalanche drops avax.getAtomicTxStatus, NEAR heads to protocol 88

Ankr Team
Docs Team

On NEAR mainnet, view_access_key_list now returns at most 100 keys per response, and an unpaginated request for an account with more than 100 keys fails. On Avalanche C-Chain, avax.getAtomicTxStatus is gone. Both changes come from upstream releases our nodes now run, nearcore 2.14.0 and AvalancheGo v1.15.2. We did not change any rate limits, and no other method limits, error codes, batch caps or range caps changed. nearcore 2.14.0 also carries NEAR's move to protocol version 88, with voting from 4 November. Ethereum mainnet is on reth v2.9.0, which runs a new EVM, and the x402 manifest now lists paid JSON-RPC on 126 networks, payable on Monad, Base or Solana.

Already announced since the last roundup​

Docs​

  • NEAR view_access_key_list paging. The View access key list reference documents limit, after_key and last_key, and the 100-key cap. It also shows the right request_type; it used to say view_access_key.
  • Avalanche C-Chain methods. We removed avax.getAtomicTxStatus from the Avalanche reference, and avax.getAtomicTx now says it replaces it.
  • Team accounts in the Platform Swagger UI. The Platform Swagger page explains that your API key always belongs to your personal account, so a request without group returns your personal data, for example a zero balance while the funds sit on the team. Call GET /auth/group for the team's groupAddress and pass it as group. Team balance and transaction history are open to the Owner, Admin and Finance roles, and GET /auth/group/rules lists the roles allowed on each endpoint.

Agentic RPC​

  • The x402 manifest lists paid JSON-RPC on 126 networks. https://x402.rpc.ankr.com/.well-known/x402 now has 149 resources: the 23 priced Agent RPC MCP tools and 126 JSON-RPC routes of the form POST https://x402.rpc.ankr.com/<chain>. On 12 October it listed one JSON-RPC route, Monad mainnet. Whitechain mainnet (whitechain) and Whitechain Sepolia (whitechain_testnet) joined on 30 October. An unpaid request gets HTTP 402 with x402 offers in USDC on Monad (eip155:143), Base (eip155:8453) and Solana mainnet, plus an MPP challenge on Solana. Prices did not change: $0.001 per call, with eth_chainId, net_version and web3_clientVersion free on JSON-RPC and describeMethods and listChains free on MCP. /pricing has the full list.
  • Agent RPC MCP 0.2.7 is on npm and in the MCP Registry. @w3tech.io/agent-rpc-mcp and the MCP Registry entry io.github.w3tech/agent-rpc-mcp moved from 0.2.4 to 0.2.7 on 22 October. A local stdio install now starts without ANKR_API_KEY: tools/list answers, and every tool call returns INVALID_KEY with a link to get a key until you set one. A blank ANKR_API_KEY falls through to ANKR_RPC_KEY. Every top-level tool input field now has a description.

Network upgrades​

  • NEAR mainnet: nodes on nearcore 2.14.0, which moves the protocol from version 86 to 88 in two steps. Voting for protocol 87 starts on 4 November at 00:00 UTC and for protocol 88 on 6 November at 00:00 UTC. Upstream expects each upgrade 7 to 14 hours after its voting epoch ends.

Client versions​

Deprecations and end-of-support​

  • Avalanche C-Chain avax.getAtomicTxStatus, from 27 October 2026. AvalancheGo deprecated the method in v1.15.0 and removed it in v1.15.2. On rpc.ankr.com/avalanche-c it now returns -32000 with rpc: can't find method "avax.GetAtomicTxStatus". Call avax.getAtomicTx instead: it returns the transaction once it is accepted and an error until then.

Worth checking on your side​

  • If you list access keys on NEAR, page with limit and after_key for any account that can hold more than 100 keys. An unpaginated request for such an account returns -32000 with Account <account> has more than 100 access keys; use a paginated view_access_key_list request, and a limit above 100 is lowered to 100.
  • NEAR timeouts say how far a transaction got. A TIMEOUT_ERROR from tx, EXPERIMENTAL_tx_status, or send_tx and broadcast_tx_commit with wait_until now carries a cause in info. EXPERIMENTAL_tx_status is also available as tx_status; the old name keeps working.
  • NEAR protocol 87 and 88 change what transactions can do. After activation, a contract no longer receives 30% of the gas its calls burn, a DelegateV2 action is rejected with ActionsValidationError::RemovedProtocolFeature, and a receipt that exceeds the 4 MB storage proof limit fails with ReceiptStorageProofSizeExceeded on any action, not only FunctionCall. If you decode NEAR action errors against a fixed list, add the new variants; the release notes list all of them.
  • Avalanche platform.getCurrentValidators returns two new fields for auto-renewed validators, restakedValidationRewards and restakedDelegateeRewards.
  • reth v2.9.0 on Ethereum mainnet runs a new EVM. Upstream replaced revm with evm2 for block execution, RPC and the tracing inspectors. The release notes list no change to debug_* or trace_* output, but the tracers are a new implementation, so if you compare traces against stored results, re-run a sample. eth_getProof responses now follow the execution-apis spec.
  • No other RPC method limits, error codes, batch caps or range caps changed.