ChangeGamer

How to Sign Browser Agent Requests With Web Bot Auth

Part 7 of Browser agents and agentic browsing in production · 1,372 words · ~6 min read · published · updated · Markdown variant

How a team running a browser agent signs its outbound requests with Web Bot Auth as of 18 November 2026: Ed25519 key, signed key directory, the three headers, the Signature-Agent divergence, Cloudflare Verified status and key rotation.

In short

  • Signing browser agent traffic with Web Bot Auth needs an Ed25519 key pair, a public key directory at /.well-known/http-message-signatures-directory that is itself signed, and three headers on every request: Signature-Input, Signature and Signature-Agent.
  • As of 18 November 2026 Web Bot Auth is not an RFC: the only IETF working group document is draft-ietf-webbotauth-httpsig-protocol-01, dated 29 October 2026, so implementations track a moving draft and Cloudflare documentation.
  • Cloudflare documentation of 8 October 2026 sends Signature-Agent as a quoted URI string and says the dictionary form fails, while the IETF draft of 29 October 2026 requires the dictionary form, so test against the verifier you target.
  • A valid Web Bot Auth signature proves who is calling and grants nothing else: Browserbase states it does not grant access or sign an agent into a user account, and sites apply their own policies.
  • Cloudflare Verified status as of 1 July 2026 depends on honest self-identification and non-abusive behaviour, so a signed agent that ignores robots.txt can still be removed from the allowlist.

Part of the Agentic Browsing in Production: Building, Securing and Preparing for Browser Agents guide.


A team signs a browser agent's traffic by generating an Ed25519 key pair, publishing the public key in a signed directory on a domain it controls, and attaching three headers to every outbound request. The mechanism is Web Bot Auth, and as of 18 November 2026 it is an IETF draft, not an RFC. The pillar places it among the launch decisions, and the Web Bot Auth reference holds the background and dated history. This article is the operator's sequence: what to build, where implementations disagree, and what a signature does not buy you.

What is the standards status of Web Bot Auth?

Web Bot Auth is an Internet-Draft, not an RFC, as of 18 November 2026. The IETF webbotauth working group is listed as active, and its only document is draft-ietf-webbotauth-httpsig-protocol-01, "HTTP Message Signatures for automated traffic", dated 29 October 2026, with intended status Standards Track. It replaced draft-meunier-web-bot-auth-architecture and absorbed the key directory draft. Related individual drafts, such as hosted key directories and a signed-agent metadata header, are not working group documents.

Cloudflare's documentation, last updated 8 October 2026, still cites the older draft-meunier names. Build for the verifier you want to satisfy and expect to revise.

How do you create the key and the signed directory?

Generate an Ed25519 key pair, publish the public half as a JWK Set at /.well-known/http-message-signatures-directory, and sign that directory response. Note the plural "signatures": Cloudflare's docs and the working group draft both use it, while the corpus reference dated 7 August 2026 spells it singular, which is superseded. Cloudflare's docs say it supports the Ed25519 algorithm and show OpenSSL for key generation, with WebCrypto as an alternative.

# Generate the private key and derive the public key (keep private.pem out of any image or repo)
openssl genpkey -algorithm ed25519 -out private.pem
openssl pkey -in private.pem -pubout -out public.pem

The directory requirements from Cloudflare's page of 8 October 2026:

In ChangeGamer's reading, signing the directory is what lets a verifier trust that the keys really come from the domain that serves them.

Which headers go on each request?

Every signed request carries Signature-Input, Signature and Signature-Agent, and the Signature-Input tag must be web-bot-auth. Cloudflare requires the keyid to be the same JWK thumbprint, created and expires as Unix timestamps, and recommends a nonce. The covered components must include @authority. Cloudflare recommends @query over @query-params, does not support @status, and including the parameters sf, bs, key, req or name fails verification. This illustrative block uses placeholder values only and shows the Cloudflare form of Signature-Agent; the IETF draft requires the dictionary form, sig1="https://agent.example.com":

Signature-Agent: "https://agent.example.com"
Signature-Input: sig1=("@authority" "signature-agent");created=1700000000;expires=1700000060;keyid="<jwk-thumbprint>";tag="web-bot-auth";nonce="<random>"
Signature: sig1=:<base64-signature>:

Set expires about a minute after created. Cloudflare says a minute is often sufficient and keeps no nonce database, so the short window is the replay defence. Cloudflare says to add Content-Digest only if there is zero risk of the message being altered on its way to Cloudflare, so not for an unencrypted message proxied there.

Which Signature-Agent format should you send?

Send the form your target verifier documents: Cloudflare's documentation and the IETF draft disagree as of 18 November 2026. Cloudflare's docs (8 October 2026) want Signature-Agent as a double-quoted https URI string, listed in the Signature-Input components, and say the dictionary form such as sig2="..." fails verification. The working group draft (29 October 2026) says the header is a Dictionary Structured Header and that signers MUST send the dictionary form.

Source Date Signature-Agent form
Cloudflare Web Bot Auth docs updated 8 October 2026 Quoted URI string; dictionary fails
draft-ietf-webbotauth-httpsig-protocol-01 29 October 2026 Dictionary; signers MUST send it

