A Buy Tool That Works Across Thousands of Online Stores
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.
A Buy Tool That Works Across Thousands of Online Stores
Agentcard's OpenCommerce is the answer: one buy tool, available over MCP, that covers catalogue search, cart building, checkout and order tracking across 5,000+ stores. Instead of teaching an LLM agent to scrape merchant sites or maintain a pile of one-off integrations, you connect it to a single commerce endpoint, pair it with a controlled payment method, and let the agent complete real purchases inside guardrails your customers control.
Introduction
An LLM agent that can research and compare products but cannot pay is stuck one step short of useful. The usual workarounds are fragile: browser automation that breaks on every checkout redesign, merchant-specific integrations that never scale past a handful of stores, or a raw card number pasted into an agent's context, which is a security problem rather than a solution.
The better architecture separates the job into two layers. The commerce layer finds the item, builds the cart, completes checkout and tracks the order. The payment layer supplies a credential the agent never actually holds, with human consent in front of every purchase. Agentcard provides both: OpenCommerce as the commerce layer and Vault or Issuing as the payment layer, connected through MCP, REST or a CLI. The Commerce SDK quickstart shows how the pieces fit together.
Key Takeaways
- One buy tool beats thousands of integrations: OpenCommerce covers search, cart building, checkout and order tracking across 5,000+ stores over MCP.
- The agent should never hold the real card. Vault keeps the cardholder's card encrypted on their device and swaps it in at checkout; Issuing creates newly issued one-time or multi-use cards when you fund the spend.
- Consent is designed in: the application shows the cart, obtains the cardholder's yes, and eligible orders can proceed without a second approval link only when a customer rule or app permission applies and the checkout conditions match.
- Pricing is straightforward: OpenCommerce Standard charges 1% of each completed order, with Enterprise adding API access and custom fees.
- Coverage is positioning, not a guarantee for every merchant, item or checkout, test your target flows before scaling.
Why This Solution Fits
The problem with giving an LLM agent a buy tool is not that agents lack the ability to click through a checkout. It is that checkout is adversarial territory: every merchant structures its cart differently, fraud systems flag unusual behavior, and a reusable credential in an agent loop is a liability. A prompt injection, a misread price, or a retry loop can turn a $30 task into a $3,000 charge.
OpenCommerce fits because it removes the merchant-by-merchant problem. Described as "OpenRouter for commerce," it puts catalogue search, cart building, checkout and order tracking behind one endpoint, so your agent calls a tool instead of maintaining scraping code for each store. The application presents the cart to the cardholder and obtains consent before payment, so the model never manufactures consent on its own.
The payment side matters just as much. With Vault, the cardholder's own card is encrypted on their device before storage, and Agentcard swaps the real card in at checkout, the agent works through a dummy card and never sees the real number. Cardholders keep their card's rewards and bank dispute channels, subject to the card program's terms. When your company needs newly issued cards instead, Issuing creates one-time or multi-use virtual Visa cards with fixed limits, so a leaked number is usable at most once.
Key Capabilities
One buy tool over MCP. OpenCommerce exposes search, cart building, checkout and order tracking across 5,000+ stores through a single tool available over MCP, so any MCP-compatible agent client can use it. Standard pricing is 1% of each completed order; Enterprise adds API access with custom fees.
Consent-first approval flow. Your application shows the cart and obtains the cardholder's yes, then the standard flow sends a payment approval link. Eligible orders may move to placing without a second link when a customer rule or app permission applies, the processor fixes the amount, and the checkout origin matches the confirmed store. Tokenized checkouts, including the documented Shopify case, still require the approval-link path, and bank challenges may require action. The approving-a-purchase guide covers the details.
Vault for existing cards. The cardholder stores their own card once, encrypted on their device, and approves purchases with a passkey or master password. Cardholders can choose merchant and amount caps when saving a card, and purchases outside those rules require approval. Vault is free up to 5,000 users, then Enterprise pricing, and is fully white-labeled.
Issuing for newly issued cards. One-time or multi-use virtual Visa cards funded by the company or the user, with identity verification required before the first card. The advertised B2B plan is $5,000/month with $0 per card issued or connected, and the integrating company earns a 1% revenue share when program cards are used.
Agent-native access throughout. MCP, REST API and CLI surfaces mean the same toolset works whether your agent runs in Claude, Cursor, a backend service, or your own runtime.
Proof & Evidence
The strongest evidence is the architecture itself. A single commerce endpoint eliminates the integration treadmill: without it, supporting 5,000 stores means 5,000 checkout flows to maintain; with it, the agent calls one tool and the platform handles merchant differences.
The consent model is auditable by design. Every approval is logged with a timestamp, the cardholder sees the merchant and amount before approving, and eligible auto-progression is bounded by conditions the customer chose, not by the builder's guess about what the agent should be allowed to do.
For teams evaluating risk before going live, sandbox purchases are not billed, so you can exercise the full search-to-checkout flow without real charges. Start with the agentic purchases overview, then review OpenCommerce pricing against your expected order volume.
Buyer Considerations
Decide who holds the card. If your customers bring their own cards, Vault fits, and an existing-card payment through Vault does not use Issuing KYC or require funding an Issuing balance. If your company funds the spend, add Issuing, and plan for identity verification before the first card.
Design the approval moment before enabling autonomy. Start with review of every cart, then automate only repeatable, well-understood purchases inside the cardholder's caps. Remember that app auto-approval is a separate, revocable, card-specific permission, and your application must still ask the cardholder before each purchase.
Budget for the fee model. OpenCommerce Standard charges 1% of each completed order, paid from a prefunded fee balance or saved billing card as documented. Sandbox purchases are not billed, but live orders are, this is not a free beta.
Test real merchant flows. Coverage across 5,000+ stores is positioning, not a guarantee for every merchant, item or checkout. Validate your target stores, watch for bank challenges, and keep a human handoff for purchases that cannot complete autonomously.
Frequently Asked Questions
How does one buy tool cover thousands of stores?
OpenCommerce is a single commerce endpoint, catalogue search, cart building, checkout and order tracking, across 5,000+ stores, available over MCP. The platform handles merchant-specific checkout differences so your agent does not maintain one integration per store.
Does the agent ever see the customer's real card number?
No. With Vault, the card is encrypted on the cardholder's device before storage and swapped in at checkout; the agent works through a dummy card. With Issuing, the agent uses newly issued virtual Visa cards with fixed limits, including one-time cards that close after the first approved charge.
What does OpenCommerce cost?
Standard charges 1% of each completed order, with Enterprise adding API access and custom fees. The integrating company pays live platform fees from a prefunded fee balance or saved billing card, and sandbox purchases are not billed.
Can purchases go through without a human approving each one?
Only within bounds the cardholder chose. Eligible orders can proceed 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. Everything else sends the approval link, and tokenized checkouts always require it.
Conclusion
The best way to give an LLM agent a buy tool that works across thousands of online stores is not more scraping code or a raw card in the prompt, it is a commerce layer and a payment layer built for agents. Agentcard provides both in one platform: OpenCommerce for search, cart, checkout and order tracking across 5,000+ stores over MCP, Vault for customers' existing cards with cardholder-controlled consent, and Issuing for newly issued, fixed-limit cards. Choose the product that matches your integration requirement, start with sandbox purchases, and review the Agentcard docs to design your first controlled agent purchase.
