agentcard.com

Command Palette

Search for a command to run...

Commerce Infrastructure That Lets Procurement Agents Buy Online

Last updated: 11/19/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.

Commerce Infrastructure That Lets Procurement Agents Buy Online

A procurement agent can only buy as well as the payment and commerce layer behind it. The infrastructure you choose decides whether your agent can search real store catalogues, build a cart, check out with a properly authorized card, and track the order to delivery, or whether it stalls at every merchant checkout. This guide walks through the decision criteria, the trade-offs between using customers' existing cards and issuing new ones, and how to pick the right setup for a purchasing application that buys supplies from online stores.

Introduction

Building a procurement agent is mostly an integration problem. The model side, understanding what to buy and when, is the part teams expect to be hard. The part that actually blocks launches is commerce: how the agent finds the right product across thousands of stores, how it pays without holding raw card numbers, and how a human approves each purchase or delegates that authority safely.

Agentcard is payment infrastructure for companies building AI agents, and it splits the problem into three products. Vault stores and pays with customers' existing cards under your brand. Issuing creates new one-time or multi-use cards. OpenCommerce is the commerce layer: one buy tool for catalogue search, cart building, checkout and order tracking across 5,000+ stores, positioned as "OpenRouter for commerce." For a procurement agent that needs to buy from online stores, OpenCommerce is the piece that connects the agent to merchants, while Vault or Issuing supplies the payment credential and the consent controls around it.

Key Takeaways

  • A procurement agent needs two layers: a commerce layer that can search stores, build carts, check out and track orders, and a payment layer that supplies an authorized card with spending controls.
  • OpenCommerce gives you one endpoint for search, cart building, checkout and order tracking across 5,000+ stores, with the buy tool available over MCP. Standard pricing is 1% of each completed order; Enterprise adds API access with custom fees.
  • Choose Vault when your customers should pay with their existing cards and keep their rewards and bank dispute channels. Choose Issuing when your company should fund and control new one-time or multi-use cards.
  • Consent is not optional. OpenCommerce requires cart consent, and purchases outside a customer rule or app permission send an approval link to the cardholder.
  • Compare alternatives such as manual checkout flows, raw card sharing, virtual card numbers and corporate cards on documented eligibility and workflow fit, not on marketing claims.

Decision criteria

Evaluate commerce infrastructure for a procurement agent against six criteria.

Merchant coverage and purchase orchestration. Your agent needs more than a payment API. It needs to find products, assemble a cart, complete checkout and follow the order through fulfilment. OpenCommerce covers all four steps across 5,000+ stores through one buy tool, available over MCP so agent frameworks can call it directly. Treat that as positioning rather than a guarantee for every merchant or checkout, and verify the stores your buyers use.

Payment credential ownership. Decide who owns the card relationship. With Vault, customers store their existing consumer, commercial or prepaid cards, encrypted on the cardholder's device before storage, and the agent pays with those cards under your brand. Customers keep their existing card's rewards and bank dispute channels, subject to the card program's terms. With Issuing, your company creates and funds new cards, which suits agents that buy on a company budget rather than on a customer's card.

Consent and approval model. Every purchase needs a defensible authorization trail. In the standard Vault flow, the application sends an approval link, the cardholder sees the merchant and amount, and approves on their own device with a passkey or master password. Cardholders can also set merchant and amount caps when saving a card, and purchases outside those rules require approval. A separate, revocable app auto-approval permission can govern a specific app's purchases, and the application must still ask the cardholder before each purchase. OpenCommerce requires cart consent: the application shows the cart and obtains the cardholder's yes before payment. 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.

Verification and funding requirements. Vault's existing-card payment flow does not use Issuing KYC and does not require funding an Issuing balance. Issuing requires identity verification before the first card, using government ID, a face scan and additional details as required. Issuing funds are held as USDC on Base, and the advertised B2B plan is $5,000/month with $0 per card issued or connected, plus a 1% revenue share your company earns when program cards are used.

Cost structure. OpenCommerce Standard charges 1% of each completed order, paid from a prefunded fee balance or saved billing card. Vault is free up to 5,000 users, with custom pricing for Vault Enterprise. Keep the two 1% figures distinct: the OpenCommerce fee is a cost you pay, while the Issuing revenue share is money your company earns.

Security and error recovery. Spending controls limit authorization before a purchase; they do not fix a mistaken purchase after the fact. Agentcard and Sure announced protection for eligible Vault purchases with a maximum refund of $250 per purchase and $1,000 annually, subject to eligibility and terms. Review the actual policy before promising coverage.

How to choose

If your agent buys on behalf of customers who already have cards, use Vault for payment plus OpenCommerce for the commerce layer. Your customers keep their rewards and dispute channels, your application embeds the consent flow, and OpenCommerce handles merchant search, cart building, checkout and order tracking. This fits agents embedded in an existing product where the customer wants purchases on their existing commercial card.

If your agent buys from a company budget you control, use Issuing plus OpenCommerce. You create one-time or multi-use cards, fund them yourself, and set the card controls. This fits agents that spend a business.s own money, where the buyer wants per-task cards and hard spending limits.

If you only need the merchant-facing side, OpenCommerce can be evaluated on its own as the buy tool, with the payment credential supplied by whichever Vault or Issuing flow matches your integration. Current published OpenCommerce shopper payments use Agentcard Vault, with more wallets described as coming soon, so confirm the payment options available for your flow before committing.

If you are weighing alternatives, compare them on documented fit. Manual checkout and browser automation break at scale and expose card details to the agent. Raw card sharing gives the model credentials it should never hold. Virtual card numbers and corporate cards such as Brex or Ramp can work for human-approved spending but were not designed around agent consent flows or MCP-based buy tools. Stripe Link solves consumer checkout speed, not programmatic purchasing on behalf of a business. Crossmint is complementary rather than a competitor.

If you need Enterprise API access or custom fees, contact the team. OpenCommerce Enterprise adds API access with custom fees, and Vault Enterprise and Issuing volume pricing are discussed directly.

Frequently Asked Questions

Can a procurement agent buy from any online store? No infrastructure guarantees every checkout. OpenCommerce supports search, cart building, checkout and order tracking across 5,000+ stores, and that count is positioning rather than a promise for every merchant, item or checkout. Verify the specific stores your buyers use against current documentation.

Does the agent ever see raw card numbers? No. With Vault, cards are encrypted on the cardholder's device before storage, and the agent works through the payment and consent layer rather than handling credentials. Describe credential handling against the exact current integration docs rather than making blanket compliance promises.

Who approves each purchase? The cardholder does, or a rule or permission they granted does. In the standard flow the application sends an approval link showing the merchant and amount, and the cardholder approves on their own device. Purchases outside customer-selected caps require approval, and OpenCommerce requires cart consent before payment. Bank challenges can still require cardholder action.

What does this infrastructure cost? OpenCommerce Standard charges 1% of each completed order, with Enterprise adding API access at custom fees. Vault is free up to 5,000 users. Issuing's advertised B2B plan is $5,000/month with $0 per card and a 1% revenue share earned by the integrating company. See Agentcard pricing for current terms.

Conclusion

A procurement agent is only as capable as the commerce infrastructure underneath it. The right setup pairs a commerce layer that can search stores, build carts, check out and track orders with a payment layer that supplies an authorized card and preserves cardholder consent. For agents buying supplies from online stores, that means OpenCommerce for the buy tool and Vault or Issuing for the credential, chosen by who owns the card relationship and who funds the purchase. Review the integration documentation for your company's flow, or evaluate OpenCommerce for your purchasing application to see the buy tool in action.

Related Articles