Incode's Know Your Agent Ties Every AI Agent to a Verified Human
Incode launched Know Your Agent on November 17, 2026, binding each customer AI agent to a verified person and a bounded mandate — with J.P. Morgan and Wells Fargo as design partners.

Why it matters
- Incode launched Know Your Agent on November 17, 2026, immediately available to businesses across payment rails and AI-agent providers.
- The suite has five modules: Agent Detection, Agentic Identity, Agent Access Management, Agent Monitoring and Agent Audit.
- Incode names J.P. Morgan, Wells Fargo, Experian and Chime as design partners, within a base of more than 800 organizations.
- The product expands on Agentic Identity, announced October 27, 2025, which entered pilot programs in Q4 2025.
- Incode's base includes nine of the top 10 US banks, eight of the top nine US telecoms, and four of the top five global marketplaces.
Incode launched Know Your Agent on November 17, 2026, a product that binds each customer AI agent to an identity-verified person and a bounded mandate before the agent can act. The suite is immediately available to businesses, works across payment rails and AI-agent providers, and turns on a blunt premise: after a customer completes a one-time live verification and consents, every action an agent takes carries a named human authorizer.
Why does this matter?
The launch targets an access-control gap that detection tools cannot close. Incode's product documentation states that a customer's agent and an attacker's agent can present the same credential, device, IP address and behavior at login. Block every agent and you reject legitimate customer activity; admit every agent and you admit fraud. The missing context, in Incode's framing, is who sent the agent and what that person authorized.
"An agent with no human behind it is a stranger with your customer's password," said Ricardo Amper, Incode's founder and CEO. Incode says an agent without a verified person behind it is stopped before acting, while a verified customer's agent operates within its permissions. The claim is strong; whether it holds in production depends on detection accuracy the company does not quantify.
The stakes are financial and regulatory at once. Autonomous agents are beginning to move money and execute transactions on payment rails, and institutions currently lack a standard way to know which human stands behind an automated request. Incode's answer — identity verification plus scoped mandates plus audit trails — competes to become the default control layer for that traffic.
How does Know Your Agent check each action?
The documentation divides the product into five modules: Agent Detection, Agentic Identity, Agent Access Management, Agent Monitoring and Agent Audit. Each module can run independently or as part of the full suite, and an existing detection signal can feed the other functions.
- Agent Detection examines declared agent headers and signed requests alongside session timing, navigation, browser behavior and automation patterns. When those signals point to an agent, a live-presence check can establish whether a real person is present. The business can then register the agent, require the person to verify directly, or block it. Incode says this process identifies agents that do not announce themselves — though the company offers no published accuracy figures for that claim.
- Agentic Identity is the binding layer. After the customer completes a one-time live verification and consents, it binds each agent to that person and to a mandate defining scope, spending amount and duration. The business sets the mandate; the customer can narrow it; the agent cannot extend it on its own.
- Agent Access Management runs before an action executes. It checks that the agent is registered, its mandate is valid, its person is verified, and the action falls within those permissions. Exceeding a limit can require live approval from the person. The customer can also revoke an agent instantly, stopping pending actions while preserving the record.
- Agent Monitoring looks for compromised or misaligned agents using patterns across sessions and organizations. Incode says an agent blocked at one organization is already flagged when it reaches another.
- Agent Audit maintains a tamper-evident trail containing the action, person, mandate and proof — giving a questioned transaction a named authorizer and a record of the permission under which it ran.
The cross-organization flagging claim deserves scrutiny: it implies shared intelligence among participating institutions, and Incode does not detail how that exchange works or who participates at launch. In plain words, the suite treats detection as the first decision and verification as the one that actually governs access.
Which protocols does it support?
The suite is designed to work with existing agent and payment protocols rather than require one agent platform. Incode names Model Context Protocol, Agent2Agent, Agent Payments Protocol and Web Bot Auth among the compatible standards, alongside card-network agent programs. Those protocols can carry the agent's credential; Know Your Agent adds the verified person and the mandate behind the action.
That positioning matters. Interoperability claims are cheap in this market, and Incode has not published results from the card-network programs it names. Still, attaching identity to open protocols rather than a proprietary agent framework is the architecture most banks would require before adoption.
How does the identity check actually work?
The verified-person layer draws on three Incode components: Deepsight liveness checks, TrustGraph identity history across participating institutions, and GovFaceMatch. For GovFaceMatch, the user scans the barcode on the back of a government ID and takes a live selfie. The system then compares that selfie with the issuing state's Department of Motor Vehicles record in real time.
Incode says its face-match engine runs inside DMV infrastructure and portrait images never leave that environment. The company also says no biometric data is stored and no government personally identifiable information is shared during matching. These are vendor claims about privacy architecture; independent verification is not cited.
The customer list lends weight. Incode names J.P. Morgan, Wells Fargo, Experian and Chime as design partners, and reports an identity-platform base of more than 800 organizations. That base includes nine of the top 10 US banks, eight of the top nine US telecommunications companies, and four of the top five global marketplaces.
Where did this product come from?
Know Your Agent expands on Agentic Identity, announced on October 27, 2025. The earlier product was offered through early access, with pilot programs beginning in the fourth quarter of 2025. It already covered agent detection, verified-human owner binding, scoped consent through cryptographic identity tokens, and continuous behavioral monitoring.
In the new architecture, Agentic Identity is specifically the module connecting an agent to its person and mandate. It sits within a suite that separates detection, access management, monitoring and audit into their own components — moving the earlier early-access work into an immediately available product. In short, what was a pilot capability last year is now a generally released platform.
What is the takeaway?
For businesses weighing customer access against fraud, the central implication is that detection is only the first decision. Incode's model ties admission to a verified person, a bounded mandate, live approval for exceptions, revocation, and an audit trail — making the human authorization behind an agent as consequential as the credential it carries. Whether that model becomes an industry norm or one vendor's pitch will depend on adoption beyond the named design partners and on results Incode has yet to publish.
Source: unite.ai
More from James Calloway
Show full bio
News editor covering people, launches and day-to-day practice in artificial intelligence and machine learning at AI In Context.
722 articles
Related articles
- JPMorgan, Amazon and Kohl's Are Blocking AI Agents. Experts Say They Can't Win That Fight
- IBM Buys AuthMind to Watch What AI Agents Do After They Log In
- Cato Networks Launches AgentSense to Block AI Agent Attacks
- RSA Launches Agent ID to Tame Shadow AI Agents
- AI Security in 2027: Agent Permissions Will Define the Blast Radius