# Web Bot Auth

Category: Agent readiness
Version: 1.0.0

## Goal
Identify your own bot traffic with Web Bot Auth signed requests so receiving sites can verify and trust them.

## Issue
The audited site did not satisfy the Web Bot Auth readiness check.

## Fix
Publish a JWKS at /.well-known/http-message-signatures-directory containing the public keys you use to sign outgoing bot requests, so receiving sites can verify those requests via HTTP Message Signatures (RFC 9421). Rotate keys on a regular cadence and keep the previous key in the JWKS until in-flight requests have aged out.

## Validation
- Confirm content types, payload shape, and discoverability from the public web surface.
- Verify against fresh public evidence, not only local source changes.
- Re-run the relevant isitready.dev scan before claiming the issue is closed.

## Copyable Fix Prompt
```text
Outcome: make this single public-readiness issue pass for the audited site.

Goal: Web Bot Auth for https://example.com

Issue: The audited site did not satisfy the Web Bot Auth readiness check.

Fix: Publish a JWKS at /.well-known/http-message-signatures-directory containing the public keys you use to sign outgoing bot requests, so receiving sites can verify those requests via HTTP Message Signatures (RFC 9421). Rotate keys on a regular cadence and keep the previous key in the JWKS until in-flight requests have aged out.

Skill: /.well-known/agent-skills/web-bot-auth/SKILL.md

Docs: https://blog.cloudflare.com/web-bot-auth/, https://datatracker.ietf.org/doc/html/draft-meunier-http-message-signatures-directory

Validation: Confirm content types, payload shape, and discoverability from the public web surface.

Requirements: preserve existing product behavior, add or update relevant tests, and validate public response shape/content type where applicable.

When done, tell the user to re-run the public scan at https://isitready.dev so they can verify this issue now passes. Do not claim it is fixed until a fresh report confirms.
```