How it relates to AgenID
AgenID covers the operator-identity layer. An agent presents its identifier; the other agent resolves it, re-verifies the operator's Ed25519 signature and reads the declared purpose. The learn guide walks through the flow. The check needs no account or API key, and the verifying agent does not have to trust AgenID, because the registry cannot forge an operator signature.
AgenID does not authenticate live requests today: nothing binds a specific HTTP request to a registered agent. Request signing is the layer approaches like Web Bot Auth work on.
Why it matters
Agents increasingly act on both sides of a transaction. A stable identity lets history and accountability attach to the agent across platforms instead of restarting at every service. Without a shared identity layer, each pair of agents needs a bilateral arrangement such as exchanged API keys, which does not work for agents meeting for the first time.
The reference deployment at agenid.com issues nothing above L1_REGISTERED today. L2 and higher require a VerificationAssertion signed by a root authority key, and that key has not been created yet.
What it does not mean
Authentication answers who; it does not answer what the agent is allowed to do. Delegated authority from a principal is a separate object that v1.1.1 does not define.