This can be pointed at a labeler to check that it is correctly deployed and operating. It checks four layers:
- Identity: DID document contains an
atproto_labelerservice entry of typeAtprotoLabelerand a#atproto_labelsigning key; the labeler's PDS holds a validapp.bsky.labeler.service/selfrecord with policies. - HTTP:
com.atproto.label.queryLabelsresponds with well-formed labels and handles pagination/schema correctly. - Subscription:
com.atproto.label.subscribeLabelsWebSocket firehose emits valid frames and supportscursor=0backfill. - Crypto: Label signatures verify against the declared
#atproto_labelkey.