How it relates to AgenID
Web Bot Auth works at the request layer: this HTTP request was signed by this key. AgenID works at the operator layer: this agent was declared by this operator, in a manifest bound by an operator-signed proof that anyone can resolve. AgenID does not authenticate individual requests today, so the two are complementary rather than competing.
The working group also lists related drafts, including one on a registry and a Signature Agent card and one on use cases. These are Internet-Drafts whose scope may change, so this page does not describe their details.
Why it matters
A website that can verify a request signature knows the traffic came from a particular key holder. Pairing that with a resolvable operator identity would tell the site who is accountable for the agent behind the key. Request signatures say this request came from this key; an operator identity says which accountable party stands behind the agent.
The reference deployment at agenid.com issues nothing above L1_REGISTERED today. L2 and higher require a VerificationAssertion signed by a root authority key, and that key has not been created yet.
What it does not mean
A signed request authenticates the sender; it does not decide what the bot is allowed to do. Access policy remains the site's choice. AgenID makes no claim about any site's support for these drafts.