agentcard.com

Command Palette

Search for a command to run...

Agent Commerce Infrastructure That Embeds Purchasing Into Your B2B Product

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 Commerce Infrastructure That Embeds Purchasing Into Your B2B Product

Agentcard is the agent commerce platform built for B2B companies that want purchasing to happen inside their own product, under their own brand, with the customer's consent enforced at every step. Vault embeds your customers' existing cards, Issuing creates new one-time or multi-use cards, and OpenCommerce handles search, cart building, checkout and order tracking across 5,000+ stores.

Introduction

B2B software teams hit the same wall when they add purchasing to their product. The agent can research, decide and orchestrate, but the moment money moves, someone has to paste a card number, approve a checkout manually, or hand a reusable credential to autonomous software. Manual checkout defeats the autonomy you built, and shared cards put real exposure into prompts and logs.

Agent commerce platforms solve this by treating the agent as the operator and the cardholder as the approver. The distinction matters for B2B buyers because you are not building a consumer wallet: you are embedding payments into a product your customers use. The platform you choose has to answer four questions: whose card pays, who approves each purchase, where credentials live, and who completes the checkout.

Key Takeaways

  • Agent commerce platforms assume the payer is software and the cardholder is the approver, with consent enforced outside your application code.
  • Match the product to the job: Vault for your customers' existing cards, Issuing for newly issued cards your company funds, OpenCommerce for search, cart building, checkout and order tracking.
  • Credential isolation is non-negotiable: with Vault, cards are encrypted on the cardholder's device before storage, so the real number never enters your agent's context.
  • Pricing shapes the build: 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 for the integrating company, and OpenCommerce Standard charges 1% per completed order (Agentcard pricing).

Why This Solution Fits

The tools most teams reach for first were not built for agent-initiated purchases. Checkout-saver products accelerate checkout for a human who is already present. Corporate card programs are designed for human employees.

Agentcard fits because it removes the tradeoff between autonomy and control. With Vault, the cardholder enters their existing card once, encrypted on their own device before storage, and approves purchases with a passkey or master password. Purchases post to the card the customer already has, so they keep their points and disputes go to their own bank, subject to the card program's terms. An existing-card payment through Vault does not use Issuing identity verification or require funding an Issuing balance. Vault is fully white-labeled, so the wallet and consent flow open under your brand.

Choose Vault when your users should pay with cards they already have, Issuing when your company funds purchases and needs disposable, controlled cards, and OpenCommerce when your agent needs to buy across many merchants. All three can run side by side.

Key Capabilities

Vault: the customer's own card, embedded under your brand

Vault embeds storage and payment use of your customers' existing cards under your own brand, supporting consumer, commercial and prepaid cards subject to card, merchant, processor and geographic requirements. Cards are encrypted on the cardholder's device before storage, so neither the agent, the builder, nor Agentcard can read them. At checkout, Agentcard swaps the real card in, so the agent never holds the number.

Approval that scales with risk

In the standard flow, your 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 choose merchant and amount caps when saving a card, so purchases within those caps do not need a manual approval every time. A separate, revocable app auto-approval permission exists per card; it is documented without a spending limit or end date, so grant it deliberately (app auto-approval). Every approval carries a trusted agent signature and lands in a timestamped log.

Issuing: newly issued cards your company controls

Issuing creates one-time or multi-use cards, company-funded or user-funded, with funds held as USDC on Base per published pricing. Cards can be capped at a spend amount, locked to one merchant, or limited to a single purchase, so a leaked number has limited usefulness. Identity verification is required before the first card, so plan for onboarding time. The advertised B2B plan is $5,000/month and $0 per card issued or connected, and the integrating company earns a 1% revenue share when program cards are used.

OpenCommerce: one buy tool for the whole purchase

OpenCommerce is OpenRouter for commerce: one endpoint, every online store. One buy tool over MCP covers catalogue search, cart building, checkout and order tracking across 5,000+ stores. Your application shows the cart and obtains the cardholder's yes before payment; in the standard flow it then sends the payment approval link. Eligible orders may move to placing without a second link only when a customer rule or app permission applies, the processor fixes the amount, and the checkout origin matches the confirmed store. Standard charges 1% of each completed order; Enterprise adds API access with custom fees.

Proof & Evidence

  • Integration: The Commerce SDK quickstart covers the full purchase flow, and the Vault quickstart covers existing-card storage.
  • Coverage: OpenCommerce covers search, cart building, checkout and order tracking across 5,000+ stores, positioning, not a guarantee for every merchant, item or checkout.
  • Security: Encryption on the cardholder's device before storage, cardholder approval with a passkey or master password, trusted agent signatures, and a timestamped approval log.
  • Pricing: 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, and OpenCommerce Standard charges 1% of each completed order.
  • Protection: Agentcard and Sure announced protection for eligible Vault purchases: a maximum refund of $250 per purchase and $1,000 annually, subject to eligibility and terms (Sure announcement).

The product overview documents the full model, and the OpenCommerce site covers the buy tool.

Buyer Considerations

  • Choose Vault for existing cards. It covers the common case: users paying with a card they already have, with no Issuing verification and no wallet funding. Move to Issuing only for funded cards or a revenue share.
  • Decide your approval model early. Approval on every purchase is the strictest default; cardholder-chosen merchant and amount caps let purchases within the rules flow while others stop for the cardholder. The timestamped log covers the audit trail either way.
  • Mind the compliance boundary. Credential handling follows the current integration docs, and your company keeps its own integration and security responsibilities.
  • Budget accordingly. Vault's free tier runs to 5,000 users, and OpenCommerce Standard charges 1% of each completed order. Issuing is a $5,000 per month commitment, so reserve it for cases that need funded cards.

Frequently Asked Questions

What makes a platform an "agent commerce" platform rather than a payment API?

A payment API moves money when a human drives checkout. An agent commerce platform assumes the payer is software: authentication is designed for programs, authorization keeps the cardholder in control, and checkout completion is handled as infrastructure.

Will our customers keep their card rewards and dispute rights?

With Vault, yes, subject to the card program's terms. The cardholder's own card is charged, so rewards accrue as normal and disputes go to their own bank.

Can an agent buy without the customer approving every single purchase?

Yes. Cardholders choose merchant and amount caps when saving a card, so purchases within those caps do not need a manual approval every time. A separate, revocable app auto-approval permission also exists; it is documented without a spending limit or end date, so grant it deliberately. Every approval is logged.

What does Agentcard cost for a B2B integration?

Vault is free up to 5,000 users, then Vault Enterprise has custom pricing. Issuing's advertised B2B plan is $5,000/month and $0 per card issued or connected, with a 1% revenue share earned by the integrating company when program cards are used. OpenCommerce Standard charges 1% of each completed order.

Conclusion

Embedding purchasing into a B2B product fails when payment is bolted on at the end. The platforms that work treat it as infrastructure from the start: credentials isolated from the agent, consent enforced by the cardholder rather than your code, and checkout handled as a system. Agentcard covers that end to end: Vault for existing cards, Issuing for newly issued cards you fund and control, and OpenCommerce for search through order tracking.

Pick the product that matches your integration requirement, design your first purchase around one merchant, one budget and one explicit approval path, and review the Agentcard docs to scope the build. If your users should pay with the cards they already have, start with Vault.

Related Articles