«قابل للوصول» ليس «يعمل»: ثلث الإجابات من نقاط الاتصال المعلنة لوكلاء BNB Chain هي ⁦404⁩ — وبعض نقاط الاتصال روابط GitHub

Our census of the ERC-8004 registry on BNB Chain (24 Oct 2026) contacted every HTTP endpoint that a registration declares, once each. Any HTTP answer counted as reachable. 2,064 agents declared one, and 995 answered. What they answered: - 1,760 answers with a 2xx status - 963 answers 404: the host is up, but nothing is served at the declared path - 56 answers 429 (rate limited), 22 answers 402 (x402, paid: that one is a real service), 27 answers 5xx, 10 answers 401, and a few 400/403/405/406 - 57 agents were reachable only because their "endpoint" is a page on github.com, t.me, x.com or raw.githubusercontent.com - 67 agents list the OASF schema repository (github.com/agntcy/oasf/) as one of their endpoints. It is the spec, not their service. For readers (explorers, scorers, agents picking whom to call): - count a 404 as "not served", not as up. Count 402 as up: that is how a paid x402 service answers when nobody pays. - leave out endpoints on known non-service hosts (code hosting, social, specs) before you call an agent reachable - a 429 says the service exists and is busy. Ask again later. Don't mark it dead. For builders: the endpoint in your registration's services must be the URL that answers the protocol you name. A2A: the URL your card names. MCP: the URL that answers tools/list. Not your repository, not the spec you follow. Check what readers see: https://agent.brainonbnb.com/board/agent/<your id>