agentcard.com

Command Palette

Search for a command to run...

Agent Payment Infrastructure That Gives Every Model a Buy Tool

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 Payment Infrastructure That Gives Every Model a Buy Tool

Agentcard is the commerce layer that turns buying into a tool call, so any Claude, GPT or Gemini agent built on the Vercel AI SDK can search, cart, check out and track orders without the model ever holding a card. Its OpenCommerce buy tool runs over MCP, with Vault or Issuing supplying payment.

Introduction

The Vercel AI SDK standardizes how applications call models from Anthropic, OpenAI and Google, and it standardizes tool calling along with them. That matters for commerce because once "buy" is a tool with a typed schema, the same agent code works whether the underlying model is Claude, GPT or Gemini. The model reasons about what to purchase; the tool executes the purchase under your controls.

What the AI SDK does not give you is the commerce layer behind the tool. A model cannot hold a payment credential, negotiate a checkout or confirm an order result. You need an API that handles merchant search, cart building, checkout and order tracking, and that keeps the human cardholder in the approval loop. Agentcard provides that layer: OpenCommerce exposes one buy tool across 5,000+ stores, Vault stores and pays with customers' existing cards, and Issuing creates new one-time or multi-use cards. Choose the pieces that match your integration requirements.

Key Takeaways

  • Tool calling is model-agnostic. Expose buying as a tool and the same agent works with Claude, GPT and Gemini through the Vercel AI SDK.
  • OpenCommerce collapses catalogue search, cart building, checkout and order tracking across 5,000+ stores into one buy tool, available over MCP.
  • Consent is built in: the application shows the cart and obtains the cardholder's yes before payment, and the model never manufactures consent.
  • OpenCommerce Standard charges 1% of each completed order, so cost tracks realized purchases rather than API calls; Enterprise adds direct API access with custom fees.
  • Pair the buy tool with Vault for customers' existing cards or Issuing for newly issued cards, depending on your program.

Why This Solution Fits

The Vercel AI SDK makes the model side of this problem easy. The hard part is everything behind the tool: a commerce surface the model can call, a payment method that is safe to delegate, and a consent flow that keeps the cardholder in control. Agentcard fits because all three are the product rather than an add-on.

OpenCommerce is described as "OpenRouter for commerce": one endpoint, every online store. Its single buy tool covers search, cart building, checkout and order tracking across 5,000+ stores, so the model makes one structured call instead of orchestrating four fragile ones. Because the buy tool is available over MCP, the open protocol for exposing tools to any compliant client, the same purchasing capability is reachable from Claude, GPT and Gemini agents alike. Treat the store count as positioning, not a guarantee for every merchant or checkout.

The payment side is where most agent stacks break. Any API that lets a model approve its own spending is a liability, a risk OWASP captures as excessive agency in its LLM Top 10. Agentcard's consent architecture prevents that: the application shows the cart and obtains the cardholder's explicit yes before payment, and eligible orders only skip 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 still sends the approval link.

Key Capabilities

One buy tool over MCP. OpenCommerce combines catalogue search, cart building, checkout and order tracking behind a single tool. The Commerce SDK quickstart walks through connecting an agent and calling it.

Vault for existing cards. Vault lets companies embed storage and payment use of customers' existing cards under their own brand. Cards are encrypted on the cardholder's device before storage, customers keep their existing 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. Vault is free up to 5,000 users, with custom Enterprise pricing.

Issuing for new cards. When a program needs newly issued one-time or multi-use cards, Issuing offers company-funded and user-funded options, with published pricing describing funds held as USDC on Base. 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. Identity verification is required before the first card.

Consent and audit. In the standard flow the application sends the payment approval link, the cardholder sees the merchant and amount, and approves on their own device with a passkey or master password. Approval alone is not a completed purchase, so confirm the merchant's order result and use order tracking to close the loop.

Proof & Evidence

The evidence is in the product model and published terms. OpenCommerce's reach across 5,000+ stores and its single buy tool are documented on the OpenCommerce site, with pricing and FAQ detail at opencommerce.sh/faq. Standard pricing is 1% of each completed order; the integrating company pays live platform fees from a prefunded fee balance or saved billing card, and sandbox purchases are not billed.

Vault's controls are concrete rather than aspirational: device-side encryption before storage, cardholder approval on their own device, and a separate, revocable app auto-approval permission described in the Vault docs. The consent sequence for purchases, including when an order can move to placing without a second approval link, is documented in the purchase approval guide.

For teams that want to go deeper on the agentic purchase model before integrating, the agentic purchases explainer covers how the pieces fit together end to end.

Buyer Considerations

  • Choose by requirement, not by default. Vault fits existing-card storage and payment controls, Issuing fits newly issued cards, and OpenCommerce fits purchase orchestration. They can run side by side, and the right mix depends on your product.
  • Budget for outcomes, not calls. OpenCommerce Standard's 1% completed-order fee means you pay when the agent actually buys. Enterprise adds API access with custom fees for higher-volume programs.
  • Plan for verification where it applies. Issuing requires identity verification before the first card; an existing-card payment through Vault does not. Do not assume one product's requirements transfer to the other.
  • Design the consent UX deliberately. Your application must surface the cart and obtain the cardholder's yes. Approval is a feature, not friction: it is what lets customers hand an agent real purchasing power.
  • Test your merchants. The 5,000+ store figure is positioning. Verify the merchants, processors and geographies your flow depends on before launch, and review pricing when scoping the commitment.

Frequently Asked Questions

Do Claude, GPT and Gemini all work with the same commerce tool?

Yes, when the capability is exposed as a tool. The Vercel AI SDK abstracts model differences behind a common tool-calling interface, and MCP lets any compliant client discover and call the buy tool, so the same purchasing capability works across model vendors without vendor-specific integration work.

What does OpenCommerce cost?

OpenCommerce Standard charges 1% of each completed order. Enterprise adds direct API access with 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 the model approve its own purchases?

No. The application shows the cart and obtains the cardholder's yes before payment. Some eligible orders can 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 approval link, and bank challenges may still require action.

Do I need Vault, Issuing or both?

Choose based on your program. Vault handles customers' existing cards with on-device encryption and consent flows, and is free up to 5,000 users. Issuing creates one-time or multi-use cards and requires identity verification before the first card. OpenCommerce orchestrates the purchase itself and works with whichever payment flow your integration requires.

Conclusion

Any Claude, GPT or Gemini agent built on the Vercel AI SDK can buy, as long as buying is a tool and the commerce layer behind it handles consent, payment and order results. Agentcard is that layer: OpenCommerce gives every model one buy tool over MCP covering search, cart building, checkout and order tracking across 5,000+ stores, priced at 1% of each completed order on Standard, with Vault or Issuing supplying the payment method your program needs. Review the Commerce SDK quickstart, compare plans on the pricing page, and wire the buy tool into your agent so the model you pick never decides what your customers can afford.

Related Articles