agentspeed.
Rubric / Discoverability

Web Bot Auth

discoverability.web_bot_auth
weight 1deterministicemerging

The site signals support for the Web Bot Auth IETF draft (HTTP Message Signatures over a known JWKS) so well-behaved agents can prove identity.

Adoption of what this check tests is still climbing, so failing it is an opportunity rather than a defect. Remediation lists rank these after established fixes, and the weight moves only when measurement earns it.

Definition
Check ID
discoverability.web_bot_auth
Category
Discoverability
Weight
1
Counts toward the score
Yes.
Evaluated by
A fixed rule with no threshold of our choosing. The same input always produces the same verdict.
Standard maturity
emerging
Canonical spec
https://datatracker.ietf.org/doc/draft-meunier-web-bot-auth-architecture/
Introduced in
r2026.04.2
Retired in
Still active.
History
Every change to the instrument— including the versions that changed this check
Machine-readable
/rubric.json— this check, and every other, as data
How often this check is right

No rate published. Too few labelled cases to publish a rate: 1 flagged case (30 needed to publish), 1 defective case (30 needed to publish). The counts are the honest answer here. The matrix behind discoverability.web_bot_auth is 3 labelled cases — reported here rather than turned into a percentage that would read as more certain than the evidence is.

Corpus v1, measured under rubric r2026.11.0. Full method and every other check at /rubric/accuracy.

How to fix it
Publish a JWKS at `/.well-known/http-message-signatures-directory.json` and accept signed requests per the Web Bot Auth draft. Lets you allow trusted agents while keeping a default-deny posture for the rest.
Does your site pass this check?

Free scan, 30 seconds, no signup — this check and the other 35, with the exact evidence for each verdict.

Scan my site →
Web Bot Auth · discoverability.web_bot_auth · AgentSpeed