Web Bot Auth vs Personal Agent Protocol

Web Bot Auth vs Personal Agent Protocol: one proves the operator, the other proves the agent and its user.

11 min read
In short: Web Bot Auth signs each request with RFC 9421 HTTP message signatures and proves which operator's infrastructure sent it. The Personal Agent Protocol (Poppy) signs a Poppy-Session JWT per request and proves which personal agent sent it and that it acts for one of its users, with sign-in through the site's own OAuth server. An agent can use both, and the Poppy specification recommends it. Arcjet verifies both and reports them in one bot identity with SIGNATURE evidence, setting delegated only for Poppy.

What's the difference between Web Bot Auth and the Personal Agent Protocol?

Web Bot Auth vs the Personal Agent Protocol comes down to the question each one answers. Web Bot Auth proves which operator's infrastructure sent a request, with an RFC 9421 HTTP message signature and keys on the operator's domain. The Personal Agent Protocol (Poppy) proves which personal agent sent a request and that it acts for one of its users, with a signed session token and sign-in through the site's own OAuth server.

Both protocols use public-key signatures and keys that the signer publishes on its own domain, so a valid signature can't come from anyone else. They differ in who signs, what the signature covers, and whether a user is part of the picture. They aren't competitors: an agent can use both on the same request, and the Poppy specification recommends it. Meta's Muse publishes a Web Bot Auth key directory and a Poppy client_id.

Arcjet publishes this comparison. Specification details come from RFC 9421, the IETF draft draft-ietf-webbotauth-httpsig-protocol, and the Personal Agent Protocol 1.0 specification, reviewed on November 16, 2026. Specifications and adopters change, so check the linked sources before you decide.

Which question does each protocol answer?

Web Bot Auth answers "which operator sent this request?", and Poppy answers "which agent sent this request, and is it acting for a user?". The first is an infrastructure identity. The second is a delegated identity, tied to a pseudonymous user and, when the user signs in, to an OAuth grant with scopes the user approved.

Web Bot Auth: the operator

A Web Bot Auth request carries three headers. Signature-Agent names the operator's origin. Signature-Input lists the signed components and parameters, with the tag web-bot-auth. Signature carries the signature bytes. The verifier fetches the operator's keys from /.well-known/http-message-signatures-directory on that origin and checks the signature.

A valid signature proves that the holder of the operator's key signed the request. When the operator is a hosted browser platform, such as Browserbase, Kernel, or Cloudflare Browser Run, the signature identifies the platform, not the customer whose agent runs on it. It says nothing about a user.

Poppy: the agent and its user

A Poppy request carries a Poppy-Session JWT. The agent's client_id is an HTTPS URL that returns its metadata, including a jwks_uri. A key from jwks_uri signs a delegation that authorizes a short-lived key for at most 24 hours, and that delegated key signs a session token for each request. The session names the agent, a pseudonymous user ID that's different at each business, and the request's method and URL.

A verified session proves which agent sent the request and that the agent acts for one of its users. When the user signs in through the business's OAuth server, the request also carries an access token, and the session binds to it with a hash in the ath claim.

How do Web Bot Auth and Poppy compare side by side?

The following table compares Web Bot Auth and the Personal Agent Protocol across nine areas, as of November 2026:

AreaWeb Bot AuthPersonal Agent Protocol (Poppy)
What it identifiesThe operator that holds the signing key.The personal agent, and that it acts for one of its users.
Signer

The operator's key, usually Ed25519, named by its JWK thumbprint in keyid.

A key from the agent's jwks_uri signs a delegation with ES256 or PS384. The delegated key signs each session with ES256.

Key discovery

Signature-Agent names an origin. Keys live at /.well-known/http-message-signatures-directory.

The client_id URL returns metadata. Keys live at its jwks_uri, on the same domain.

What the signature covers

Components the signer picks. @authority and signature-agent are required; @method and @path are recommended.

Method and URL (htm, htu), the business's issuer (aud), the time (iat), and the access token hash (ath) when signed in.

Replay window

Until expires. The draft recommends no more than 24 hours. An @authority-only signature works on any path on that host.

A freshness window that the business chooses, such as one minute, for one method and URL. The business can also reject a reused jti.

User involvementNone.

A pseudonymous user ID per business. Optional OAuth sign-in with scopes the user approves.

Site setup

None to receive signatures. You verify them, or use a product that does.

Publish /.well-known/poppy.json. To offer sign-in, run an OAuth authorization server with the metadata the specification lists.

Standards status

RFC 9421 is a published standard. The Web Bot Auth profile is an IETF working group draft.

Specification 1.0, published November 14, 2026, developed by Sierra, Meta, and design partners. Not an IETF document.

Adopters

ChatGPT agent, Google's agent, DuckAssistBot, Browserbase, Manus, Meta Muse, and others.

Meta Muse publishes a client_id. Instinct, Manus, Meta, and OpenAI are personal-agent design partners.

For Web Bot Auth, OpenAI documents its signatures in its cloud browser allowlisting guide, and Google describes its implementation as experimental. For Poppy, the path to 1.0 page lists the design partners on both the agent side and the company side.

Can an agent use both protocols?

Yes. The Poppy specification recommends that a personal agent also sign its requests with Web Bot Auth, and that the signature cover the poppy-session header and the authorization header when present. The two layers do different jobs, and neither replaces the other.

The operator signature lets traffic-management tools that know Web Bot Auth recognize the agent on any site, including sites that don't publish poppy.json. The session gives a site that opts in a delegated identity and a path to account access through its own OAuth server. A missing operator signature doesn't make a session invalid, and a valid operator signature doesn't create a session.

