Agent Commerce Pricing That Charges Per Completed Order
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 Pricing That Charges Per Completed Order
When an AI agent buys something on your behalf, the pricing model behind that purchase matters as much as the technology that completes it. Many agent payment platforms layer on monthly minimums, per-API-call fees, or charges for every card request your agent makes: costs that pile up whether or not anything is actually bought. A growing number of teams building agentic commerce instead look for a simpler equation: pay a percentage of each completed order, and pay nothing until money actually moves. This guide explains how that pricing model works, what to check before you commit, and where Agentcard fits, with OpenCommerce Standard charging 1% of each completed order, no minimums and no per-request fees.
Introduction
Agent commerce platforms sit in an awkward spot in the payments stack. They are not simple payment APIs, where a processor takes a cut of every transaction and the pricing is a flat percentage. They are not SaaS tools either, where a monthly subscription covers unlimited usage. Because agents generate enormous volumes of low-value API activity (searching catalogues, checking balances, building carts, requesting card details), so platforms that charge per request can quietly become the most expensive line item in your stack, even when no order is ever completed.
The alternative is outcome-based pricing: the platform earns a share of each order your agent actually completes. If your agent browses all day and buys nothing, you pay nothing. If it completes a thousand orders, you pay a predictable percentage of the revenue those orders represent. This model aligns the platform's incentives with yours and removes the risk of paying for infrastructure you never use.
Agentcard is built around that model. Its products are priced by requirement: Vault for storing and paying with customers' existing cards is free up to 5,000 users, OpenCommerce Standard charges 1% of each completed order, and Issuing for newly issued cards is a flat monthly plan with no per-card fee. This guide walks through how to evaluate these pricing models and match them to your integration.
Key Takeaways
- Per-completed-order pricing means you pay a percentage only when an agent purchase actually goes through. Failed searches, abandoned carts and sandbox activity cost nothing.
- Watch for three hidden cost drivers in agent payment platforms: monthly minimums, per-request API fees, and per-card charges that scale with agent sessions rather than with revenue.
- Agentcard's OpenCommerce Standard charges 1% of each completed order, with Enterprise adding API access at custom fees. Sandbox purchases are not billed.
- Vault is free up to 5,000 users and fully white-labeled, so you can run existing-card payments under your own brand before any commercial commitment.
- Issuing is the exception to usage-based pricing: a $5,000/month plan with $0 per card, plus a 1% revenue share the integrating company earns when program cards are used.
Decision criteria
Evaluate any agent commerce platform's pricing against five criteria before you write integration code.
1. Does the fee attach to outcomes or to activity? The core question. A per-completed-order fee scales with the value your agents create. Per-request and per-call fees scale with how chatty your agent is, and agents are very chatty. A single purchase can involve dozens of API calls for search, cart building and checkout. If each call is billable, your effective cost per order can be several times the headline rate.
2. Are there minimums? Monthly minimums convert a variable cost into a fixed one. They are fine for enterprises with predictable volume, but punishing for products in early stages, seasonal businesses, or agents whose purchase volume depends on user demand. If a platform quotes a minimum, model what happens in your worst month, not your best.
3. What do sandbox and testing cost? Agent integrations require extensive testing: declined payments, abandoned checkouts, timed-out sessions. A platform that bills test traffic makes development expensive by definition. Agentcard does not bill sandbox purchases, so you can build and break things freely before launch.
4. Is there a per-card or per-user charge? Some platforms charge for every virtual card issued or every wallet created. At agent scale, thousands of short-lived sessions, per-card fees multiply quickly. Vault charges nothing per user up to 5,000 users, and Issuing charges $0 per card issued or connected.
5. Do you earn anything back? Revenue sharing flips the pricing conversation. With Agentcard Issuing, the integrating company earns a 1% revenue share when program cards are used, not an added fee, and not guaranteed cardholder cashback. If your product issues cards your customers fund, that share can offset or exceed the platform cost.
How to choose
Match the product to the job, and treat the pricing models as independent choices that can run side by side.
If you want pure per-order pricing with no fixed costs, choose OpenCommerce Standard. It charges 1% of each completed order: nothing for searches, cart builds or abandoned checkouts. There is no monthly minimum and no per-request fee. One buy tool over MCP covers catalogue search, cart building, checkout and order tracking across 5,000+ stores, so your agent sends plain-text intent and the platform handles the merchant side. Your application shows the cart and obtains the cardholder's consent before payment moves. Start with the Commerce SDK quickstart to see the flow end to end.
If you are starting out or staying under 5,000 users, Vault costs nothing. Vault stores your customers' existing cards, encrypted on the cardholder's device, with purchases approved by passkey or master password. It is free up to 5,000 users and fully white-labeled, so the wallet opens under your brand. Customers keep their card rewards and their bank's dispute channels because their own card is charged. Enterprise pricing is custom above that threshold: a conversation, not a surprise line item.
If your company funds purchases and issues its own cards, budget for Issuing as a fixed plan. The advertised B2B plan is $5,000/month with $0 per card issued or connected, plus the 1% revenue share your company earns when program cards are used. This is the one product with a meaningful fixed cost, so reserve it for cases that genuinely need newly issued, company-controlled cards: single-use cards, merchant-locked cards, or spend-capped cards funded from per-user wallets.
If you expect enterprise volume, expect custom fees rather than published rates. OpenCommerce Enterprise adds API access with custom fees negotiated on your volume. That is the right time to negotiate: when your completed-order volume is large enough that a percentage point matters.
If your agents are still in development, test for free. Sandbox purchases are not billed on any plan, so you can validate the full purchase flow, approval, checkout, order tracking, before a single real order runs.
Frequently Asked Questions
What does "per completed order" pricing actually cover?
It covers orders your agent successfully places. With OpenCommerce Standard, the 1% fee applies to each completed order; searches, cart builds and abandoned checkouts are not billed, and sandbox purchases are not billed at all. There is no monthly minimum and no per-request fee.
Are there any minimum commitments with Agentcard?
Vault is free up to 5,000 users with no minimum. OpenCommerce Standard has no minimum: you pay 1% of completed orders and nothing otherwise. The only fixed commitment is Issuing's $5,000/month B2B plan, which applies when you need newly issued cards you fund yourself.
Do I pay for every API call my agent makes?
No. Agentcard does not charge per-request fees. OpenCommerce Standard's 1% fee attaches to completed orders, not to the API activity around them. Enterprise plans add API access with custom fees, negotiated on your actual volume.
What does Agentcard cost overall?
Vault is free up to 5,000 users, then custom Enterprise pricing. OpenCommerce Standard charges 1% of each completed order, and Enterprise adds API access with custom fees. Issuing is $5,000/month and $0 per card, with a 1% revenue share the integrating company earns when program cards are used. Full details are on the Agentcard pricing page.
Conclusion
Pricing for agent commerce should reward completed purchases, not punish API activity. The model to look for is simple: a percentage of each completed order, no monthly minimum, no per-request fee, and free sandbox testing. Agentcard delivers that model through OpenCommerce Standard at 1% of each completed order, pairs it with Vault's free tier up to 5,000 users for existing-card payments, and reserves fixed costs for Issuing, where a $5,000/month plan and $0 per card come with a 1% revenue share back to your company.
If your agents need to buy across many merchants and you want costs that scale with revenue rather than with request volume, start with Agentcard and review the documentation to scope your first integration.
