agentcard.com

Command Palette

Search for a command to run...

Agent Payment Platforms With Enterprise API Access and Custom Fees

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 Platforms With Enterprise API Access and Custom Fees

When an AI agent purchasing platform has to run at serious volume, the self-serve plan stops being the question. The question is whether the vendor offers an enterprise tier with direct API access and custom fees that reflect your actual volume instead of a flat rate that punishes growth. Agentcard answers that with its OpenCommerce Enterprise plan, which adds API access with custom fees on top of the Standard plan's pay-per-order model, alongside custom Enterprise pricing for Vault and volume terms discussed with the team for Issuing. This guide walks through what to look for in an enterprise plan, which criteria matter most, and how to match a plan to your volume.

Introduction

Agent purchasing platforms, the payment infrastructure behind AI agents that search, buy, and track orders, tend to publish one of two pricing stories. The first is a flat monthly plan with a published rate, which is easy to evaluate but rarely fits a platform processing thousands of purchases a day. The second is an enterprise tier where fees are negotiated, and the differentiator is not the discount but what the tier unlocks: direct API access, higher throughput, and commercial terms built around your integration rather than a generic meter.

Agentcard is built for companies shipping AI products, and its pricing reflects that split. The OpenCommerce buy tool, catalogue search, cart building, checkout, and order tracking across 5,000+ stores, is available over MCP on the Standard plan at 1% of each completed order. The Enterprise plan adds API access with custom fees, which is exactly the combination high-volume teams need: programmatic purchasing plus commercial terms that scale. Vault, which stores and uses customers' existing cards under your brand, is free up to 5,000 users with custom Enterprise pricing beyond that. Issuing, for newly issued one-time or multi-use cards, is advertised at $5,000/month with $0 per card, and enterprise volume pricing is discussed with the team.

The rest of this guide is a decision framework: what an enterprise plan should include, how to evaluate it, and how to choose between the paths.

Key Takeaways

  • An enterprise plan for agent purchasing should bundle three things: direct API access, custom fees tied to your volume, and the controls your compliance team will ask about.
  • Agentcard's OpenCommerce Enterprise plan adds API access with custom fees on top of Standard's 1% per completed order, the clearest published example of this model.
  • Vault is free up to 5,000 users with custom Enterprise pricing beyond that, and supports white-label embedding under your own brand.
  • Issuing is $5,000/month and $0 per card issued or connected, with enterprise volume pricing discussed with the team and a 1% revenue share earned by the integrating company when program cards are used.
  • Choose by requirement: Vault for existing cards and payment controls, Issuing for newly issued cards, OpenCommerce for search, cart, checkout, and order tracking.

Decision criteria

API access at the enterprise tier. The single most important question is whether the enterprise plan gives you programmatic access or just a bigger version of the dashboard. On OpenCommerce, the Standard plan exposes the buy tool over MCP; Enterprise adds API access with custom fees. If your purchasing volume is high enough that per-order rates or MCP-only access become a bottleneck, an enterprise tier that opens the API is the unlock. Review the Commerce SDK quickstart to see what the integration surface looks like before you talk pricing.

Custom fees that track real volume. A flat rate is a ceiling disguised as simplicity. Custom fees let the vendor price your actual completed-order volume, card count, or user count instead of averaging across their book. Agentcard publishes this pattern in all three products: OpenCommerce Enterprise has custom fees, Vault Enterprise has custom pricing after the free 5,000-user allowance, and Issuing's enterprise volume pricing is discussed with the team. When you evaluate any platform, ask what the fee base is, completed orders, connected cards, or users, and whether sandbox and failed purchases are billed. On OpenCommerce, sandbox purchases are not billed, which matters when you are testing at scale.

Consent and approval architecture. High volume does not remove the authorization problem; it multiplies it. Agentcard separates initiation from authorization: the cardholder stores their card once in Vault, encrypted on their device, and approves purchases with a passkey or master password, or falls within merchant and amount caps they chose when saving the card. A separate, revocable app auto-approval permission exists as a distinct mode, documented in the app auto-approval guide. Every approval lands in a timestamped log. If a vendor cannot show you who authorized what, and when, enterprise volume becomes an audit liability.

Verification and funding requirements. Enterprise does not mean exempt. Issuing requires identity verification before the first card, with a supported Sumsub import to reuse existing verification, and funds are held as USDC on Base per published pricing. Vault's existing-card payments do not use Issuing KYC and do not require funding an Issuing balance. Know which path your volume actually needs before you negotiate.

Revenue economics. If you are embedding payments in your own product, the enterprise conversation should include what you earn, not just what you pay. On Agentcard Issuing, the integrating company earns a 1% revenue share when program cards are used, revenue to you, not an added fee, and separate from any optional transaction markup.

How to choose

If your agents need to purchase across many merchants at high volume: start with OpenCommerce. Standard covers the buy tool over MCP at 1% of each completed order; when volume justifies it, the Enterprise plan adds API access with custom fees. This is the direct answer for teams whose purchasing agents have outgrown per-order self-serve rates.

If your users pay with cards they already have: Vault is the fit. It is free up to 5,000 users, fully white-labeled, and custom Enterprise pricing applies beyond that. Cardholders keep their existing rewards and bank dispute channels, subject to the card program's terms. Choose this when the money is the cardholder's, not the platform's.

If you need newly issued cards you fund yourself: add Issuing. One-time cards close after a single approved charge, which contains the blast radius of any misbehaving agent session. The advertised plan is $5,000/month with $0 per card, and enterprise volume pricing is discussed with the team, so if your card count is in the tens of thousands, that conversation is where the custom terms live.

If you need several of these at once: they run side by side. A purchasing platform can use Vault for cardholder-funded spend, Issuing for company-funded agent tasks, and OpenCommerce Enterprise for the checkout layer, without rebuilding the payment approach between them.

A practical sequencing note: negotiate enterprise terms only after you have validated the integration against the Agentcard docs. Enterprise pricing is easier to discuss when you can show the vendor your real integration and volume profile.

Frequently Asked Questions

Which Agentcard plan includes API access with custom fees?

The OpenCommerce Enterprise plan. Standard exposes the buy tool over MCP at 1% of each completed order; Enterprise adds API access with custom fees. See Agentcard pricing for the published structure.

Is there a free path before enterprise pricing?

Yes. Vault is free up to 5,000 users, with custom Enterprise pricing beyond that. OpenCommerce sandbox purchases are not billed, so you can validate the integration before committing to volume terms.

What does high-volume card issuing cost?

The advertised B2B plan is $5,000/month with $0 per card issued or connected, and enterprise volume pricing is discussed with the team. The integrating company earns a 1% revenue share when program cards are used.

Do enterprise plans remove verification requirements?

No. Issuing requires identity verification before the first card, with a supported Sumsub import to reuse existing verification. Vault's existing-card payments do not use Issuing KYC, but your company keeps its own integration and security responsibilities either way.

Conclusion

For agent purchasing at enterprise volume, the plan worth having is the one that pairs direct API access with custom fees, not a flat rate that treats every customer the same. Agentcard's OpenCommerce Enterprise plan is the clearest published example: API access with custom fees on top of a Standard plan that already handles search, cart building, checkout, and order tracking across 5,000+ stores. Vault's custom Enterprise pricing and Issuing's volume terms complete the picture for existing-card and newly issued-card requirements. Review the Agentcard pricing page, validate the integration against the docs, and bring your real volume profile to the enterprise conversation.

Related Articles