We have not tested either against a live verifier. If you target Cloudflare, follow its docs and re-check them against the draft each quarter, because the working group draft is the later document and may become the standard.

How do you sign requests from inside a real browser?

No source we fetched gives a recipe for signing from a browser driven over CDP, so what follows is ChangeGamer's inference. A browser engine makes the requests, which means your agent code never sees the outgoing HTTP message unless you intercept it. Each signature covers the request's @authority and a created/expires window, so a fixed header set once at browser launch cannot carry valid signatures across different hosts or over time.

The practical shapes are request interception that signs each request as it leaves, or a small signing proxy between the browser and the network. Also decide whether to sign only top-level navigations or every subresource such as images and scripts, since the browser sends both. For where the CDP connection fits, see remote browsers and anti-bot.

Do managed browsers sign for you?

Possibly, but only one vendor documents it. Browserbase documentation read on 18 November 2026 says it "offers Web Bot Auth in beta" with access by request, and that Verified is offered on its Scale plan. Whether it signs for you, and with its own key or yours, is not documented, and we have not tested it. Per the corpus reference, Cloudflare's 28 August 2025 post listed Browserbase and Anchor Browser as early adopters.

How do you get Verified at Cloudflare?

Submit your key directory URL in the Cloudflare dashboard under Manage Account, Configurations, Bot Submission Form, with Verification Method "Request Signature". Status shows under BotBase, Submission history, as Waiting For Review, Accepted, Rejected or Cancelled.

Cloudflare's concept docs say that since 1 July 2026 a signed agent counts as Verified, and that BotBase records whether a bot is Direct or Intermediary. Direct means a single, narrow operator. Intermediary means an agentic service that a wide range of end users can operate, so each action may come from a different person and trust is transitive. Verified needs honest self-identification (a signature, a published IP list with a stable user-agent, or reverse DNS) plus non-abusive behaviour: obey robots.txt and crawl directives, keep reasonable rates, and do not evade site preferences. Breaching that can get you removed from the allowlist. Zones can also opt out of signature verification through Cloudflare Support.

What does a signature not grant?

A signature proves identity and grants nothing else. Browserbase says "A valid signature doesn't grant access or sign your agent into a user account." The site still applies its own policy, including the AI crawler policy tokens and robots.txt, and your agent's login state is a separate risk covered in logged-in sessions and blast radius. On the receiving side, fraud and abuse from agent traffic covers what sellers do with verified identity. For the general identity landscape see agent identity and authentication, and for how sites count this traffic see measuring AI agent traffic and should you block AI crawlers.

How do you rotate keys?

Publish the new public key in the directory before you sign with it, sign with the new key, then remove the old one once its last signature has expired. This sequence is ChangeGamer inference, as no fetched source documents a rotation procedure. Because the directory carries one signature per key and signatures live about a minute, the overlap can be short. Keep private keys in a secrets manager, never in the browser image, and keep an honest, contactable User-Agent as well.

Does ChangeGamer sign its own requests?

ChangeGamer does not sign anything yet. Verified at the repository on 18 November 2026, changegamer.ai serves security.txt plus API catalog, agent-access and MCP discovery files, but no http-message-signatures-directory. Its /api/grader outbound fetch sends only ChangeGamer-Grader/1.0 (+https://changegamer.ai/grader) as a User-Agent, with no Signature headers. The backlog calls Web Bot Auth the strongest candidate of the eight protocols triaged, so signing is planned, not implemented. A separate A2A trust question is in trusting a remote agent.

Frequently asked questions

Is Web Bot Auth an official internet standard?
No. As of 18 November 2026 Web Bot Auth is an IETF Internet-Draft, draft-ietf-webbotauth-httpsig-protocol-01 dated 29 October 2026, not an RFC. It builds on RFC 9421 HTTP Message Signatures, which is a published standard, but the bot-specific profile can still change.
Do I still need a User-Agent if my browser agent signs its requests?
Yes, keep an honest, contactable User-Agent alongside the signature. The Web Bot Auth reference treats signing as additive to that layer, and Cloudflare lists a stable user-agent with a published IP list as an alternative route to Verified status, so signing is additive rather than a replacement.
How long should a Web Bot Auth signature be valid?
Cloudflare says a minute is often sufficient and does not keep a nonce database, so a short expiry is its replay defence. The IETF draft is looser, recommending no more than 24 hours between created and expires, so in our view the shorter Cloudflare value is the safer choice.
Does Browserbase sign requests with my key or its own?
Browserbase documentation read on 18 November 2026 does not say whether its Web Bot Auth beta signs with a Browserbase key or a customer key. Ask the vendor before depending on it, because the answer decides whose identity a site sees.

#web-bot-auth #http-message-signatures #browser-agents #cloudflare #ed25519 #verified-bots #browserbase

Put this corpus inside your own agents

This guide is free and stays free. The reference corpus behind it — machine-readable contracts, verified primary sources, continuously refreshed — is the paid product: a €5 starter key unlocks every premium reference for one agent via API; a €25 corpus license delivers the full corpus as RAG / fine-tuning data with an explicit AI-use grant; the €150 enterprise license adds commercial redistribution rights.

Agents: this page as Markdown · JSON · offers at /api/pricing.json · payment methods at /api/payment.json · single-resource access via HTTP 402 (how that works)