Why is this entity important for governed agent execution?
It defines one of the control points that keeps autonomous behavior within explicit authority and risk limits.
Glossary Entry
What is KYA — Know Your Agent?
Know Your Agent (KYA) establishes verifiable on-chain identities for autonomous AI agents using W3C DIDs and A2A Agent Card verification.
Overview
Know Your Agent (KYA) establishes verifiable on-chain identities for autonomous AI agents using W3C DIDs and A2A Agent Card verification.
KYA is Layer 1 of the Agentic Control Plane stack — the foundational identity layer every downstream enforcement mechanism depends on. Before an AI agent can be governed, sanitized of injection attempts, or authorized to sign a transaction, it must have a verifiable identity. KYA establishes that identity — anchored cryptographically, not claimed.
DeAgenticAI’s Agentic Control Plane enforces cryptographic policy over AI agent authority — separating what an agent can do from what it is authorized to do — in Web3 and enterprise financial environments. KYA is the mechanism by which that authority separation becomes identity-specific: each agent’s policy, spending limits, and escalation paths are assigned to its verified identity, not to a generic process or application.
How does it work?
-
1
Define the execution boundary
Identify where this concept sits in the agent execution path and what decisions it governs.
-
2
Evaluate policy and risk implications
Map how this mechanism interacts with authorization, risk scoring, and escalation controls.
-
3
Enforce at signing or execution time
Explain how enforcement occurs at runtime and what is blocked when conditions are not met.
-
4
Record auditable outcomes
Capture approvals, denials, and context so teams can validate behavior under review.
Why does this matter?
This entity defines a core control-plane mechanism and should be linked from all related implementation and architecture pages.
Frequently Asked Questions
How does this connect to policy and signing?
This concept should map directly to policy evaluation and the final execution boundary where authorization is enforced.
Where should teams reference this term?
Use it consistently in solution pages, compare pages, and technical guides so the internal knowledge graph remains coherent.