Two discovery documents, served from the RPC host as well

An agent that knows only rpc.ankr.com can now read what the deployment supports and who answers it, without a key and without a second hostname.

Docs

• TORPC gained a Discovery section that lists both documents and where each one is served. The machine readable descriptor, with the protocol version, the negotiation headers, the tier meanings and the method list, answers at rpc.ankr.com/.well-known/torpc.json and at mcp.ankr.com/.well-known/torpc.json. It used to answer on the MCP host only.
• The agent card is new. It is an ERC-8004 registration file at rpc.ankr.com/.well-known/agent-card.json and mcp.ankr.com/.well-known/agent-card.json. It names the service, says what it does, and lists the two MCP endpoints: the keyless data plane and the OAuth gated management plane.

Worth checking on your side

• Nothing changed on the RPC service. No method limits, error codes, or rate limits moved. These are two static documents on paths nothing else uses.
• The card claims no on chain registration and no trust mechanism, because we have neither yet, and it states x402Support: false rather than leaving the question open.
• Read the served copy first. Both documents also ship in the @w3tech.io/agent-rpc-mcp npm package, and a packaged copy can lag what the deployment answers.