Skip to Content
Platform Ontology

Signed agent requests (Web Bot Auth)

An agent can sign its web requests so a site can check who sent them.

Gets silentlyWhen the page loads

Web Bot Auth uses HTTP Message Signatures (RFC 9421). The agent adds Signature, Signature-Input and a Signature-Agent header that points to a public key directory. The site fetches the keys and verifies the signature, so a user agent name cannot be faked. Google lists it as experimental for its own agent, and cloud agent platforms are adding it.

What it can and can't do

What the user does: Nothing for people. The agent platform signs for you

It can

  • Check a cryptographic signature on a request
  • Look up the operator's published keys
  • Allow known agents and rate limit the rest
  • Stop user agent spoofing

It cannot

  • Tell you what the agent will do
  • Work for agents that do not sign
  • Prove a person approved the action
  • Replace sign in

How it differs between platforms: Support is new and uneven. Sites must choose to honor it. A signature proves the operator, not the task or the person behind it.

Browser support

Version notes
  • Chrome: Sent by agent platforms, not by the browser

How a site asks for it

APISignature, Signature-Input and Signature-Agent request headers; key directory at /.well-known/http-message-signatures-directory
How access is grantednone
What the user seesNone
Needs a secure context (HTTPS)No
Needs a user gestureNo
How long it lastsNot listed
How to take it backNot listed
Inside an iframeNot listed

Typical flow

  1. Agent signs selected request parts with a private key
  2. Agent sends Signature, Signature-Input and Signature-Agent
  3. Site fetches the public key directory
  4. Site verifies the signature and trusts or denies the agent

Data you get

Shape: header
How often: per request

FieldTypeUnitRangePrecision
SignatureheaderNonesignature bytes for chosen request partsNot listed
Signature-InputheaderNonewhich parts were signed, created time, key id, tagNot listed
Signature-AgentheaderNoneURL of the agent's key directoryNot listed

Technical limits

  • Standards still in draft at the IETF
  • Only identifies the operator
  • Not a browser feature

The story

What it is

A signed envelope on each request. The site checks the signature the way a shop checks a stamp.

For you

You never see it. If you use an agent, the platform may sign its requests so sites can recognize it and treat it well.

For makers

Verify signatures against the published directory and check created and expires times. Use it for an allow list, not as proof of a safe request. Keep a fallback for unsigned agents.

Where you see it

TypeExampleApps
securityA site allows signed requests from a known agent and challenges the rest.Cloudflare
shoppingA retailer lets a verified shopping agent read stock without a challenge.None named
newsA publisher lets a signed AI fetcher read pages under its terms.None named
developerAn agent team signs requests so partner sites can recognize them.None named
enterpriseAn internal API accepts only signed agent calls.None named
travelA booking site gives signed agents a calmer rate limit.None named

Risks

  • Sites may favor big operators
  • Unsigned agents blocked by default

What the platform says

Good uses and abuse

Legitimate uses

  • Agent allow lists
  • Fewer false bot blocks

Known abuse

  • Excluding small or independent agents

Scores

ScoreValueMeaning
Sensitivity2 of 5How revealing the data is
Utility4 of 5How useful it is to honest apps
Friction0 of 5How much the user has to do
Fingerprint bits0Rough identifying entropy, when known

History

  • 2024-02, rfc: RFC 9421 HTTP Message Signatures published
  • 2025-05, all: Web Bot Auth announced by Cloudflare
  • 2026-03, all: Google reported to list Google-Agent with experimental Web Bot Auth signing

Sources

How well checked: Inferred from related behavior.

On this page