Agent capability
Verify the agent. Verify the user.
Agent verification checks an AI agent's identity and operator. User verification (KYC) checks the person's real-world identity. Keep these checks distinct so you know who is acting and who they represent.
{"agent": {"identity": "verified","operator": "acme-shopping-ai","reputation": 0.97},"human": {"proof_of_humanity": true,"passkey": "bound"},"classification": "trusted_agent","result": "verified"}
What is agent verification?
Agent verification establishes an AI agent's identity, checks its credentials, and identifies the operator or platform it represents. LoginID uses these signals to return a trust classification so you can fast-track known agents and apply stepped-up checks to unknown ones. This does not, by itself, verify the real-world identity of the user behind the agent; that is a separate KYC check.
Separate agent checks from user checks.
Agent verification
Verify the operator and identity behind each agent, so you know which platform or wallet it represents before granting trust.
User verification (KYC)
Check the person's real-world identity through identity proofing, such as government ID checks. This is separate from verifying the agent and its operator.
Trusted vs. guest
Tier agents by assurance: a known, verified agent gets a streamlined path; an unknown one gets stepped-up checks.
Portable reputation
Carry verification signals across surfaces with emerging agent-identity standards, so trust travels with the agent.
How agent verification works.
- 01
Resolve the agent identity
Identify the operator and credentials behind incoming agent traffic using Web Bot Auth and identity signals.
- 02
Link the user
Bind the agent to a passkey-authenticated user. When your policy requires KYC, check the user's identity separately; a passkey alone does not establish it.
- 03
Classify and route
Return a trust classification so your app can fast-track known agents and step up checks for the rest.
User verification (KYC)
Know Your Customer checks the real-world identity of the person behind the agent. Identity proofing, such as government ID checks, is separate from agent verification. Passkey authentication confirms access to a credential; it does not replace KYC.
Learn more- Real-world identity checks
- Government ID and age checks where required
- Separate from passkey authentication
Frequently asked questions
- How do agent verification and user verification (KYC) differ?
- Agent verification checks the AI agent's identity, credentials, and operator. User verification, or Know Your Customer (KYC), checks the person's real-world identity through identity proofing. Verifying an agent does not mean its user has passed KYC, and a verified user does not automatically make every agent they use trustworthy.
- How do you tell a trusted AI agent from a malicious bot?
- LoginID resolves the operator and credentials behind incoming agent traffic and returns a trust classification. Known, verified agents get a streamlined path while unknown ones receive stepped-up checks. User identity verification is evaluated separately when required by your policy.
- What is proof of humanity for an agent?
- Proof of humanity is a signal that a person stands behind an agent request, rather than bot detection alone. It is distinct from KYC, which checks that person's real-world identity. A passkey-authenticated interaction should not be treated as evidence that KYC has been completed.
- Does agent reputation travel across surfaces?
- Yes. LoginID carries verification signals across surfaces using emerging agent-identity standards, so a verified agent's reputation and trust tier can travel with it rather than being rebuilt on every site.
Trust the agent you can verify.
Verify the agent's identity and operator before it acts. Apply separate user verification (KYC) checks when your policy requires them.