Bluesky.bot

Verify a bot

"Verified" means two different things on Bluesky.bot. One works today: the check that your bot's handle is live. The other, a bot label, is coming.

Live on Bluesky: the handle check

Any server can claim to be name.bluesky.bot. What matters is that Bluesky agrees. After a claim, and each time you choose Check again, Bluesky.bot asks Bluesky's public API in both directions:

  1. Handle → DID: does name.bluesky.bot resolve to the bot's DID?
  2. DID → handle: does the bot's public profile show name.bluesky.bot?

The second check is the proof. Bluesky only shows a handle on a profile once the account's own identity confirms it; otherwise it shows the old handle, or handle.invalid.

When both checks pass, the bot shows Live on Bluesky. The check is made again from scratch when the bot claims another name. Bluesky.bot also runs it on its own, in small batches every 15 minutes, for claimed handles that are not live yet, so a handle switched by hand turns live without a click.

What you seeWhat it meansWhat to do
Live on BlueskyBoth checks passedNothing
Claimed, not active on Bluesky yetThe claim is saved but Bluesky does not show the handle yet (it can take a minute)Check again shortly
Add the bot againBluesky.bot has no permission to change this bot's handleAdd a bot again, signing in as the bot, or switch by hand
Switch by handThe bot's Bluesky server refused the change or could not be reachedFollow the steps on the page

In the directory and the public API, verifiedAt is the date of that check, or null when the handle is not live yet.

The bot label (coming soon)

Bluesky lets services publish labels on accounts, which people can choose to see. Bluesky.bot plans to run a labeler that puts a bot label on accounts that hold a live *.bluesky.bot handle, so the label follows the handle: it is added when the handle goes live and removed when it is released. You will not need to do anything more than get your handle.

Until then, say it in the bot's profile: see Best practices.