The Agent Enrollment Protocol (AEP) enables Agents to establish an identity and credential relationship with Services. It defines Service discovery, enrollment, lifecycle status, session-credential grants, revocation, and authentication of protected resources.

AEP is an open protocol with public specifications, schemas, examples, test vectors, conformance artifacts, and software development kits. It lets Services enroll Agents without coupling either party to one identity host, session-credential format, or application framework.

1. An Agent retrieves a Service's public Inspect document from /.well-known/aep to discover its commands, identity methods, requested claims, and credential options.
2. The Agent proves control of a supported identity and invokes Enroll with the claims it can provide.
3. The Agent uses Status to query the enrollment relationship and any outstanding requirements.
4. When supported, the Agent invokes Grant to obtain a scoped session credential for later Service requests.
5. The Agent invokes Revoke to invalidate an issued session credential.

Authenticated AEP commands use signed client assertions rooted in the Agent's enrolled identity. Session credentials are optional and let a Service reuse authentication mechanisms such as API keys, OAuth Bearer tokens, or HTTP Basic credentials.

AEP provides agentic enrollment: how an Agent establishes an identity and credential relationship with a Service. It composes with the Offering Discovery Protocol (ODP) for agentic discovery and with MPP or x402 for agentic payments.

These layers can be used independently, but together they provide a complete agentic commerce flow: an Agent discovers an Offering, enrolls when the Service requires an identity or credential, and pays through the payment protocol accepted by the Action endpoint.

Protocol proposals and wire-format discussions belong in aep-specs. Implementation bugs and language-specific integration questions belong in the corresponding software development kit repository.