Every AI Agent Needs a Human Owner. Now It Can Prove One.
NEUS × ZKPassport connect private proof of a human operator to a distinct AI agent, clear limits, a check before action, and a record of the decision.
AI agents call tools, touch private data, change infrastructure, start payments, and act across services. Most identity systems were built for people and predictable workloads, not software that acts on its own.
Who is behind the agent, what is it allowed to do, and can you prove the decision after it acts?
For enterprises, this is a non-human identity (NHI) and IAM problem. In 2026, NIST launched its AI Agent Standards Initiative and began work on software and AI agent identity and authorization. Cloud Security Alliance research found that 68% of surveyed organizations could not clearly distinguish human from AI-agent activity, while 74% said agents often receive more access than necessary. A separate CSA survey found that 82% had discovered previously unknown agents in their environments.
You need a clear link between the accountable person, the agent acting for them, what that agent may do, and the action itself. NEUS and ZKPassport connect that chain.
From proof of human to agent limits that hold
ZKPassport lets someone prove the facts a workflow needs from a supported NFC government ID on their own device, without exposing any other personal data from the ID. The document stays on the device. The app gets only the proof or attributes its policy asks for.
NEUS takes that result into the agent path: bind it to the owner, give the agent its own identity, set limits that expire, check those limits before a protected action, and record the decision.
Private operator proof → owner → distinct agent → limits → check before action → decision record
Proof of personhood does not open agent access. Agent identity does not grant permission. An old credential does not prove a request is still allowed. Each part stays separate.
Verify the operator privately, give the agent its own identity, set exact limits, check the action, and record the decision.
One flow, five control points
1. The person verifies privately
The app asks only for what the workflow needs: personhood, uniqueness, age, nationality, and sanctions status.
ZKPassport validates the ID and builds the proof on the user's device. The source document does not need to be uploaded to NEUS or stored by the app.
2. The agent gets its own identity
NEUS ties the passed check to the owner and active policy, then treats the agent as a separate actor with its own ID and key or wallet.
You can tell what the person did from what the agent did, instead of both hiding behind one login, service account, or API key.
3. Exact limits are set
The owner grants only what the task needs: tools, resources, spend caps, environment or domain, expiry, revoke, and other conditions.
Human verification and agent permission stay separate. A verified owner can approve one narrow task without open-ended access.
4. The action is checked
When the agent hits an API, tool, dataset, payment rail, or execution endpoint, NEUS checks identity and limits at that boundary.
In-scope requests can proceed. Expired, revoked, replayed, out-of-scope, or over-limit requests can be blocked.
For higher-risk actions, policy can require a stronger check or explicit human approval in sensitive cases, not for every move the agent makes.
5. The decision is recorded
The outcome can produce a proof that ties together the agent, owner relationship, policy, limits used, decision, and time.
Teams get a clear answer for why something was allowed, denied, or escalated, without putting the operator's ID document into shared systems.
Privacy without losing accountability
ZKPassport leaves ID data on the device and shares only what the app needs. NEUS uses that result with owner, agent, limits, policy, and decision context.
Prove only what the workflow needs. Bind it to that purpose. Do not create a universal identity handle. Accountability does not require a new identity honeypot.
Why this matters for NHI and IAM
Classic IAM treats a principal as a person or a predictable workload. Agents sit in between: they act for someone, use many tools, carry approved limits, and move at machine speed.
Discovery alone leaves open questions: Is the agent distinct from its owner? Who is accountable? What is allowed right now? Does that cover this action? What record remains after the decision?
NIST's work on software and AI agent identity and authorization targets the same gap: identification, authorization, auditing, and non-repudiation.
ZKPassport proves required facts about the human operator without collecting the ID document. NEUS turns that into a distinct agent, bounded limits, a check before action, and evidence you can reuse.
Build a protected agent workflow
NEUS and ZKPassport work with agent platforms, AI apps, security and IAM teams, payment infrastructure, and developers who need private operator assurance and enforceable agent limits.
- Set up a NEUS account: neus.network/profile
- Run Proof of Human with ZKPassport: Proof of Human check
- Set agent limits: Scoped permissions, spend caps, and tool access for active agents
- Enforce before action: Gate high-risk API calls, payments, and infrastructure actions with NEUS
Explore NEUS · Explore ZKPassport
About the partners
NEUS helps teams set who someone is, what they may do, and check it before access, payment, or execution for people and AI agents. Learn more at neus.network.
ZKPassport lets users prove facts from supported NFC government IDs on their own device, without handing over the document. Apps can check personhood, uniqueness, age, nationality, and sanctions status. Learn more at zkpassport.id.