KYA-OS COMMUNITY

THE RAILS

KYA-OS sits underneath the protocols you already speak. An agent proves who it is once — the same signed proof then projects onto every registry, transport, and credential format downstream.

AGENTS
agent
orchestrator
human principal
KYA-OS
identity credentials delegation consent proof audit
signed proof
PROJECTS ONTO
DISCOVERY — where agents are found
A2A AgentExtension
MCP catalog / server.json
NANDA AgentFacts
TRUST — what the proof is made of
W3C DIDs + VC 2.0 · identity
Bitstring + cheqd DLR · revocation
TRANSPORT — how the proof travels
OAuth 2.1 + DPoP

one identity in · one signed proof · every surface out

Write once, project everywhere

KYA-OS does not ask ecosystems to migrate. Write the Entity Card once - the single source of truth - and each downstream protocol gets a projection of it, emitted by the same code path and gated by the same proof posture. Update the card and every projection stays consistent.

A peer that does not speak KYA-OS ignores the extra metadata and loses nothing; a compatible peer gains cryptographic certainty about who it is talking to. All four discovery projections carry that graceful-degradation contract.

project onto A2A

Emits an AgentCard capability extension, scoped to agent entities. Activated via the A2A-Extensions header; unaware peers ignore it.

project onto MCP

An always-by-ref catalog index row plus Entity Card metadata in the MCP Registry _meta extension point — the index stays cheap, the card lazy-fetches.

project onto NANDA

An AgentFacts JSON-LD projection populating NANDA's shipped owner slot; namespaced kya:* keys degrade gracefully.

see all 19 standards rows, with evidence ->