Tool documentation

How the declared automation checker works

What the Bluesky automation checker reads, its single-labeler scope, cache and time limits, and why absent declarations cannot prove an account is human.

What is read

The checker reads a public profile from Bluesky’s AppView. A profile’s own, non-negated bot self-label is the Automation declaration. At most one bot labeler is consulted: Bluesky.bot, when its service is available. The result attributes each of its current values. Other labelers are not covered.

Meaning of the states

Present means that this source returned the signal. Absent means that a source answered and the signal was not present. Unknown means the source could not be read or its coverage was incomplete. An absent Automation label cannot establish that the account is human. An AI-generated descriptive label alone does not establish automation.

A live name.bluesky.bot handle must be the handle the public profile shows, and our resolver must name the same DID. A public listing adds its creator-selected category, public operator line and usage card. It is re-read after a cache hit, so a removed listing is not replayed from cache.

Time limits and privacy

AppView reads have four-second deadlines and bounded response bodies. Successful signal lookups use the shared one-minute identity cache and the shared per-IP and site-wide quotas. Input is not persisted or logged. The public bio is quoted as text, never analysed to infer automation; hidden or unavailable profiles do not expose it here.

See the guide to declared signals, the label inspector and the editorial policy.

Declared automation checker

See the automation signals an account makes public.