chunks/5232-db5923cda78a4960.js","6465","static/chunks/6465-6b79f1dc957ae3f4.js","9388","static/chunks/9388-d1a745fd53a10850.js","4902","static/chunks/4902-40271c136eb736f1.js","1508","static/chunks/1508-abbc58115cbb4fd0.js","6125","static/chunks/6125-6f7cbc86df4f2503.js","7771","static/chunks/7771-66979ce602088329.js","7660","static/chunks/7660-f5d56ac6a9ee6cc8.js","4147","static/chunks/4147-ef3df161a800b88b.js","9783","static/chunks/9783-e1d5b54e9718b38b.js","8084","static/chunks/8084-f1229cc5d0501fe0.js","2024","static/chunks/2024-e03e13f5faa34f45.js","7796","static/chunks/app/%5Blocale%5D/(default)/server/%5Bname%5D/%5Bauthor_name%5D/page-c3a3facf548ee943.js"],"default"] 24:T34bf,# Identity [![Lint](https://github.com/agntcy/identity/actions/workflows/lint.yml/badge.svg?branch=main)](https://github.com/marketplace/actions/super-linter) [![Contributor-Covenant](https://img.shields.io/badge/Contributor%20Covenant-2.1-fbab2c.svg)](CODE_OF_CONDUCT.md)

Welcome to the Identity repository

--- **AGNTCY Identity** provides a secure and verifiable method to uniquely identify agents through open and decentralized techniques. Each agent is assigned a universally unique identifier, backed by verifiable credentials (VCs). **AGNTCY Identity** enables to bring your own identity using conventions like IDs assigned by Identity Providers (e.g., Okta) or Agent Cards (e.g., Google’s A2A), or be assigned an ID following standards (e.g., W3C DIDs). This component ensures that every agent in the **AGNTCY** ecosystem has a verifiable, universally unique identity, enabling secure authentication, trusted communication, and interoperability across diverse multi-agent systems, regardless of the identity assignment method.

- The ID is linked to a ResolverMetadata object for secure and automated verification. - The ID can be linked to one or more Agent Badges. Why? Multiple badges can provide nuanced, task-specific access to different systems without over-privileging the agent. Agent Badges contain Verifiable Credentials (VCs), which include: - The Agent's ID - Schema definition (e.g., OASF) - Metadata for authentication and other security needs. > [!NOTE] > This same structure applies to MCP Servers and MASs, ensuring consistency across all identity-bearing entities in the IoA. ## 📚 Table of Contents - 🚀 Architecting [Agentic Trust](#-architecting-agentic-trust) - 🌟 [Features & Main Components](#-features--main-components) - ⚡️ [Get Started](#%EF%B8%8F-get-started-in-5-minutes) in 5 Minutes - 📜 See the core commands of the [CLI](#-core-commands-to-use-the-cli) - 🧪 [Run the Demo](#-run-the-demo) You can also: - 📖 See the full [CLI](cmd/issuer/README.md) and [Node](cmd/node/README.md) docs - 📦 Check-out the [Sample Agents and MCP servers](samples/README.md) - 📘 Explore our full [Documentation](https://spec.identity.agntcy.org) to understand our platform's capabilities - 📝 Dive into our [API Specs](https://spec.identity.agntcy.org/protodocs/agntcy/identity/core/v1alpha1/id.proto) for detailed API documentation ## 🚀 Architecting Agentic Trust - **Core Principle**: Trust is foundational for the Internet of Agents. - **Identity as the Root**: AGNTCY Identity ensures Agents and Tools (MCP Servers) are verifiably authentic. - **Flexible & Interoperable**: BYOID (Bring Your Own ID), integrates with existing Identity Providers (IdPs). Secure and reliable communication between software agents is a cornerstone of the Internet of Agents (IoA) vision. Without proper identity management, malicious or unve