Publish, discover, and resolve AAIF agents. SC-006 AAIF defines how to run a portable agent. SC-014 ACPM defines what it offers. AREG defines where to find it — the registry and discovery layer for the AAIF ecosystem.
An AAIF agent definition is a portable document, but there is no standard way to publish it so that orchestrators, platforms, and teams can find, verify, and fetch it. Every deployment either hard-codes an agent URL or builds a proprietary catalogue. There is no shared vocabulary for expressing what an agent is, who published it, what version it is, whether it has been yanked, or how to verify its authenticity.
A registry entry is a lightweight metadata document that records a published AAIF agent:
{
"sc_standard": "SC-013",
"sc_version": "0.1.0",
"registry_id": "a1b2c3d4-e5f6-7890-abcd-ef1234567890",
"agent_id": "550e8400-e29b-41d4-a716-446655440001",
"agent_version": "1.0.0",
"published_at": "2026-06-25T00:00:00Z",
"publisher": {
"name": "Acme Corp",
"url": "https://agents.acme.example",
"public_key_url": "https://agents.acme.example/.well-known/jwks.json"
},
"aaif_url": "https://agents.acme.example/agents/invoice-chaser/1.0.0/definition.json",
"tags": ["finance", "invoicing"],
"conformance_level": "Enterprise",
"required_capabilities": ["tool.mcp", "memory.redis"],
"acpm_profile_url": "https://agents.acme.example/agents/invoice-chaser/profile.json",
"yanked": false,
"yank_reason": null
}AREG defines the registry entry schema and the REST API for publishing, discovering, and resolving agents. A registry entry points to a full AAIF definition and optionally to an ACPM capability profile, allowing consumers to filter and verify agents without fetching the full definition document for every candidate.
AREG is a Proposed standard — v0.1.0. The registry-entry.schema.json is defined and validated. The REST API is specified in SPECIFICATION.md. Before advancing to Draft, at least one public registry must be deployed and tested against this schema.
This is an early-stage standard with no external adopters yet. If you implement it, you are a founding adopter — open a PR to ADOPTERS.md.
| File | Description |
|---|---|
| SPECIFICATION.md | Full specification: registry entry schema, REST API, signing model, discovery, versioning |
| ABSTRACT.md | Structured abstract for registry submission, IETF I-D, and citation |
| CONFORMANCE.md | Registry-implementation conformance levels and self-certification |
| WHITEPAPER.md | Publication essay — the case for a standard agent registry and readiness assessment |
| schema/registry-entry.schema.json | JSON Schema 2020-12 for a registry entry document |
| context.jsonld | JSON-LD context mapping AREG terms to semantic URIs |
| examples/invoice-chaser-entry.json | Registry entry for the SC-006 Invoice Chaser reference agent |
| examples/research-summarizer-entry.json | Registry entry for the SC-006 Research Summarizer reference agent |
| CITATION.cff | Citation metadata |
| CHANGELOG.md | Version history |
| ADOPTERS.md | Self-service adopter registry |
| NOTICE | Copyright and implementation disclaimer |
python3 tools/validate.py| Standard | Layer | Question answered |
|---|---|---|
| AAIF — SC-006 | Definition | What is this agent? |
| AREG — SC-013 | Registry | Where do I find it? |
| ACPM — SC-014 | Profile | What does it offer? |
An AREG registry entry carries the agent_id (from AAIF), an optional acpm_profile_url (to ACPM), and the required_capabilities[] copied from the AAIF document — enabling capability-based search without fetching the full definition for every result.
Licensed CC BY 4.0 — part of Schema Commons.