Definition
HTTP Message Signatures is an IETF standard, published as RFC 9421 in February 2024, for creating and checking digital signatures over selected parts of an HTTP message, such as the method, host and certain headers. It defines the Signature-Input and Signature headers. Web Bot Auth uses it so bots and AI agents can sign their requests.
Why it matters
HTTP Message Signatures is the standard underneath most of the ways AI agents now prove who they are. When ChatGPT, a card network's shopping agent or another signed bot visits your store, the signature on that request follows RFC 9421.
You will rarely touch it directly. Your CDN, firewall or a plugin usually does the checking. But knowing the name helps. When a vendor says it verifies RFC 9421 signatures, that means it can confirm which service sent a request, not just what the request claims to be.
How it works
RFC 9421 is a Proposed Standard published by the IETF in February 2024. Its abstract says it "describes a mechanism for creating, encoding, and verifying digital signatures or message authentication codes over components of an HTTP message."
The sender picks which parts of the request to sign. These can be headers, or "derived components" such as @method, @authority and @path. It then adds two headers:
Signature-Input, which lists the signed components and parameters such as when the signature was created, when it expires and which key was used.Signature, which carries the signature itself.
The receiver rebuilds the same signed content and checks it against the sender's public key. If anything covered by the signature was changed, the check fails.
RFC 9421 is a general tool. It does not say where a bot's keys live or how a site should find them. Web Bot Auth adds those pieces for bots, including the Signature-Agent header and a key directory. OpenAI's documentation states that "Web Bot Auth uses the HTTP Message Signatures standard, RFC 9421." Visa says its Trusted Agent Protocol is "Built upon the foundational HTTP Message Signature standard". At the time of writing, the Web Bot Auth layer itself is still an IETF Internet-Draft, while RFC 9421 is finished.
Example
A signed request from an AI agent carries headers like these (shortened):
Signature-Input: sig1=("@authority" "signature-agent");created=...;expires=...;keyid="...";tag="web-bot-auth"
Signature: sig1=:...:
The first line says the signature covers the host name and the Signature-Agent header. Your firewall fetches the agent's public key, checks the signature over those exact values, and marks the request as verified or not. For the full picture, read Web Bot Auth: how AI agents sign their requests.
Sources
- RFC Editor: RFC 9421, HTTP Message Signatures · checked 17 Nov 2026
- Cloudflare: Web Bot Auth · checked 17 Nov 2026
- OpenAI: Agent access (ChatGPT signed requests) · checked 17 Nov 2026
- IETF webbotauth working group documents · checked 17 Nov 2026
- Visa: Visa Unveils Trusted Agent Protocol for AI Commerce · checked 17 Nov 2026