Know Your AgentDEVerify evidence
Menu

State of the standards for AI agents

The approaches for evidence from AI agents are evolving fast. This page records where each approach stands, what KYA verifies of it and what changed most recently. It is updated monthly.

, Founder, Innopulse Consulting GmbH
Published

Current status per approach

ApproachOriginStatusIn KYA
Verifiable IntentMastercardSpecification and reference implementation public, Apache 2.0fully verified
AP2Googleopen protocol; variant using the layers of Verifiable IntentVI variant verified, classic JSON recognized
Trusted Agent ProtocolVisaSpecification and sample code on GitHub, own product termsSignature following RFC 9421
Web Bot AuthCloudflare, IETFDraft in the IETFfully verified
Agentic Commerce ProtocolOpenAI, Stripeopen specification for checkoutoutside the scope of verification
MCPAnthropic, open projectSpecification with authorization based on OAuthEvidence around tool calls
SD-JWT VCIETFDraft, in use in government walletsfully verified
OID4VPOpenID FoundationVersion 1.0 finalResult of the presentation
Swiss e-IDFederal governmentAct approved on 28 September 2025, introduction on the federal schedulededicated profile planned
EUDI walletEUeIDAS 2.0 in force since 20 May 2024, wallets of EU states being builtdedicated profile planned

As of 13 October 2026. The linked specifications are authoritative.

Chronology

DateEvent
2 August 2026European regulation on artificial intelligence: most remaining provisions apply, including the transparency obligations under Article 50 (according to the regulation text)
October 2025Visa introduces the Trusted Agent Protocol, developed with Cloudflare
28 September 2025Swiss voters approve the federal act on the e-ID
September 2025Google introduces AP2; OpenAI and Stripe publish the Agentic Commerce Protocol
July 2025OpenID for Verifiable Presentations reaches version 1.0 final
May 2025Cloudflare proposes Web Bot Auth for signed requests from bots and agents
March 2025The MCP specification adds authorization based on OAuth
November 2024Anthropic introduces MCP; the product liability directive (EU) 2024/2853 brings in software
1 August 2024European regulation on artificial intelligence enters into force
20 May 2024eIDAS 2.0 (Regulation (EU) 2024/1183) enters into force
February 2024RFC 9421 HTTP Message Signatures is published

How this page is maintained

New entries are added when an approach publishes a new version, a law enters into force or KYA starts verifying an approach. The page carries a review date; KYA's release gate requires an update at least every 45 days. The article Agent protocols compared puts the approaches in context.

Frequently asked questions

How often is this page updated?

Monthly and additionally for important events. The release gate requires an update at least every 45 days.

Which approaches does KYA verify in full?

Verifiable Intent, Web Bot Auth, HTTP signatures following RFC 9421, SD-JWT VC, JWS, status lists, RFC 3161 timestamps and its own kya-pack/1 and kya-chain/1 formats.

Can I report a development?

Yes. Notes on new versions or approaches reach the operator through the contact page.

Sources

  1. RFC 9421: HTTP Message Signatures: https://www.rfc-editor.org/rfc/rfc9421
  2. Verifiable Intent (Mastercard): https://github.com/agent-intent/verifiable-intent
  3. Agent Payments Protocol (AP2): https://github.com/google-agentic-commerce/AP2
  4. Trusted Agent Protocol (Visa): https://github.com/visa/trusted-agent-protocol
  5. Agentic Commerce Protocol: https://www.agenticcommerce.dev/
  6. Model Context Protocol: Spezifikation: https://modelcontextprotocol.io/specification
  7. OpenID for Verifiable Presentations 1.0: https://openid.net/specs/openid-4-verifiable-presentations-1_0.html
  8. Verordnung (EU) 2024/1183 (eIDAS 2.0): https://eur-lex.europa.eu/eli/reg/2024/1183/oj
  9. Verordnung (EU) 2024/1689 über künstliche Intelligenz: https://eur-lex.europa.eu/eli/reg/2024/1689/oj
  10. E-ID: offizielle Informationen des Bundes: https://www.eid.admin.ch/de