Glossary

What is an agent registry?

Definition

An agent registry is a published list of known AI agents, usually with each agent's public signing keys or a link to them, that websites and payment networks use to recognize agents they trust. Examples include the key directories Visa and Mastercard host for their registered agents. There is no single global registry.

Why it matters

A signature only proves that a request came from whoever holds a certain key. A registry tells you whose key it is and whether someone you trust has vetted that agent. Together they turn "this request is signed" into "this request comes from an agent a card network has registered".

For a store, that is the difference between letting any signed bot through and letting through the agents that a payment network, your CDN or you yourself have approved.

How it works

The word is used for a few related lists:

  • Payment network directories. Cloudflare wrote in October 2025 that "Both Visa and Mastercard protocols require agents to register" their public keys, and that Visa and Mastercard would each host a directory of their registered agents' keys. Visa's Trusted Agent Protocol specification says "For Visa's implementation, Visa will host a well-known URL" where merchants fetch those keys.
  • Bot registries for Web Bot Auth. An individual IETF draft, draft-meunier-webbotauth-registry-04 from October 27, 2026, says: "A registry is a list of entries." Each entry is an https link or an inline "Signature Agent Card", a JSON file in which a signed agent describes "its identity, purpose, rate expectations, and cryptographic keys." The draft states that it has no formal standing at the IETF.
  • Agent catalogs. The A2A specification lists "Querying curated catalogs of agents" as one way to find an agent card, alongside the well-known address.

For signed agents, the agent publishes its own keys, often at the address in its Signature-Agent header. The registry is how a verifier decides which of those agents to trust.

Example

A shopping agent sends a signed checkout request to your store. The service in front of your store looks up its key in Visa's directory, finds it registered, and checks the signature. The order goes through your normal rules. A second agent signs its requests correctly but appears in no registry you rely on. Its signature tells you which operator sent it, but not that anyone has vetted it, so you treat it with more caution. See AI agent identity: the complete guide.

Also called: agent directory, key directory, agent catalog

Sources

  1. Cloudflare blog: Securing agentic commerce: helping AI agents transact with Visa and Mastercard · checked 17 Nov 2026
  2. Visa Developer: Trusted Agent Protocol specifications · checked 17 Nov 2026
  3. IETF: draft-meunier-webbotauth-registry-04, Registry and Signature Agent card for Web bot auth · checked 17 Nov 2026
  4. A2A Protocol: Specification · checked 17 Nov 2026

The Sill Signals Team · Updated 17 Nov 2026

See which AI agents visit your site, and decide what they may do.

Scan your site free