ARO · Operational
Web Bot Auth request signing
Web Bot Auth request signing is an Agent Readiness Optimization check in the Bot access group.
Version agent-readiness-2026-10
What is this benchmark?
Web Bot Auth request signing
Web Bot Auth request signing is an Agent Readiness Optimization check in the Bot access group.
Why it matters
Request signing is for a site that sends signed requests. A content site is not scored on it.
How SiteGlue evaluates it
HTTP request to a well-known or published URL. Spec: https://datatracker.ietf.org/doc/draft-meunier-web-bot-auth-architecture/. Catalog agent-readiness-2026-10.
- Passing criteria
- The published signal for Web Bot Auth request signing is present and readable.
- Failing criteria
- The scan requested the signal and it was missing, blocked, or malformed.
- Not verified
- The check was not selected, the probe did not run, or evidence was inconclusive. Not verified is never scored as 0.
- Not applicable
- Optional checks can be recorded without changing the ARO score.
Scoring weight: 0. Evidence: Public HTTP, HTML, or DNS evidence for Web Bot Auth request signing. No private credentials.
Example results
Pass
Agents can read a valid Web Bot Auth request signing signal on the public site.
Fail
Web Bot Auth request signing is missing, blocked, or not machine-readable.
Recommended fixes
- Request signing is optional for a site that only serves content. This screen does not generate signing keys.
Related benchmarks
Frequently asked questions
Does a missing optional check lower my ARO score?
No. Weight 0 checks are recorded and shown. They do not change the score.
Is this a live ChatGPT test?
No. ARO is a website audit. Optional live walks are Test With AI Agents.
Run the ARO audit.