Legitimate verifiable agent traffic is blocked by the observed edge policy
AGENT-EDGE-001 · v1.0
Computed by Scovant Cloud — this check needs Scovant's own agent-identity fetch, which the open-source engine does not perform.
What it detects
An anonymous browser request was served, but the same request carrying a valid, verifiable Web Bot Auth signature was blocked or challenged.
Why it matters
The edge refuses exactly the agents that identify themselves cryptographically. The fix is an explicit allow path for verifiable identities — never disabling bot protection.
How to fix
Keep your bot protection turned on, and add an explicit allow path for verifiable identities — a verified-bot programme, or Web Bot Auth signature verification — so an agent that proves who it is is admitted instead of refused alongside anonymous automation. If agents are not welcome on this site, say so in robots.txt instead: an honest `Disallow` lets well-behaved, identified agents skip you cleanly. Never the third option: weakening bot protection is not the fix, and Scovant does not recommend it.
Example
GET / (anonymous) -> 200 OK; GET / (signed) -> 403
References
Last reviewed: 2026-09-01 · rule v1.0