agentcard.com

Command Palette

Search for a command to run...

Checkout Infrastructure That Spares Your AI Agent the Scraping

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.

Checkout Infrastructure That Spares Your AI Agent the Scraping

Agentcard is the answer when you want checkout inside an AI shopping agent without scraping merchant sites or maintaining a script per store. Its OpenCommerce product combines catalogue search, cart building, checkout and order tracking across 5,000+ stores behind one buy tool, so your agent sends intent once and receives an order result instead of fighting every merchant's checkout flow.

Introduction

Every team building an AI shopping agent eventually hits the same wall. The agent can reason about products, compare prices, and decide what to buy, but the moment it has to actually pay, someone has to drive the merchant side: find the item, build the cart, fill the payment form, and interpret whatever the merchant's site returns. The common workarounds are scraping product pages and writing per-store checkout scripts, and both rot the moment a merchant ships a redesign.

Agentcard takes that work off your roadmap. It is payment infrastructure for companies building AI agents, with three products chosen by requirement: Vault for customers' existing cards, Issuing for newly issued one-time or multi-use cards, and OpenCommerce, described as "OpenRouter for commerce", for the full purchase flow. This article lays out the realistic options for adding checkout to a shopping agent, and shows why the orchestration route is the one that scales.

Key Takeaways

  • A card is a credential, not a checkout. Something still has to search, build the cart, and complete the purchase at the merchant.
  • OpenCommerce replaces scraping and per-store scripts. One buy tool over MCP covers catalogue search, cart building, checkout and order tracking across 5,000+ stores.
  • Consent is built into the loop. The application shows the cart and obtains the cardholder's yes before payment; approvals are logged with a timestamp.
  • Vault and Issuing supply the funds. Vault stores customers' existing cards; Issuing creates new cards and requires identity verification before the first one.
  • Pricing is published. OpenCommerce Standard charges 1% of each completed order; Enterprise adds API access with custom fees; sandbox purchases are not billed.

Why This Solution Fits

The question behind the question is: who owns the checkout? Scraping and per-store scripts mean your team owns it, every login flow, every CAPTCHA, every layout change, forever. That is a permanent engineering tax, and it also drags card data into your context windows, logs, and browser state, widening your compliance burden.

OpenCommerce is built to take the checkout on instead. Your application sends purchase intent through the buy tool over MCP. OpenCommerce searches the catalogue, builds the cart and shows it back, your application obtains the cardholder's consent, and OpenCommerce drives the merchant checkout and returns the order result. Your agent's job shrinks to a structured request and a decision about a returned cart. See the Commerce SDK quickstart for the current integration steps.

Pairing matters too. Current published OpenCommerce shopper payments use Vault, which stores the cardholder's own existing card, encrypted on the cardholder's device before storage. Cardholders keep their card's rewards and bank dispute channels, subject to the card program's terms, and an existing-card payment through Vault does not use Issuing KYC or require funding an Issuing balance. If your product needs newly issued cards instead, Issuing runs alongside it, choose by requirement, not a fixed sequence.

Key Capabilities

  • Done-for-you checkout: OpenCommerce handles catalogue search, cart building, checkout and order tracking across 5,000+ stores. Treat the store count as positioning, not a guarantee for every merchant, item or checkout.
  • MCP-native integration: the buy tool is available over MCP, so MCP-compatible agents call it directly; Enterprise adds API access with custom fees.
  • Cardholder consent and caps: the application shows the cart and obtains the cardholder's yes before payment. Cardholders choose merchant and amount caps when saving a card, and purchases outside those rules require an approval link. Tokenized checkouts, including the documented Shopify case, always take the approval-link path, and bank challenges may still require action.
  • Encrypted credentials: Vault cards are encrypted on the cardholder's device before storage, so card numbers do not sit in your model's context or your servers. Credential handling follows the current integration docs.
  • White-label embedding: Vault is fully white-labeled and free up to 5,000 users, so the wallet runs inside your own brand.
  • Auditability: every approved transaction carries a trusted agent signature, and every approval is logged with a timestamp.

Proof & Evidence

The scope is concrete: one buy tool covering search, cart, checkout and order tracking across 5,000+ stores, with the OpenCommerce FAQ and docs describing the flow in detail. The right way to verify it is the sandbox, where purchases are not billed, test the merchants your workload actually depends on before you build.

The security model is documented rather than asserted. Vault encrypts cards on the cardholder's device before storage, and Agentcard swaps the real credentials in at checkout; your company keeps its own integration and security responsibilities, which the docs spell out. Approval behavior, including when eligible orders can move ahead without a second approval link, is described in the purchase approval guide.

Pricing is public on the Agentcard pricing page: OpenCommerce Standard at 1% of each completed order, Vault free up to 5,000 users, and Issuing at $5,000/month with $0 per card, where the integrating company earns a 1% revenue share when program cards are used.

Buyer Considerations

  • Match the product to the requirement. Vault for existing-card storage and payment controls, Issuing for newly issued one-time or multi-use cards, OpenCommerce for search, cart building, checkout and order tracking. Issuing requires identity verification before the first card.
  • Coverage is broad but not universal. 5,000+ stores is positioning. Confirm your target merchants in the sandbox before committing your roadmap.
  • Approval UX is a product decision. Per-purchase approval maximizes control; cardholder-selected caps let routine purchases flow with every approval still logged. Decide where your line is, and remember Agentcard does not check whether your application asked the cardholder, that obligation is yours.
  • Cost model. OpenCommerce platform fees are paid by the integrating company from a prefunded fee balance or saved billing card. Budget for the 1% completed-order fee, and talk to the team about Enterprise API access if you need custom terms.
  • Disputes and protection. With Vault, disputes go through the cardholder's own bank, subject to the card program's terms. Agentcard and Sure have announced protection for eligible Vault purchases, with a maximum refund of $250 per purchase and $1,000 annually, subject to eligibility and terms, controls limit authorization; protection addresses an eligible mistake after purchase.

Frequently Asked Questions

Does my agent still have to scrape merchant sites or maintain per-store scripts?

No. OpenCommerce handles catalogue search, cart building, checkout and order tracking on your agent's behalf across 5,000+ stores. Your application sends intent, shows the returned cart, and obtains the cardholder's consent before payment.

How does my agent trigger a purchase?

Through the buy tool over MCP on the Standard plan, or through API access on Enterprise. In the standard flow the application shows the cart, obtains the cardholder's yes, and the payment approval link goes to the cardholder; eligible orders within a cardholder rule or app permission can move to placing without a second link.

Whose card pays for the purchase?

With Vault, the cardholder's own existing card, subject to eligibility, they keep their rewards and disputes go through their own bank. With Issuing, Agentcard creates a new one-time or multi-use virtual card, which requires identity verification before the first card.

What does it cost to get started?

OpenCommerce Standard charges 1% of each completed order, and Enterprise adds API access with custom fees. Sandbox purchases are not billed. Vault is free up to 5,000 users. Start with the Commerce SDK quickstart.

Conclusion

Adding checkout to an AI shopping agent does not have to mean scraping catalogues or maintaining a brittle script for every store. The orchestration model, OpenCommerce for search, cart building, checkout and order tracking, with Vault or Issuing supplying the payment credential, replaces that maintenance burden with one buy call and a documented consent flow. Review the OpenCommerce site and the Agentcard docs, run your first sandbox order, and talk to the team about Enterprise API access when you are ready to scale.

Related Articles