Glossary

What is Know Your Agent (KYA)?

Know Your Agent means verifying which AI agent is acting and who it acts for. Where the term comes from, what is published, and what isn't settled yet.

Know Your Agent (KYA) is an emerging, not yet standardised term for verifying an AI agent's identity and linking it to the person or business it acts for, by analogy with Know Your Customer checks.

How does it work?

When an agent shows up at a checkout, a merchant wants to know three things: is this a known agent rather than a scraper or fraud bot, who is it acting for, and did that person authorise this purchase. KYA is the label the payments industry has started using for the first two. There is no single KYA specification. In September 2026 Ant International, Mastercard and Visa announced they had begun collaborating on a Know-Your-Agent interoperability framework. Their release describes linking each agent to a validated operator, cardholder or business, assessing agents against shared security requirements and monitoring them with identity and transaction signals, while each network keeps its own verification process. It names the building blocks as Visa's Trusted Agent Protocol, Mastercard Verifiable Intent and Ant International's Agentic Mobile Protocol, and says the parties will explore common principles, so it is a starting point rather than a finished standard. The published protocols underneath are more concrete. Visa's Trusted Agent Protocol has an agent sign its HTTP requests to a merchant using HTTP Message Signatures (RFC 9421); the merchant rebuilds the signature base and checks it against the agent's public key, which Visa says helps tell legitimate agents from bots and web crawlers. AP2 takes another angle: an open mandate names the specific agent's key, so a verifier can check that the agent closing a purchase is the one the user authorised.

In practice

For a merchant, KYA today means choosing which agent signals to accept, such as Visa TAP signatures on incoming requests, and deciding what to do with unsigned agent traffic. For someone building an agent, it means expecting to register with networks or merchants and to sign requests with a key you protect. For an owner delegating spending, it is a reminder that identity is not permission: knowing which agent is acting doesn't tell you whether it should be paying that merchant that amount. Treat vendor claims of 'KYA compliance' with care until a published framework defines what that means.

What it does not mean

  • KYA isn't a regulation or a single standard. As of the Ant International, Mastercard and Visa announcement it is a framework under development.
  • It isn't KYC for the agent's owner, though the two may be linked: the announced approach ties each agent to a validated operator, cardholder or business.
  • Verifying an agent's identity doesn't limit what it spends. Budgets, approvals and allowed payees are separate controls.
  • A signed request proves which key signed it, not that the agent's instructions weren't manipulated.

Where does Veyra fit?

Veyra doesn't implement Trusted Agent Protocol, AP2 or any KYA framework, and doesn't sign requests to merchants. On the payer side it identifies each agent by its own endpoint and bearer token, applies that endpoint's policy to every payment it requests, and logs each decision, so you can see which agent asked for what.

Veyra's spend policy for one agent endpoint: per-transaction limit, daily limit, auto-approve limit, ask-up-to limit and recipient allowlist
What this looks like in Veyra: one spend policy per agent endpoint, with a per-payment cap, a daily cap, an auto-approve band, an ask band and a recipient allowlist, all checked on the server. Try the free policy generator →

Sources

Guides that use this term

This page explains how agent payments and the related technology work. It is not financial, investment, legal or tax advice. Protocols and provider features change; check the linked official sources before relying on a detail.