# Buy something the person has just approved

> Buy something the person has just approved: 0 companies fully do it, 6 with a limit, 24 carry the tag. Every listing in Agent checkout protocols with the reason and a source.

- Canonical: https://www.anchorterminal.com/niches/checkout-protocols.buy-for-person/
- Markdown: https://www.anchorterminal.com/niches/checkout-protocols.buy-for-person/index.md (~1,100 tokens)
- Slim: https://www.anchorterminal.com/niches/checkout-protocols.buy-for-person/index.min.md (~280 tokens, same facts, less prose, for token-sensitive contexts)
- JSON: https://www.anchorterminal.com/niches/checkout-protocols.buy-for-person/index.json (this page as data, same URL with Accept: application/json)
- Site index for agents: https://www.anchorterminal.com/llms.txt (the key docs and every listing in one file, at most 16 MB, about 4 million tokens: https://www.anchorterminal.com/llms-full.txt)
- API: https://www.anchorterminal.com/api/v1/index.json
- MCP: https://www.anchorterminal.com/mcp (the whole catalogue as tools, no key)
- DNS: dig +short TXT <slug>.grade.anchorterminal.com (the grade as a DNS TXT record, for a sandbox with no HTTP where names still resolve; also top., best.<category>. and <a>.vs.<b>. under the zone, and the same under grade.letme.dev)
- Licence: CC BY 4.0, credit Anchor Terminal and link this page (https://www.anchorterminal.com/terms/#data)
- Updated: 2026-11-15

No company's docs show a full fit yet. The listings below do the job with a limit, or not at all.

| Companies, full fit | With a limit | Carry the tag | Share of the category's work | First-hand accounts |
| --- | --- | --- | --- | --- |
| 0 | 6 | 24 | 20 | 4 |

## What counts as done

An order exists at the merchant for the approved items and total, the person approved that exact cart and total, stock and price were confirmed before payment, and when the merchant needs the person (3D Secure, login) the agent hands over a link instead of retrying.

How agents ask for it: buy this for me; order the cheapest one; check out with my saved card; get me two of these delivered

## Does the job, with a limit

It 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.

- **Agentic Commerce Protocol (ACP) (OpenAI and Stripe)**: Sessions carry items and totals, return out_of_stock and price-change messages, set authentication_required for 3-D Secure and intervention_required for steps the agent can't do, with an Idempotency-Key on every POST. One buyer learned of stock only at payment (acc-01), and few merchants offer native checkout (acc-06).
- **American Express Agentic Commerce Experiences (ACE) (American Express Company)**: Payment Credentials and Intent Intelligence specifications (available since 2026-04-14) issue tokenised credentials to verified agents against a Card Member-authenticated intent. The specifications are shown only to approved developers under agreement, so the checkout steps could not be read; vendor claim only.
- **Agent Payments Protocol (AP2) (Google LLC)**: The closed Checkout Mandate is signed on a Trusted Surface and bound by hash to the merchant-signed Checkout JWT, so the approval covers that exact cart, and the merchant returns a receipt. AP2 defines no catalogue, stock or handoff calls itself, and no production deployment is named.
- **Mastercard Agent Pay (Mastercard)**: Registered agents submit a scoped agentic token in the normal card fields, which the processor detokenises, and the merchant guide covers Level 1 form checkout. Registration and tokens need Mastercard onboarding with no public API, sandbox or process, so an agent platform cannot start on its own.
- **Universal Commerce Protocol (UCP) (UCP Authors (Google, Shopify and co-developers))**: Checkout sessions return authoritative prices per line and move to requires_escalation with a continue_url when the buyer must act, and a WooCommerce test order went through that hand-off (acc-02). Shopify's checkout API was gated behind approval for one builder (acc-05).
- **Visa Intelligent Commerce (Visa Inc.)**: The person authenticates each payment instruction by passkey, credentials are released only if the request matches it, and VisaNet checks merchant and amount at authorisation; payment is guest-checkout form fill. Agents need Visa onboarding, and one builder found no developer tooling (acc-17).

## What stops agents finishing

- 3D Secure or a merchant login needs the person
- native checkout available at few merchants
- out-of-stock reported only at the payment step

## Around it

Before: checkout-protocols.find-and-cart, agent-wallets.card-checkout. After: commerce.track-order, email.send-receipt.

## Where this comes from

Weight 20 of 100 in Agent checkout protocols: 4 of 18 accounts (acc-01, acc-02, acc-06, acc-17); the job the ACP launch and Walmart threads are about

As data: https://www.anchorterminal.com/api/v1/use-cases/checkout-protocols.buy-for-person.json, or the MCP tool get_use_case with id checkout-protocols.buy-for-person. Draft, read 2026-11-15 from public docs and first-hand accounts, not yet reviewed by a person.

---

Query this catalogue directly over MCP: https://www.anchorterminal.com/mcp (Streamable HTTP, no key). How: https://www.anchorterminal.com/agents/#mcp
