Why a firm cannot act on a well-written request
Firms hold material a client expects to stay confidential, and requests that look like they come from a client are a known route to extracting it. Email domains and letterheads can be imitated. When the requester is an agent, the firm needs something it can check that does not depend on how convincing the request reads.
How the firm checks the requesting agent
The client's agent presents its AgenID. The firm's intake agent resolves it and re-verifies the operator's signature over the manifest. The illustration shows L2_DOMAIN_VERIFIED, where an authority checked control of the client's domain, and L3_ORGANIZATION_VERIFIED, where it reviewed evidence of the organization itself.
Because the identifier is persistent, the firm can later confirm which agent made which request, and which operator claims were verified for that manifest version, without relying on either side's recollection.
Privilege, conflicts and engagement stay with the firm
Whether the organization is a client, whether a conflict exists, what is privileged and what may be released are professional judgments the firm makes under its own obligations. AgenID identifies the requester. It does not form an engagement, waive or protect privilege, or tell the firm what it may disclose. Nothing here is legal advice.
Today the reference registry at agenid.com issues DECLARED and L1_REGISTERED. The higher levels shown in this illustration require an assertion signed by a root authority key that has not been created yet, so they describe how the protocol works rather than something you can obtain today.
Frequently asked questions
Can a law firm work with a client's AI agent?
Some firms already receive requests from client-side automation. The open question is which agent is asking and which organization it acts for, which a portable identity makes checkable.
How does a firm verify an AI agent's organization?
It resolves the agent's AgenID, re-verifies the operator's signature, and reads which claims about the operator have been independently verified. In this illustration those are domain control at L2 and organization evidence at L3.
Does verification mean the firm should release the documents?
No. AgenID answers which agent is acting and who declared it. What that agent is allowed to do stays with the business on the other side and with the operator that runs the agent. Protocol v1.1.1 defines no signed authorization object.
Does AgenID create an attorney-client relationship?
No. AgenID is an identity layer. Engagement, conflicts and privilege are determined by the firm and the applicable professional rules, not by any verification level. This is not legal advice.