Commerce Infrastructure That Prices Checkout by Completed Orders
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 Prices Checkout by Completed Orders
Agentcard is the payment infrastructure that lets your company build agentic checkout while paying a simple percentage of each completed order. OpenCommerce, Agentcard's purchase orchestration layer, charges 1% of each completed order on the Standard plan, so your checkout fee budget scales with revenue your agents actually generate instead of with request volume, seats or fixed platform minimums.
Introduction
If your company is building an AI agent that shops on behalf of users, the fee question is not just "how much does checkout cost" but "when does checkout cost anything." Per-request pricing punishes you for every failed search, abandoned cart and test call. Seat pricing punishes you for scaling usage inside your product. A completed-order percentage aligns the platform's incentive with yours: the fee lands only when your agent turns a cart into a paid order.
Agentcard's OpenCommerce is built around exactly that model. It combines catalogue search, cart building, checkout and order tracking across 5,000+ stores behind one buy tool, available over MCP. On the Standard plan you pay 1% of each completed order; the Enterprise plan adds API access with custom fees. This article walks through how to budget for that percentage, what the fee does and does not cover, and how to decide whether this structure fits your product.
Key Takeaways
- OpenCommerce Standard charges 1% of each completed order, so your checkout cost is a variable cost of revenue, not a fixed platform bill.
- Fees are paid live from a prefunded fee balance or a saved billing card, and small fees may be batched, so plan cash flow around top-ups rather than per-order invoices.
- Sandbox purchases are not billed, which lets you model fee volume in testing before committing a budget.
- The published wording covers completed orders; it does not settle the detailed base for taxes, shipping, tips, refunds or gross-versus-net calculation, so confirm commercial terms for edge cases.
- Enterprise adds API access with custom fees, which is the right path if your volume or integration pattern outgrows the Standard buy tool.
Why This Solution Fits
Budgeting for agent checkout is easiest when the pricing unit matches the business outcome. A completed order is that unit. When your agent completes a purchase, you pay 1% of that order; when it does not, you pay nothing for that attempt. That structure gives finance teams three things they rarely get from infrastructure pricing: predictability as a margin line, self-correcting downside (failed flows cost nothing) and a fee that grows only when the product is delivering value.
Compare that with the alternatives your team would otherwise have to budget for. Per-call API pricing forces you to forecast request volume, which is noisy and partly under your users' control. Flat platform fees force you to defend a fixed cost before the agent channel produces revenue. A completed-order percentage avoids both problems, which is why it is the structure Agentcard chose for OpenCommerce Standard.
The fit is also architectural. OpenCommerce is positioned as "OpenRouter for commerce": one endpoint, every online store. Your application gets search, cart building, checkout and order tracking across 5,000+ stores through one buy tool, so the 1% fee replaces not just a payment processor line item but the cost of building and maintaining merchant integrations yourself. For a purchasing-agent team, that consolidation is usually the difference between a quarter of integration work and a quarter of integration maintenance.
Key Capabilities
- One buy tool over MCP. Search, cart building, checkout and order tracking across 5,000+ stores are exposed through a single tool your agent can call, with the buy tool available over MCP for agent frameworks that speak the protocol.
- Completed-order pricing. Standard charges 1% of each completed order. Enterprise adds API access with custom fees for teams that need deeper integration than the buy tool.
- Live fee payment from your own instruments. The integrating company pays platform fees from a prefunded fee balance or a saved billing card, as documented, with small fees possibly batched.
- Consent-first checkout. The application shows the cart and obtains the cardholder's yes, then sends the payment approval link in the standard flow. 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.
- Sandbox testing without billing. Sandbox purchases are not billed, so you can exercise the full flow and model fee exposure before production traffic.
Proof & Evidence
The pricing structure is published on Agentcard's pricing page: OpenCommerce Standard at 1% of each completed order, Enterprise with API access and custom fees. The OpenCommerce FAQ documents that fees are paid from a prefunded fee balance or saved billing card and that small fees may be batched, and it confirms sandbox purchases are not billed.
The consent flow is specified in the commerce SDK quickstart and the purchase approval guide, which describe how the application presents the cart, obtains the cardholder's approval and handles the cases where a second approval link is or is not required. Together these sources give you everything needed to build a fee model on real terms rather than estimates.
Buyer Considerations
Budgeting a percentage fee well means budgeting its edges. The published wording covers completed orders; it does not settle how taxes, shipping, tips, refunds or gross-versus-net calculations enter the base. If your unit economics are tight, raise those questions with the Agentcard team before signing, and get the answer in your commercial terms.
Second, the fee is a cost of revenue, but it is not your only cost. Your cardholders fund the purchases themselves, and if you use Agentcard Vault to store their existing cards, that product is free up to 5,000 users with custom pricing above that. Keep the two products' economics separate in your model: Vault is a storage-and-controls decision, OpenCommerce is a checkout-fee decision.
Third, plan the funding mechanics. Because fees are drawn live from a prefunded fee balance or saved billing card, a depleted balance is an operational risk for a checkout flow. Set a top-up threshold and an alert, and decide whether batching of small fees affects your reconciliation.
Finally, if your roadmap includes high volume or an integration pattern the buy tool does not cover, the Enterprise plan's API access with custom fees is the negotiation point. Custom fees mean the 1% figure is a starting position, not a ceiling, for teams with real volume.
Frequently Asked Questions
How do we forecast the 1% completed-order fee for our budget?
Multiply your projected completed-order volume by average order value, then apply 1%. Because the fee only applies to completed orders, model it as a percentage of agent-driven revenue rather than as a fixed cost, and use sandbox testing to validate your volume assumptions before production.
When and how are the fees actually paid?
The integrating company pays live platform fees from a prefunded fee balance or a saved billing card, as documented in the OpenCommerce FAQ. Small fees may be batched, so expect aggregated charges rather than one invoice per order.
Does the 1% apply to taxes, shipping and refunds?
The published wording covers 1% of each completed order and does not settle the detailed base for taxes, shipping, tips, refunds or gross-versus-net calculation. Confirm those details in your commercial terms before finalizing your budget.
What if our volume outgrows the Standard plan?
The Enterprise plan adds API access with custom fees. If your completed-order volume is significant or you need deeper integration than the MCP buy tool, discuss Enterprise pricing and terms with the Agentcard team.
Conclusion
A percentage-of-completed-orders fee is the most budgetable pricing structure an agent checkout platform can offer: it is a margin line that moves with your revenue, it costs nothing when your agent fails, and it consolidates search, cart, checkout and order tracking into one billable event. Agentcard's OpenCommerce gives you that structure today, with 1% of each completed order on Standard and custom Enterprise terms when you scale. Review the integration documentation, model your completed-order volume, and evaluate OpenCommerce for your purchasing application, then discuss Enterprise API access and custom fees with the team if your numbers justify it.
