MapGraphSeamsCalendarIntroductionDisclosureMethodFor agents and tools

Updated weekly, new versions on Mondays · Corrections: open an issue

KYAPay (Skyfire)

Industryspecificationcore entry

Verified 2026-10-14. Status as of 2026-10-13. All entries.

Seams: S3

Status

Individual Internet-Drafts named for the OAuth Working Group (WG) (draft-skyfire-oauth-*); WG stream or adoption: not found on the datatracker, 2026-10-13 (the pages of kyapay-token and using-kyapay-tokens show "(No stream defined)"). On 2026-10-02 the author announced new revisions of five drafts: kyapay-token-02, using-kyapay-tokens-01, amr-values-02, id-verification-02 and aml-methods-01 (datatracker date 2026-10-01 for all five). The datatracker lists two more documents of the family, kyapay-token-exchange-01 (2026-07-19) and kyapayprofile-02 (2026-06-20, replaced by kyapay-token), seven in all. The Technical Plenary and Advisory Committee (TPAC) breakout proposal #39 (KYAPay: Verified Agent Identity and Payments for Ubiquitous Agentic Commerce) is open on 2026-10-13 with one comment and no assigned slot; the datatracker shows no revision of kyapay-token-exchange after -01 of 2026-07-19.

Relevance

KYAPay defines a signed JWT carrying verified agent and human identity (KYA) and payment credentials (PAY), so that merchant security infrastructure can distinguish human-authorised agents from malicious bots. The author's announcement of 2026-10-02 describes the token as a "JWT token providing claims about the person or organization authorizing an agent to act, the agent platform, the agent instance, and optionally a payment method". On the oauth list the token is discussed among bot managers, CDNs and site policy engines.

Committed next

Boundary

A participant review of 2026-09-23 reads hid, aid and apd as identifying principal, agent and platform, not the authority delegated.

Sources

Overlaps

W3C Agentic Web Working Group (draft charter), IETF Web Bot Auth (webbotauth WG), Mastercard Agent Pay

Neighbours in the map

Neighbours of KYAPay (Skyfire) in the map Each circle is an entry of the map and links to its page; the colour is the kind of body behind it, a filled circle is a core entry and a dashed circle a context entry. The entry in the middle, with the entries it overlaps and the entries named by the same seams. Overlaps (8)Share a seam (9)W3C Agent Identity Registry Protocol Community Group (W3C, context)W3C Agent Identity Regi… W3C Agentic Web Working Group (draft charter) (W3C, core)W3C Agentic Web Working… W3C Web Payment Security Interest Group (W3C, context)W3C Web Payment Securit… WebMCP (Draft Community Group Report, Web Machine Learning CG) (W3C, context)WebMCP IETF Web Bot Auth (webbotauth WG) (IETF, core)IETF Web Bot Auth Individual IETF drafts on the seller side (IETF, core)Individual IETF drafts… DIF Trusted AI Agents Working Group (Linux Foundation, context)DIF Trusted AI Agents W… Mastercard Agent Pay (Industry, core)Mastercard Agent Pay IETF agentproto (Agent Communication Protocols WG) (IETF, core)IETF agentproto S3 x402 (Linux Foundation, core)x402 S3 Browser vendor positions on WebMCP (WebKit, Mozilla, Chrome, Edge) (Independent, core)Browser vendor position… S3 OpenID Foundation AuthZEN Working Group (agent authorization drafts AARP and COAZ) (Independent, context)OpenID Foundation AuthZ… S3 Agentic Commerce Protocol (ACP) (Industry, core)Agentic Commerce Protoc… S3 Personal Agent Consent & Trust Protocol (PACT), published by Decagon with Instinct (Industry, core)Personal Agent Consent… S3 Personal Agent Protocol (PAP, "Poppy"), published by Sierra with Meta (Industry, core)Personal Agent Protocol S3 Universal Commerce Protocol (UCP) (Industry, core)Universal Commerce Prot… S3 Visa Trusted Agent Protocol (TAP) (Industry, core)Visa Trusted Agent Prot… S3 KYAPay

Solid lines: overlaps declared by one of the two entries. Dashed lines, coloured by seam: entries named by the same seam (S1 to S4) in the seams note. Every node is a link.

Evidence and coverage

Read
Datatracker search for draft-skyfire and the pages of kyapay-token and using-kyapay-tokens, 2026-10-13 (seven documents: kyapay-token-02, using-kyapay-tokens-01, amr-values-02, id-verification-02, aml-methods-01, kyapay-token-exchange-01, kyapayprofile-02); datatracker listing of 2026-10-02 (it named four, kyapay-token-02, token-exchange-01, using-kyapay-tokens-01, kyapayprofile-02); the announcement of 2026-10-02 on the oauth list names five; oauth list from 2026-08-01, subject filter (142 of 505 messages), KYAPay threads read.
Not read
The pages of the other five drafts on the datatracker (stream and state), skyfire-xyz repositories; IETF 126 session; kyapay.org beyond main page; adopters named in the announcement; threads excluded by the subject filter.
Not found
Not found in the messages read, 2026-10-03: the merchant's own identity, product identity, prices, checkout.

Open proposals

ProposalAuthorDateStateLink
TPAC 2026 breakout on KYAPay (agentic commerce on the existing web); no slot assigned yet.Michael B. Jones and a co-author2026-10-01openhttps://github.com/w3c/tpac2026-breakouts/issues/39