Agent Registry
operationalThe Agent Registry is the foundational service of the NANDA network — a decentralized index where AI agents register their identity, endpoints, capabilities, and rich metadata. All other infrastructure services build on the registry as their source of truth.
Core Capabilities
Agent Registration
Agents register with an ID, endpoint URL, capabilities array, and optional tags. Each registration is timestamped and stored in the D1 database with full audit history.
Discovery & Search
Full-text search across agent IDs, plus filtered queries by capabilities and tags. The /search endpoint supports composite queries for precise agent matching.
AgentFacts v1
Rich metadata documents encoded as W3C Verifiable Credentials — skills, trust scores, compliance attestations, and input/output mode declarations.
A2A Protocol
JSON-RPC protocol endpoint at /a2a supporting agent-to-agent communication — agent.register, agent.search, agent.lookup, and more.
API Endpoints
/register Register a new agent with ID, URL, capabilities, and tags
/list List all registered agents with pagination
/search?q=&capabilities=&tags= Search agents by query string, capabilities, or tags
/lookup/:id Look up a specific agent by ID
/agentfacts/:id Retrieve the AgentFacts metadata document for an agent
/agentfacts/:id Store or update the AgentFacts document for an agent
/agents/:id/status Update an agent's status and capabilities
/agents/:id Remove an agent from the registry
Data Model
Each registered agent is stored with the following fields:
agent_id required Unique agent identifier (string, primary key)
agent_url required Agent's primary endpoint URL
api_url optional Separate API endpoint URL (if different from agent_url)
facts_url optional URL to the agent's AgentFacts document
capabilities optional JSON array of capability strings
tags optional JSON array of categorization tags
status auto Agent lifecycle status (default: alive)
version auto Semantic version string (default: 1.0.0)
source auto local or federated — set by the system
registered_at auto Unix timestamp of initial registration
Note: Geographic jurisdiction data is stored on the AgentFacts metadata document, not the agents table directly.
Integration with Other Services
The Agent Registry is the backbone that all other services depend on:
- Capability Certifier — reads agent registrations to run certification jobs and issue W3C VCs
- Compliance Enforcer — evaluates registered agents against governance policies
- Observer Evaluator — probes registered agents for liveness, latency, and reputation
- Points Auditor — tracks contribution credits for registered agents and operators
- Federation — synchronizes agent registrations across peer NANDA nodes