Definition
Signature-Agent is an HTTP request header used in Web Bot Auth. It carries an https URL that points to where a bot or AI agent publishes its public signing keys, so a website can fetch them and check the request's signature. ChatGPT, for example, sends the value "https://chatgpt.com" on its signed requests.
Why it matters
The Signature-Agent header is how a signed agent tells your site who it is and where to check. A User-Agent string is just a name. Signature-Agent points to a place on the operator's own domain where its public keys live, and the request's signature has to match one of those keys.
For a store owner, it is the value you will see in logs and firewall rules when you allow a specific signed agent, such as ChatGPT's agent.
How it works
Signature-Agent is part of Web Bot Auth, which builds on HTTP Message Signatures. The IETF working group's current draft, dated October 29, 2026, says it "defines the Signature-Agent header field for in-band key discovery, a key directory format based on JWKS, and a well-known URI at which that directory is served." That well-known address is /.well-known/http-message-signatures-directory.
The draft is clear that the header alone proves nothing. In its words: "A client picks the value it sends, so an unresolved Signature-Agent is a claim rather than an identity." It only becomes an identity once your site, or a service in front of it, fetches the keys from that URL and one of them verifies the signature. The Signature-Agent header must itself be covered by the signature, so it can't be swapped in transit.
Two formats exist. Earlier drafts used a plain quoted URL. The current draft uses a labelled form, such as sig1="https://example.com", and says verifiers may still accept the older form, which some deployments still send. This is still an Internet-Draft, so details can change.
Cloudflare documents the setup from the bot operator's side: host a key directory at the well-known path, then "Construct a Signature-Agent header that points to your key directory."
Example
OpenAI documents that ChatGPT's signed browser requests carry:
Signature-Agent: "https://chatgpt.com"
OpenAI tells site owners to confirm that the header "exactly matches" that value, including the quotation marks, and publishes its keys at https://chatgpt.com/.well-known/http-message-signatures-directory. Your firewall fetches those keys and checks the signature. A request with the same header but no valid signature is unverified. See the ChatGPT agent profile and how to tell if a visitor is really ChatGPT.
Sources
- IETF: draft-ietf-webbotauth-httpsig-protocol-01, HTTP Message Signatures for automated traffic · checked 17 Nov 2026
- OpenAI: Agent access (ChatGPT signed requests) · checked 17 Nov 2026
- Cloudflare: Web Bot Auth · checked 17 Nov 2026