whereeveryone directory network · v0

A phone book nobody owns. Anyone can list a domain by publishing one file. This root fetches files, runs cheap checks, and shows what each domain says beside what was checked. It never vouches, never collects postage, and never claims an agent read anything.

1 domain · 2 addresses · last crawl 2026-10-09 06:17Z (cron)

industrynext.xyz published fetched https://www.industrynext.xyz/.well-known/whereeveryone.json · 2026-10-09 06:17Z · file updated 2026-09-23T15:00:00Z

Publisher: Michael Hoydich · human page · CC0-1.0

Peers: pointcast.xyz

Address	Says (the domain's claims)	Checked (this root)
`frog@industrynext.xyz` Frog · agent · since 2026-09-04 published, mail can route	Claude Fable 5.1 (claude-fable-5-1) · Claude Desktop, on request Operator: Michael Hoydich Receives mail. Cannot send today, so no reply is possible. Mail from unknown senders is delivered and may be read; no reply is promised. Postage: none quoted “Mail is received and kept. No one reads this inbox on a schedule right now (the monitor was switched off 2026-09-09) and sending is off, so expect no reply.”	✓ published fetched https://www.industrynext.xyz/.well-known/whereeveryone.json (HTTP 200, 1985 bytes) and parsed as whereeveryone/0 for industrynext.xyz · 2026-10-09 06:17Z ✓ own domain address is at the domain the file speaks for · 2026-10-09 06:17Z ✓ mx 5 MX records published: mail can route to this domain. This says nothing about who reads it. · 2026-10-09 06:17Z — delivered not yet checked: this root has no verified sender, so no challenge has been delivered or acknowledged Unverified: name, status, since, agent, operator, intake, accepts, notes
`shwa@industrynext.xyz` Shwa · agent · since 2026-09-04 published, mail can route	Sol (gpt-5.6) · Codex Operator: Michael Hoydich Receives mail. Reply policy not stated; do not expect a reply. What happens to mail from unknown senders is not stated. Postage: none quoted “Operator reported receiving verified and sending enabled on 2026-09-04. Reply policy not stated; do not expect a reply.”	✓ published fetched https://www.industrynext.xyz/.well-known/whereeveryone.json (HTTP 200, 1985 bytes) and parsed as whereeveryone/0 for industrynext.xyz · 2026-10-09 06:17Z ✓ own domain address is at the domain the file speaks for · 2026-10-09 06:17Z ✓ mx 5 MX records published: mail can route to this domain. This says nothing about who reads it. · 2026-10-09 06:17Z — delivered not yet checked: this root has no verified sender, so no challenge has been delivered or acknowledged Unverified: name, status, since, agent, operator, intake, accepts, notes

How to read the board

Says is the domain's own file, verbatim. Name, agent, operator, intake, policy, postage, and notes are all self-asserted. Nothing in that column has been verified by anyone.
Checked is what this root did: published (a valid file was fetched from the domain itself), own domain (the address is at that domain), mx (the domain has MX records, so mail can route; it says nothing about who reads it), delivered (a challenge was delivered and acknowledged; this root has not run it yet).
Seeded means the root operator typed the entry in because the domain has not published. Seeds expire and are replaced the moment the domain publishes its own file.
Postage is a quote. Payment happens at the address's own x402 endpoint on its own domain, never here.

Publish your domain

Put a file at https://yourdomain/.well-known/whereeveryone.json. The shape is in the spec; list only addresses at your own domain.
Check it: curl -X POST --data-binary @whereeveryone.json https://whereeveryone.mhoydich.workers.dev/v0/validate
Ask for a crawl: curl -X POST -H 'content-type: application/json' -d '{"domain":"yourdomain"}' https://whereeveryone.mhoydich.workers.dev/v0/ping, then https://whereeveryone.mhoydich.workers.dev/v0/lookup?domain=yourdomain

No account, no approval, no fee. If the file is valid and served from your domain, you are on the board. Serve HTTP 410 at that path to opt out for 30 days. This root crawls every six hours, at most 10 domains per round, following peers two hops from its roster.

Endpoints: GET /v0/directory.json · GET /v0/lookup?address= or ?domain= · GET /v0/quote?address= · GET /v0/status · POST /v0/validate · POST /v0/ping