Meta's Muse shows the pattern as of November 2026. It publishes Web Bot Auth keys at https://muse.ai/.well-known/http-message-signatures-directory and the Poppy client_id https://muse.ai/poppy/agent.json. Meta's Poppy post calls Muse "the first personal agent to support Poppy". For more information, see how to detect Meta's Muse AI agent.

What doesn't either protocol prove?

Neither protocol identifies the person behind the agent, and neither proves that the person approved the action in the request. A signature proves who holds a key. A session adds that the agent acts for some user, with an ID that's different at every business and contains no personal information.

The following limits apply to each protocol:

  • Web Bot Auth identifies an operator, not a customer. A hosted browser platform signs for every customer that runs on it. Rate limit and authorize platform traffic as a group of unrelated clients.
  • A Web Bot Auth signature can be replayed until it expires. A captured signature that covers only @authority works on any path on that host.
  • A Poppy session doesn't identify the user. The sub is pseudonymous, and an agent can issue a fresh one for each anonymous browsing session.
  • A Poppy session doesn't prove approval. The specification says that a message from the agent doesn't authorize the account action it requests. The access token and its scopes say what the user granted, and your code decides whether this action fits.

Both protocols identify the client. Authorization for signups, purchases, and data changes stays in your application. For more information about the delegation model, see AI agent on-behalf-of identity.

How does Arcjet verify Web Bot Auth and Poppy?

Arcjet verifies both protocols in the detectBot rule and reports the result in one bot identity, so you write one policy rather than two integrations. A verified Web Bot Auth signature or Poppy session gives SIGNATURE evidence and sets operator to the signer's hostname. Only a verified Poppy session sets delegated to true. Arcjet verifies the signers and agents in the open source well-known-bots catalog, any other Web Bot Auth signer that you name with a SIGNED_BOT: entry, and Poppy sessions only for agents the catalog vets. It doesn't fetch a client_id or directory that a request names on its own. You read the identity in your route handler, next to the user and the account, in the JavaScript, Python, or Go SDK. For the reference, see agents that act for a user and verify signed bots with Web Bot Auth in the Arcjet docs.

Which protocol should you implement?

Which protocol you implement depends on whether you run an agent or a site, and whether the agent acts for individual people. The following sections list the signals for each choice.

If you operate a bot or agent

Implement Web Bot Auth if any of the following apply:

  • You run a crawler, fetcher, or cloud browser and want sites to recognize it without an IP allowlist.
  • You run a hosted browser platform and want sites to tell your traffic apart from other cloud networks.
  • You want recognition on every site, including sites that publish nothing for agents.

Add Poppy if any of the following apply:

  • Your agent acts for individual people at businesses, such as tracking orders or changing bookings.
  • You need account access through the business's own sign-in, instead of the person's password.
  • You can publish a client_id metadata document and a jwks_uri on your domain.

If you run a site

Verify Web Bot Auth signatures if you want to name signed crawlers and cloud browsers and allow or deny them by route. Publish poppy.json if you want personal agents to act for your customers, and you have, or can add, an OAuth authorization server for sign-in. Verify both if agents reach checkout, account, or support routes, so that your handlers see the operator, the agent, and whether it acts for a user in one identity.

For more information about the evidence each method provides, see AI agent evidence levels. For more information about the other identification methods, see how to identify AI agents and bots.

Frequently asked questions

What is the difference between Web Bot Auth and the Personal Agent Protocol?

Web Bot Auth proves which operator's infrastructure sent a request, with an RFC 9421 HTTP message signature and keys at /.well-known/http-message-signatures-directory. The Personal Agent Protocol (Poppy) proves which personal agent sent a request and that it acts for one of its users, with a Poppy-Session JWT signed by a key the agent delegates from its jwks_uri, and optional sign-in through the site's OAuth server.

Do I need both?

As a site, verify Web Bot Auth to name signed crawlers and cloud browsers, and publish poppy.json if you want personal agents to act for your customers. As an agent operator, sign with Web Bot Auth for recognition on every site, and add Poppy if your agent acts for individual people. The Poppy specification recommends that agents do both.

Which one should a bot operator implement?

A crawler, fetcher, cloud browser, or hosted browser platform implements Web Bot Auth. A personal agent that acts for individual people at businesses also implements Poppy, publishing a client_id metadata document and a jwks_uri on its own domain.

Which one identifies the user?

Neither. Web Bot Auth has no user at all. A Poppy session proves that the agent acts for a user, but its sub is a pseudonymous ID that's different at each business and contains no personal information. Neither proves that the user approved the action in the request.

Are they standards yet?

RFC 9421 HTTP Message Signatures is a published IETF standard, and the Web Bot Auth profile on top of it is an IETF working group draft. The Personal Agent Protocol published its 1.0 specification on November 14, 2026, developed by Sierra, Meta, and design partners outside the IETF.

How does Arcjet handle Web Bot Auth and Poppy?

Arcjet verifies both in the detectBot rule and reports one bot identity: SIGNATURE evidence and the signer's hostname as operator for either protocol, with delegated set to true only for a verified Poppy session. It verifies signers and agents from the open well-known-bots catalog, plus Web Bot Auth signers you name with SIGNED_BOT: entries.

AI runtime security in your code

Protect your AI agent workflows with Arcjet

Arcjet runs inside your application, where it can use runtime context to enforce agent actions and budgets, detect prompt injection, and protect sensitive information before a workflow acts.