§56 · Lane 8 — Agent Infrastructure Standards & Toolchain
IETF Internet-Draft — Web Bot Auth Architecture verifiable agent identity for metered and gated access
Meunier et al. (2026) · draft-meunier-web-bot-auth-architecture-05
Bibliographic data
- Title
- Web Bot Auth Architecture (draft-meunier-web-bot-auth-architecture-05, 2 March 2026)
- Authors / Issuing body
- Thibault Meunier (Cloudflare) and contributors; co-authored with Google
- Venue / Publisher
- Internet Engineering Task Force (IETF) — individual Internet-Draft feeding an Active Working Group
- Year
- 2026
- Designation
- Internet-Draft
- Licence
- IETF Trust LP — refer to publisher for full licence terms.
How to cite
Meunier et al. (2026). Web Bot Auth Architecture (draft-meunier-web-bot-auth-architecture-05, 2 March 2026). Internet Engineering Task Force (IETF) — individual Internet-Draft feeding an Active Working Group. https://datatracker.ietf.org/doc/draft-meunier-web-bot-auth-architecture/.
An IETF Internet-Draft (revision 05, 2 March 2026) specifying how an automated agent cryptographically signs its outbound requests using Ed25519 over RFC 9421 HTTP Message Signatures, so a verifying origin or fronting edge can confirm the agent's identity. The core architecture draft has no formal standing in the IETF standards process and now feeds an Active Working Group formed on 23 October 2025.
Why it matters for NETEVO
Verifiable agent identity is the prerequisite for every priced or gated access decision: an edge cannot charge, tier or admit an agent it cannot identify. This draft is the request-signing scheme that the largest edge operators already treat as their strongest verification tier — a signed request is admitted to the verified tier, while an unsigned one falls to a heuristic, spoofable tier.
The identity layer is the least mature and most consequential gap in the machine-payment stack. The core architecture remains an individual Internet-Draft with no formal standing, the verified-agent registry is not yet cross-vendor, and the scheme signs the operator rather than the end user. Any architecture that meters or gates agent access should treat verified identity as an emerging dependency, not a settled one.
The same identity primitive underpins both metered content access and agent-mediated transactions, which is why it bridges the agent-infrastructure and content-economy material.
Where NETEVO applies this
- AI Traffic Monetisation Whitepaper — load-bearing — verifiable agent identity is the prerequisite for the verified-versus-unverified pricing tier
- Agent-Ready Lending Whitepaper — supporting — the shared agent-identity rail beneath agent-mediated credit