Protocol Schemas
The canonical registry for the KYA-OS protocol's JSON Schemas. Every schema is versioned and immutable, served at a stable $id URL with open CORS. Reference one to validate KYA-OS messages, or to resolve $ref pointers from any JSON Schema validator.
Handshake
KYA-OS Handshake Request
Client-initiated handshake request to establish a KYA-OS session with nonce-based replay protection.
raw .jsonKYA-OS Handshake Response
Server response to a successful handshake request, establishing session context.
raw .jsonProof
KYA-OS Detached Proof
Cryptographic proof binding an MCP tool request/response pair to an agent's identity and session context.
raw .jsonDelegation
KYA-OS Delegation Credential
W3C Verifiable Credential containing a KYA-OS delegation with CRISP constraints.
raw .jsonKYA-OS StatusList2021 Credential
W3C StatusList2021 Verifiable Credential used to publish delegation revocation or suspension state.
raw .jsonAuthorization
KYA-OS Needs-Authorization Error
Error returned when a tool call requires user authorization.
raw .jsonAudit
KYA-OS Audit Record
Versioned, portable audit log record summarizing a single verified KYA-OS tool call.
raw .jsonDiscovery
KYA-OS Discovery Document
Well-known discovery document served at /.well-known/mcp for KYA-OS service discovery.
raw .jsonFrequently asked
What is KYA-OS?
KYA-OS is an open protocol for verifiable AI-agent identity, delegation, and proof. It defines how an agent proves who it is and what authority it holds, enforceable at the edge and compatible with the web. The protocol is donated to the Decentralized Identity Foundation (DIF).
How do I reference a KYA-OS schema?
Every schema is published at its canonical $id URL under schema.kya-os.org/v1/protocol/. Point a JSON Schema $ref or $schema field directly at that URL. All documents are served with open CORS and the application/schema+json content type, so validators and $ref resolvers can fetch them from any origin.
What schema format is used?
Schemas are versioned (v1.0.0) JSON Schema documents, immutable at their $id: a published schema never changes in place, so consumers can pin a version with confidence. New revisions are published at a new version path rather than overwriting an existing one.
Where is the KYA-OS specification?
The full protocol spec lives at kya-os.org, which spans every binding — MCP, HTTP, and more. For MCP specifically, see kya-os.org/mcp; its reference implementation and these schemas are in the donated core repo, decentralized-identity/kya-os-mcp.