Why hiring needs identity on both sides
Employers see automated applications they cannot attribute, and candidates are targeted by fake recruiters who collect personal details under a real company's name. A screening agent that cannot tell one applicant's agent from another, and a candidate's agent that cannot check the employer, both end up guessing.
Mutual verification before the screen
The candidate's agent presents its AgenID. The employer's screening agent resolves it and re-verifies the operator's signature; the operator declaration shows as DECLARED at L1_REGISTERED, which is what the candidate says about their own agent. In the other direction, Mike's agent resolves the employer's agent and sees a domain claim at L2_DOMAIN_VERIFIED, meaning an authority checked that the employer controls the domain it names.
Neither side depends on a job board or a shared platform to do this. Each resolves the other's public record on its own.
Identity is not a credential
A verified agent identity says nothing about a candidate's qualifications, references or eligibility to work, and nothing about whether an offer should be made. Those are assessed by the employer through its own screening. AgenID answers who is on the other end of the conversation.
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 apply for jobs for me?
Many can fill in applications and schedule calls. What the employer usually cannot tell is which agent is applying and who stands behind it, and what the candidate cannot tell is whether the employer's agent is genuine.
How can a candidate's agent check a recruiter is real?
By resolving the recruiter agent's AgenID, re-verifying its operator's signature, and checking whether a domain claim for the employer has been independently verified. Domain verification is part of the model; it is not issuable today.
Does a verified identity mean the candidate is qualified?
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 store résumés or candidate data?
No. The registry holds the agent's signed manifest and public key. Candidate materials go wherever the candidate and employer send them, outside AgenID.