Two identities, not one
Agencies already run identity proofing for residents. That process establishes who the license holder is. It says nothing about the software submitting on their behalf, which may be operated by a filing service the agency has never dealt with. Without a way to identify the filer, an agency either blocks automated filing or accepts submissions it cannot attribute.
How the portal checks the filing agent
The filing agent presents its AgenID. The portal resolves it, reads the signed manifest naming the filing service as operator, and re-verifies the signature itself. The operator declaration shows as DECLARED at L1_REGISTERED; the illustration then shows L2_DOMAIN_VERIFIED for the service's domain and L3_ORGANIZATION_VERIFIED for evidence of the organization.
Because the identifier is persistent, the agency can attribute every filing to the same agent over time and see which operator stands behind it.
Resident proofing and the decision stay with the agency
AgenID does not identify the resident and does not replace the agency's own identity proofing. Eligibility, fees and the licensing decision follow the agency's rules. The filing agent's identity is one more input the agency can read; it grants nothing.
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 an AI agent renew a license or permit?
Filing services and agents can already submit renewals where portals allow it. The open question for the agency is which agent is filing and who operates it, which a portable identity makes checkable.
Does AgenID verify the resident's identity?
No. AgenID identifies the agent and its operator. Proofing the resident is a separate process the agency runs on its own terms.
Does a verified filing agent get the renewal approved?
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.
What does an agency need to verify an agent?
An HTTPS request to resolve the identifier and standard Ed25519 signature verification over RFC 8785 canonical JSON. It does not need an account or a contract with AgenID.