{
  "data": null,
  "kind": "anchor.page",
  "links": {
    "api": "https://www.anchorterminal.com/api/v1/index.json",
    "html": "https://www.anchorterminal.com/niches/checkout-protocols.verify-agent/",
    "json": "https://www.anchorterminal.com/niches/checkout-protocols.verify-agent/index.json",
    "llms": "https://www.anchorterminal.com/llms.txt",
    "markdown": "https://www.anchorterminal.com/niches/checkout-protocols.verify-agent/index.md",
    "mcp": "https://www.anchorterminal.com/mcp",
    "slim": "https://www.anchorterminal.com/niches/checkout-protocols.verify-agent/index.min.md"
  },
  "markdown": "No company's docs show a full fit yet. The listings below do the job with a limit, or not at all.\n\n| Companies, full fit | With a limit | Carry the tag | Share of the category's work | First-hand accounts |\n| --- | --- | --- | --- | --- |\n| 0 | 4 | 32 | 14 | 4 |\n\n## What counts as done\n\nThe merchant verifies the signature against the published key directory, records which agent and platform placed the order, and rejects stale or replayed signatures, using test vectors the spec publishes.\n\nHow agents ask for it: is this bot a real agent; accept orders only from verified agents; check the agent signature\n\n## Does the job, with a limit\n\nIt does the job, but something in the docs or a user's account will get in an agent's way. The limit is named in each row.\n\n- **Agent Payments Protocol (AP2) (Google LLC)**: Merchants verify mandate signatures by key id, and one merchant publishes discovery and JWKS files for v0.2 (acc-09). The repository has no signature test vectors or conformance suite, and agent identity signatures over HTTP are left to other specs.\n- **Mastercard Agent Pay (Mastercard)**: Certified agents sign requests with RFC 9421 Web Bot Auth keys registered in payment-network directories, which merchants or edge providers verify. No Mastercard directory URL, test vectors or versioned spec were found in the guides read.\n- **Universal Commerce Protocol (UCP) (UCP Authors (Google, Shopify and co-developers))**: Requests are signed per RFC 9421 with keys published in /.well-known/ucp, keyid as the JWK thumbprint, created and expires required and a nonce recommended, with Web Bot Auth compatibility. No signature test vectors were found in the spec or the conformance suite.\n- **Visa Intelligent Commerce (Visa Inc.)**: TAP signs requests with created and expires at most 8 minutes apart and a nonce the merchant records to block reuse, with keys from a retrieval service. The spec has no version or test vectors (acc-15), and the reference proxy rejects the RFC 9421 keyid spelling (acc-14); both are open.\n\n- not this job: Agentic Commerce Protocol (ACP) (OpenAI and Stripe): Clients SHOULD sign requests with a Signature and Timestamp header, but algorithms are published out of band, there is no key directory or test vectors, and no required field names the agent (acc-07).\n- not this job: American Express Agentic Commerce Experiences (ACE) (American Express Company): The Agent Registration specification, which would let a merchant or Amex verify an agent, is still under development per the ACE page; no key directory or test vectors are published.\n\n## What stops agents finishing\n\n- reference implementation rejects the RFC spelling\n- no public API contract or sandbox for the card programmes\n\n## Around it\n\nBefore: agent-auth.sign-request. After: checkout-protocols.buy-for-person, checkout-protocols.dispute-evidence.\n\n## Where this comes from\n\nWeight 14 of 100 in Agent checkout protocols: 4 of 18 accounts (acc-07, acc-14, acc-15, acc-17); Visa and Mastercard programmes have no other first-hand reports\n\nAs data: https://www.anchorterminal.com/api/v1/use-cases/checkout-protocols.verify-agent.json, or the MCP tool get_use_case with id checkout-protocols.verify-agent. Draft, read 2026-11-15 from public docs and first-hand accounts, not yet reviewed by a person.\n",
  "meta": {
    "attribution": "Anchor Terminal (https://www.anchorterminal.com)",
    "attributionRequired": true,
    "credit": "CC BY 4.0, credit Anchor Terminal and link the page or API address you took it from (https://www.anchorterminal.com/terms/#data)",
    "docs": "https://www.anchorterminal.com/docs/",
    "generatedAt": "2026-11-16",
    "license": "CC-BY-4.0",
    "method": "https://www.anchorterminal.com/benchmark/",
    "methodology": "0.8",
    "openapi": "https://www.anchorterminal.com/openapi.json",
    "preview": false,
    "run": "2026-10-01",
    "runLabel": "October 2026 research run",
    "terms": "https://www.anchorterminal.com/terms/#data"
  },
  "page": {
    "breadcrumbs": [
      {
        "name": "Home",
        "url": "https://www.anchorterminal.com/"
      },
      {
        "name": "For agents",
        "url": "https://www.anchorterminal.com/agents/"
      },
      {
        "name": "Niches",
        "url": "https://www.anchorterminal.com/niches/"
      },
      {
        "name": "Recognise a trusted agent and check its credential before accepting the order",
        "url": ""
      }
    ],
    "description": "Recognise a trusted agent and check its credential before accepting the order: 0 companies fully do it, 4 with a limit, 32 carry the tag. Every listing in Agent checkout protocols with the reason and a source.",
    "facts": null,
    "h1": "Recognise a trusted agent and check its credential before accepting the order",
    "image": "https://www.anchorterminal.com/assets/og/default.png",
    "path": "/niches/checkout-protocols.verify-agent/",
    "published": "",
    "section": "agents",
    "title": "Recognise a trusted agent and check its credential before accepting…",
    "toc": null,
    "updated": "2026-11-15",
    "url": "https://www.anchorterminal.com/niches/checkout-protocols.verify-agent/"
  },
  "tokens": {
    "markdown": 1000,
    "slim": 280
  },
  "version": 1
}
