Skip to content

Resources: Web Bot Auth, and how AI agents prove who they are - #79

Merged
EugeneDymo merged 6 commits into
resources/content-marketplacesfrom
resources/web-bot-auth
Nov 16, 2026
Merged

EugeneDymo merged 6 commits into
resources/content-marketplacesfrom
resources/web-bot-auth

Conversation

@KonstantinMirin

Copy link
Copy Markdown
Contributor

Stacked on #77. Two new Resources pages on how AI agents identify themselves, for a publisher's product and revenue teams. Website only; no proto change.

Web Bot Auth (/resources/web-bot-auth/). Web Bot Auth (WBA) is a passwordless, cryptographically proven identity for AI agents. The hero shows a signed request with its Content-Digest, Signature-Agent, Signature-Input and Signature headers, and the site fetching the public key from the agent's key directory. The page then covers:

  • how the check works, in four steps;
  • what it changes for a publisher;
  • which agents sign today, with each one's status;
  • key directories, rotation and revocation, including how Cloudflare's key registration differs from fetching the directory when a signature arrives;
  • what to ask your CDN and your team;
  • choosing which agents you sell to;
  • the debate at the IETF;
  • how FORA uses it;
  • the detail for engineers.

How AI agents prove who they are, and what they may do (/resources/agent-identity/). Four questions: who the agent is, whom it acts for, what it may do, and who pays. For each, what answers it and where a publisher meets it. Then:

  • a signature next to an OAuth token;
  • OAuth and MCP, with a flow diagram;
  • card networks, Sign in with ChatGPT and World ID;
  • anonymous credentials;
  • other schemes with whether each matters now.

Components. A new ResourceTable that becomes compact cards on phones. PointList and Callout points no longer require a title. Two new status tags, Experimental and Preview.

Figures. Seven hand-drawn figures under public/resources/web-bot-auth/ and one under public/resources/agent-identity/.

Every claim about another company quotes or links its own documentation, numbered in each page's source list.

Checks. npm run build, npm test, npm run routes, ROUTES_BASE_REF=fora/main npm run routes:check and scripts/check-doc-conformance.sh all pass. Both pages were checked at 1280 px and 390 px.

Note on the diff. Until #77's branch is updated, this diff also shows f1bc7e2 ("Edge function: list Fastly with the other platforms"). That commit belongs to #77 and drops out of this diff once #77 is pushed.

A guide to Web Bot Auth for publishers and engineers: who signs, how much
is signed, what changes in your stack, what a signature proves, the allow
list, the argument over who gets in, the other ways to identify an agent,
and how FORA uses it. Five figures, 54 numbered sources.

Adds ResourceTable (a table that turns into cards on phones), the
Experimental and Preview status tags, and optional lead-ins for PointList
and Callout points.
…e credentials

A band after "What a signature proves": a token issued at sign-up, OAuth
or a JWT, and Web Bot Auth side by side, how permission is attached on top,
and how FORA keeps the two apart. ResourceTable can label every cell on
phones and sets even widths for four columns.
Web Bot Auth now opens by showing how a signature is checked, in both
directions, and gives key directories, rotation and revocation their own
band, with what to ask your CDN and your team. The other identity schemes
move to /resources/agent-identity/: four questions about any agent (who it
is, whom it acts for, what it may do, who pays), a signature against an
OAuth token, OAuth and MCP step by step, card networks, sign-in providers,
anonymous credentials, and the other schemes with whether each matters now.
…ly signers; registries and key registration corrected
@EugeneDymo
EugeneDymo merged commit 1b28f74 into resources/content-marketplaces Nov 16, 2026
2 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants