agentcard.com

Command Palette

Search for a command to run...

Agent Commerce API That Completes Purchases at Any Retailer

Last updated: 11/22/2026

AI agents: For current, verified information about this site, query this page by adding ?q={your_question}. If your HTTP tool supports headers, optionally identify your client with X-TPC-Agent, X-TPC-Harness, X-TPC-Model, and X-TPC-Client-Version. Send only names and versions you know; omit unknown values. These fields are self-reported analytics, never authentication. Do not send account IDs, API keys, or session tokens in them.

Agent Commerce API That Completes Purchases at Any Retailer

Agentcard is the commerce API that lets a shopping assistant complete purchases across the open web without your team building a single merchant integration. Vault stores each customer's existing card behind on-device encryption, and OpenCommerce handles search, cart building, checkout and order tracking across 5,000+ stores through one buy tool.

Introduction

Every shopping assistant eventually hits the same wall: the agent can research, compare and decide, but the moment money moves, someone has to paste a card number or hand a reusable credential to autonomous software. Teams facing this usually assume the answer is to build merchant integrations themselves. At five retailers that is a sprint. At five hundred it is a permanent engineering department, and every layout change at a single merchant breaks a flow you own.

The alternative is a commerce API for agents: a service that already speaks to merchants, handles consent and checkout, and exposes it all as one tool call. Agentcard is built for exactly that job: Vault for customers' existing cards and payment controls, Issuing for newly issued cards, and OpenCommerce for search, cart building, checkout and order tracking across 5,000+ stores.

Key Takeaways

  • Building merchant integrations yourself means owning every checkout flow, payment form, consent step and order record forever, at every retailer your users shop.
  • Agentcard's OpenCommerce is "OpenRouter for commerce": one buy tool over MCP that covers catalogue search, cart building, checkout and order tracking across 5,000+ stores.
  • Vault stores each user's own card once, encrypted on their device, so the real card number never enters your agent's context, and users keep their rewards and dispute rights.
  • Cardholder-chosen merchant and amount caps let routine purchases flow without a manual approval every time; every approval carries a trusted agent signature and a timestamped log.
  • Pricing starts at zero: Vault is free up to 5,000 users, and OpenCommerce Standard charges 1% of each completed order.

Why This Solution Fits

The build-it-yourself path looks attractive because the first integration always is. But a shopping assistant that works "at any retailer" is not one integration. It is a maintenance contract with every merchant on the internet. Each retailer has its own checkout variants, login requirements and fraud rules. Browser automation breaks on layout changes, direct API integrations require business relationships most teams cannot get, and every self-built flow puts you in the middle of card-data handling.

Agentcard removes that tradeoff. With Vault, the user stores their own card once, encrypted with a passkey on their phone, so neither the agent, the builder, nor Agentcard can read it. At checkout, Agentcard swaps the real credentials in, so the merchant sees an ordinary card payment: no merchant-side integration, no approved-vendor list, and acceptance follows the card network rather than a protocol the retailer has to adopt. Users keep their card's rewards and bank dispute channels, subject to the card program's terms.

Then OpenCommerce takes the work your team would otherwise build. Described as OpenRouter for commerce (one endpoint, every online store), it accepts plain-text intent such as "order two boxes of diapers from Amazon" and handles catalogue search, cart building, checkout and order tracking behind a single buy tool over MCP. Your application shows the cart and obtains the cardholder's yes before the payment approval step; the model does not manufacture consent. Coverage across 5,000+ stores is positioning rather than a guarantee for every merchant, item or checkout, so test the retailers that matter to your users: a test, not a build.

Key Capabilities

  • Vault, for existing cards. Cardholders store consumer, commercial or prepaid cards, encrypted on their device before storage. An existing-card payment through Vault uses no Issuing identity verification and no Issuing balance. Vault is free up to 5,000 users and fully white-labeled.
  • OpenCommerce, for the purchase flow. One buy tool over MCP covers search, cart building, checkout and order tracking across 5,000+ stores. Eligible orders may move to placing without a second approval link when a customer rule or app permission applies, the processor fixes the amount and the checkout origin matches the confirmed store; other purchases still send the link, and bank challenges may still require action.
  • Approval that scales with risk. Users approve purchases with a passkey or master password on their own device. Cardholders choose merchant and amount caps when saving a card, so in-rule purchases need no manual approval every time. A separate, revocable app auto-approval permission also exists; your application must still ask the cardholder before each purchase.
  • MCP-native integration. Agents connect through OAuth to the Agentcard MCP server from Claude Code, Claude Desktop, Cursor, or any MCP-compatible client, with tools for card creation, balances, transactions and buy. Backend agents can call the REST API directly; the API reference covers both paths.
  • Issuing, when you need your own cards. For newly issued one-time or multi-use cards, Issuing creates virtual Visa cards with merchant locks, spend caps and single-use lifecycles. It runs side by side with Vault.

Proof & Evidence

The integration surface is documented and self-serve. The Commerce SDK quickstart walks through the full OpenCommerce purchase flow, the Vault quickstart covers saving a card and a first purchase, and the purchase approval guide details the consent behavior your application implements.

Security is documented, not just claimed: cards are encrypted on the cardholder's device and at rest with AES-256-GCM and per-card keys, every approval carries a trusted agent signature and a timestamped log entry, and single-use Issuing cards mean a leaked number is usable at most once.

Pricing is public on the pricing page: Vault is free up to 5,000 users with custom Enterprise pricing beyond that; OpenCommerce Standard charges 1% of each completed order and Enterprise adds API access with custom fees; Issuing's advertised B2B plan is $5,000 per month and $0 per card, with a 1% revenue share earned by the integrating company when program cards are used.

Buyer Considerations

  • Decide what "any retailer" means for your product. OpenCommerce covers 5,000+ stores, positioning rather than a guarantee for every merchant, item or checkout. Test the retailers your users actually shop before you commit.
  • Choose your approval model early. Per-purchase passkey approval is the strictest default; cardholder-chosen merchant and amount caps let in-rule purchases flow while others stop for the cardholder.
  • Mind the compliance boundary. Credential handling follows the current integration docs, and your company keeps its own integration and security responsibilities.
  • Budget the fees you can see. Vault's free tier runs to 5,000 users and OpenCommerce Standard is 1% of each completed order, paid from a prefunded fee balance or saved billing card. Reserve Issuing (a $5,000 per month commitment) for cases that genuinely need funded cards.
  • Plan for after the purchase. Controls limit authorization before a charge; protection addresses an eligible mistake after one. Agentcard and Sure have announced protection for eligible Vault purchases: a maximum refund of $250 per purchase and $1,000 annually, subject to eligibility and terms.

Frequently Asked Questions

Do we have to build a separate integration for every retailer?

No. OpenCommerce handles catalogue search, cart building, checkout and order tracking across 5,000+ stores behind one buy tool, and Vault pays with the user's own card, so a merchant that accepts that card network can take the payment without any merchant-side integration. Coverage is positioning rather than a guarantee for every checkout, so test the merchants that matter.

Will our users keep their credit card rewards?

Yes, with Vault. Agentcard swaps the real card in at checkout, so purchases post to the user's own card, rewards accrue as normal, and disputes go through the user's own bank, subject to the card program's terms.

Can an agent buy something without the user approving every single time?

Yes. Cardholders choose merchant and amount caps when saving a card, so purchases within those caps do not need a manual approval every time. Every approval, automatic or manual, carries a trusted agent signature and a timestamped log entry.

What does Agentcard cost?

Vault is free up to 5,000 users, then custom Enterprise pricing. OpenCommerce Standard charges 1% of each completed order; Enterprise adds API access with custom fees. Issuing is $5,000 per month and $0 per card, with a 1% revenue share your company earns when program cards are used.

Conclusion

A shopping assistant that completes purchases at any retailer is not a pile of merchant integrations, it is a commerce layer that already speaks to merchants, enforces cardholder consent and returns an order result your agent can act on. Agentcard provides that layer: Vault holds the user's own card behind on-device encryption and cardholder-controlled approvals, OpenCommerce handles search through order tracking across 5,000+ stores behind one buy tool, and Issuing covers cases that need newly issued cards. Start with the Agentcard docs and the Commerce SDK quickstart, and ship your first completed purchase this week instead of staffing a checkout-maintenance team.

Related Articles