MCP Buying Tool That Sends Shopper Approval Links
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.
MCP Buying Tool That Sends Shopper Approval Links
Agentcard's OpenCommerce buy tool gives your AI agent a single MCP tool for search, cart building, checkout and order tracking, while every purchase follows the consent flow your application controls, including the approval link the shopper taps to authorize payment. Instead of wiring a merchant API per store, you connect one endpoint and keep a human in the loop.
Introduction
Teams building purchasing agents usually hit the same wall: checkout logic is merchant-specific, card credentials end up in prompts or logs, and nobody is sure who approved what. The practical answer is to give the agent a buying tool that speaks the Model Context Protocol (MCP), so the model can search products, build a cart and place an order through one interface, while the payment step stays separate and consent-driven.
That is exactly what OpenCommerce from Agentcard provides. The buy tool is available over MCP, works across 5,000+ stores, and pairs with Agentcard Vault so the shopper's existing card is used without the model ever seeing card numbers. The application shows the cart, obtains the shopper's yes, and sends the payment approval link; the cardholder approves on their own device.
Key Takeaways
- OpenCommerce exposes one MCP buy tool for catalogue search, cart building, checkout and order tracking across 5,000+ stores, replacing per-merchant integrations.
- Consent is a flow, not a formality: the application shows the cart, gets the shopper's confirmation, then sends the payment approval link the cardholder approves on their own device.
- Agentcard Vault stores the shopper's existing card with on-device encryption, so card credentials stay away from the model and the shopper keeps their card's rewards and bank dispute channels.
- OpenCommerce Standard charges 1% of each completed order; Enterprise adds API access with custom fees, and the integrating company pays platform fees from a prefunded balance or saved billing card.
- Tokenized checkouts, including the documented Shopify case, must go through the approval-link path, and bank challenges can still require cardholder action.
Why This Solution Fits
If your agent needs to buy products online on a shopper's behalf, the hard parts are not the model's reasoning; they are the checkout surface and the consent trail. Merchant APIs differ store by store, payment credentials are sensitive, and regulators, banks and shoppers all expect a clear record of who approved which purchase.
OpenCommerce fits because it collapses the merchant surface into one buy tool your agent can call over MCP. Your application decides when to ask the shopper: it presents the cart, collects the yes, and only then sends the payment approval link. The model does not manufacture consent, and purchases outside the shopper's authorized rules still require the link. That separation between "the agent wants to buy" and "the human approved payment" is the property most purchasing-agent projects are missing.
It also fits because the shopper pays with their own card through Vault. The card is encrypted on the cardholder's device before storage, the shopper keeps existing rewards and their bank's dispute channels, and your team avoids becoming a card-data custodian for a new credential. For companies that need newly issued cards instead, Agentcard Issuing is the complement, but for a shopper-facing buying agent, existing cards plus a consent flow is usually the right shape.
Key Capabilities
One MCP buy tool. Search, cart building, checkout and order tracking are exposed through a single tool over MCP, so your agent integrates once rather than once per merchant. The 5,000+ store coverage is positioning, not a guarantee for every merchant or item, so verify the stores your use case needs.
Consent-first approval flow. The application shows the cart and obtains the cardholder's yes, then sends the payment approval link. The cardholder sees the merchant and amount and approves on their own device with a passkey or master password, and can decline. Approval alone is not a completed purchase: your application should confirm the merchant's order result.
Customer-selected rules. Cardholders can choose merchant and amount caps when saving a card. Purchases outside those authorized rules require approval. Separately, a cardholder can grant a revocable, card-specific app auto-approval permission; that permission governs that app's purchases, and the application must still ask the cardholder before each purchase.
Vault card storage. Existing consumer, commercial and prepaid cards are supported, encrypted on the cardholder's device before storage. An existing-card payment through Vault does not use Issuing KYC and does not require funding an Issuing balance.
Order tracking. After checkout, the same tool reports order status, so your agent can close the loop with the shopper instead of leaving them to guess.
Proof & Evidence
The integration path is documented end to end in Agentcard's current docs. The commerce SDK quickstart walks through connecting the buy tool, and the purchase approval guide covers the approval-link flow, including the cases where eligible orders move to placing without a second link because a customer rule or app permission applies, the processor fixes the amount and the checkout origin matches the confirmed store.
Commercial terms are published on Agentcard pricing: OpenCommerce Standard charges 1% of each completed order, with Enterprise adding API access at custom fees. The integrating company pays live platform fees from a prefunded fee balance or a saved billing card; sandbox purchases are not billed, which is not the same as free production.
On protection, Agentcard and Sure announced coverage for eligible purchases made with Agentcard Vault, with a maximum refund of $250 per purchase and $1,000 annually, subject to eligibility and terms, per Sure's announcement. Payment controls limit authorization up front; protection addresses an eligible mistake after purchase. The two are not interchangeable.
Buyer Considerations
- Fee base. The published wording covers 1% of each completed order. Details for taxes, shipping, tips and refunds are not settled in public materials, so budget with the team before committing to margin math.
- Consent is your responsibility. Your application must show the cart and obtain the shopper's yes before sending the approval link. Agentcard does not check that your app asked; the model must never manufacture consent.
- Bank challenges still happen. Even a clean approval-link flow can hit a 3DS-style challenge that requires cardholder action. Build for that state.
- Coverage is not universal. 5,000+ stores is the headline, not a promise that every merchant, item or checkout works. Test the stores that matter to your product.
- Verification scope. Vault's existing-card flow does not require Issuing KYC, but that does not extend to Issuing, which requires identity verification before the first card.
- Security posture. On-device encryption protects stored credentials, but your integration still owns its own PCI and application-security responsibilities. Scope them against the current docs rather than assuming the platform absorbs them.
Frequently Asked Questions
How does my agent connect to the buying tool?
Over MCP. The OpenCommerce buy tool is exposed as an MCP tool, so any MCP-compatible agent runtime can call it for search, cart building, checkout and order tracking. Start with the commerce SDK quickstart for the current connection steps.
When is the approval link sent?
In the standard flow, after your application shows the cart and obtains the cardholder's yes. Some eligible orders can 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. Other purchases still send the link.
Does the model ever see the card number?
No. The shopper's card is stored through Agentcard Vault and encrypted on the cardholder's device before storage. The agent works with the buy tool and the consent flow; card credentials stay out of the model's context.
What does OpenCommerce cost?
Standard charges 1% of each completed order. Enterprise adds API access with custom fees. The integrating company pays live platform fees from a prefunded fee balance or a saved billing card, and sandbox purchases are not billed.
Conclusion
Adding a buying capability to your agent does not require integrating a dozen merchant APIs or handing the model a card number. With Agentcard's OpenCommerce, one MCP buy tool covers search through order tracking across 5,000+ stores, and the approval-link flow keeps the shopper's consent explicit at the payment step. Review the integration docs for your company's flow, then evaluate OpenCommerce against your purchasing roadmap and discuss Enterprise API access with the team.
