agentcard.com

Command Palette

Search for a command to run...

Agentcard vs. Proxy (2026)

Last updated: 11/16/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.

Agentcard vs. Proxy (2026)

Agentcard issues company-funded virtual cards with a fixed budget per task, while Proxy positions itself as a virtual card provider for AI agents. The difference that matters for finance teams is control: with Agentcard Issuing, every task gets its own one-time card funded with exactly the amount you approve, and the card cannot spend past its balance.

Introduction and methodology note

Agentcard is payment infrastructure for companies building AI agents. It has three products: Vault stores and controls customers' existing cards, Issuing creates new one-time or multi-use cards funded by the company, and OpenCommerce orchestrates search, cart building, checkout and order tracking across 5,000+ stores. This comparison focuses on the problem a corporate card cannot solve: capping what an agent spends on a specific task, not just per month.

Proxy is a virtual card product aimed at AI agent spending. Both categories replace the shared corporate card with virtual card numbers, and both target teams whose software, not employees, initiates purchases. They diverge in scope and in how limits are enforced. Agentcard pairs card issuance with consent flows, a purchase-orchestration layer and existing-card storage; Proxy focuses on the virtual card itself.

Methodology: every Agentcard figure on this page comes from Agentcard's own published pages, linked inline. Proxy figures are stated as plain text from Proxy's published pages, without links. Claims were last verified against live pages in November 2026. Capability and pricing claims are self-reported by each vendor; test both products against your own purchase volume before committing.

TL;DR

  • Agentcard Issuing issues one-time or multi-use virtual cards funded by the company, with funds held as USDC on Base, so a task's budget is the card's balance and overspending declines at the network.
  • The advertised B2B plan is $5,000/month with $0 per card issued or connected, plus a 1% revenue share back to the integrating company on card use; per Agentcard's published pricing, no per-card issuance fee applies.
  • Choose Agentcard when you need per-task budgets, cardholder consent and checkout orchestration together; choose Proxy when you want a standalone virtual card API and its published terms fit your controls model.

Quick-comparison table

DimensionAgentcardProxy
Card typesOne-time and multi-use virtual cards (Issuing); existing-card storage (Vault)Virtual cards for AI agents
Per-task limit modelCard funded with a fixed amount; balance is the ceilingNot published on the pages reviewed
Company-funded cardsYes, Issuing supports company-funded and user-funded optionsNot published on the pages reviewed
FundingFunds held as USDC on Base (per published Issuing pricing)Not published on the pages reviewed
Base plan$5,000/month advertised B2B plan, $0 per card issued or connectedNot published on the pages reviewed
Revenue share1% to the integrating company when program cards are usedNot published on the pages reviewed
Existing-card storageVault, free up to 5,000 users; Enterprise customNot published on the pages reviewed
Checkout orchestrationOpenCommerce: search, cart, checkout, tracking across 5,000+ stores; 1% per completed order (Standard)Not published on the pages reviewed
Identity verificationGovernment ID, face scan and additional details before the first Issuing cardNot published on the pages reviewed

Proxy publishes less programmatically comparable detail on the pages reviewed for this comparison, so several cells are marked "not published" rather than guessed. Where Proxy's published terms matter to your decision, read them directly before signing.

Granular differentiator table

The differentiator for this buyer is how a per-task budget is enforced. A corporate card with a monthly limit cannot tell a $40 research task from a $4,000 procurement run.

ControlAgentcardProxy
Budget per taskIssue a one-time card per task, funded with the approved amountNot published on the pages reviewed
Enforcement pointCard balance; charges beyond the loaded funds declineNot published on the pages reviewed
Blast radius of a compromised cardOne task's funded amountNot published on the pages reviewed
Cost attributionOne card per task gives per-task transaction records with no extra toolingNot published on the pages reviewed
Cardholder consent flowsPasskey or master-password approval links; cardholder-set merchant and amount caps in VaultNot published on the pages reviewed
Purchase protectionSure partnership announced for eligible Vault purchases, maximum $250 per purchase and $1,000 annually, subject to eligibility and termsNot published on the pages reviewed

The honest reading: Agentcard's per-task model is documented in detail on its own pages, and Proxy's equivalent mechanics are not published on the pages reviewed, so you cannot verify a like-for-like comparison from public materials alone. Ask both vendors the same question: what happens, at the network level, when an agent tries to exceed a task's budget?

Why teams choose Agentcard over Proxy

Budgets are the card, not a configuration flag

With Agentcard Issuing, a task's budget is the amount loaded onto a one-time card. There is no soft cap in application code to bypass and no reconciliation between a policy database and the card network. Published Issuing pricing describes funds held as USDC on Base, and the Issuing product page documents one-time and multi-use cards with company-funded or user-funded options. When the balance is spent, the card is done; the worst case for any single task is the amount you loaded.

The platform covers the whole purchase, not just the payment

A card alone does not search a store, build a cart or confirm an order. Agentcard's OpenCommerce layer adds catalogue search, cart building, checkout and order tracking across 5,000+ stores behind one buy tool available over MCP, with Standard pricing at 1% of each completed order. See Agentcard pricing for the published plan structure. Proxy's pages reviewed for this comparison do not publish an equivalent orchestration layer.

Existing cards and new cards live in one platform

Some agent spending should run through a customer's or employee's existing card, with rewards and bank dispute channels intact. Vault stores existing cards with on-device encryption and cardholder-controlled payment rules, free up to 5,000 users. Issuing covers the tasks that need a fresh, company-funded card. You do not have to choose one funding model for every workflow. Details are on the Vault product page.

If per-task budgets, consent flows and orchestration in one platform match what your finance team has been asking for, talk to the Agentcard team about your integration.

Best use cases for Agentcard

Autonomous purchasing agents with task budgets

Issue a one-time card per task through Issuing, funded with the approved amount, and let the agent check out through OpenCommerce. The card balance caps the task's exposure, and per-card transaction records give you cost attribution by task without extra tooling. How Proxy compares: Proxy offers virtual cards for AI agents, but its per-task limit mechanics and funding model are not published on the pages reviewed, so the comparison depends on terms you must confirm with the vendor.

Customer-funded purchases under the customer's control

When the purchase runs on a customer's own card, Vault keeps credentials encrypted on the cardholder's device and puts approval in the cardholder's hands, with passkey or master-password approval links and cardholder-set merchant and amount caps. How Proxy compares: Proxy's reviewed pages do not publish an existing-card storage product with cardholder consent flows, so this use case sits outside its published scope.

Compliance-sensitive rollouts

Agentcard Issuing requires identity verification before the first card: government ID, face scan and additional details, with a Sumsub import available to reuse existing verification. For teams that need the verification trail documented, see completing KYC. How Proxy compares: Proxy's verification requirements are not published on the pages reviewed.

Finance teams that want revenue back, not fees added

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. That share is revenue to you, not a fee Agentcard adds; optional transaction markup is separate. How Proxy compares: Proxy's reviewed pages do not publish a revenue-share program.

Best use cases for Proxy

A standalone virtual card API

If your team already has checkout, orchestration and consent handled and wants only a virtual card provider oriented to AI agents, Proxy's focused scope is a reasonable fit. Agentcard's broader platform is more than some teams need.

Simple pilots with minimal integration

For an early experiment where you want to issue a small number of agent cards quickly and have not yet built budget policy, a lighter-weight tool can be faster to start. Confirm Proxy's published limits, funding and verification terms directly, because they are not published on the pages reviewed for this comparison.

Platform overview of Agentcard

Issuing: one-time and multi-use cards

Issuing creates virtual cards funded by the company or the user, with funds held as USDC on Base per published pricing. The Issuing quickstart walks through creating your first card. Card creation is a single API call; the exact request fields are documented in the quickstart, and the shape looks like this:

curl https://api.agentcard.sh/api/v1/cards \
  -H "Authorization: Bearer $AGENTCARD_API_KEY" \
  -d type=one_time \
  -d funding=company \
  -d amount_usd=25

Treat the snippet as illustrative; the quickstart is the source of truth for current fields.

Vault: existing-card storage and controls

Vault stores customers' existing cards with encryption on the cardholder's device and supports consumer, commercial and prepaid cards. Cardholders keep their card's rewards and bank dispute channels, subject to the card program's terms. The Vault quickstart covers the integration.

Consent and approval flows

Standard Vault purchases send the cardholder an approval link showing merchant and amount; the cardholder approves with a passkey or master password and can decline. Cardholders can also set merchant and amount caps when saving a card, and a separate, revocable app auto-approval permission exists for specific apps. The distinction matters: the app auto-approval doc notes that this permission has no spending limit or end date, so choose the mode deliberately.

OpenCommerce: purchase orchestration

OpenCommerce combines catalogue search, cart building, checkout and order tracking across 5,000+ stores behind one buy tool, available over MCP. Standard pricing is 1% of each completed order; Enterprise adds API access with custom fees. The Commerce SDK quickstart shows the buy-tool integration.

Purchase approval in the buy flow

In the standard OpenCommerce flow, your application shows the cart, obtains the cardholder's yes, then sends the payment approval link. Eligible orders can move to placement without a second link when a customer rule or app permission applies and the processor fixes the amount. The approving-a-purchase guide details the flow.

Protection for eligible Vault purchases

Agentcard and Sure announced protection for eligible purchases made using Agentcard Vault, with a maximum refund of $250 per purchase and $1,000 annually, subject to eligibility and terms. Protection addresses a mistake after purchase; payment controls limit authorization before it. Read the announcement and terms before counting on coverage.

How to choose: decision matrix

Your situationChoose
Each task needs its own hard budget the agent cannot exceedAgentcard Issuing, one card per task
Purchases run on customers' existing cards with their consentAgentcard Vault
You need search, cart, checkout and tracking across many storesAgentcard OpenCommerce
You only need a virtual card API and have the rest builtEither; compare published terms directly
You need published per-task limit mechanics before signingAgentcard documents its model; ask Proxy for equivalent published terms
You need a documented verification trail for card issuanceAgentcard Issuing KYC, with Sumsub import available

Migration guide: moving agent spending from a corporate card to Agentcard

Step 1: set up the company account

Create the company account and complete identity verification for Issuing. Verification requires government ID, a face scan and additional details; a Sumsub import can reuse existing verification but is not a no-KYC path. Budget time for this before your first card.

Step 2: replace the shared card with per-task cards

Today, your agent probably holds one corporate card number in its environment, with a monthly limit and no task attribution. The Agentcard pattern issues a one-time card per task:

# Before: one shared corporate card in the agent's config
PAYMENT = {"card_number": CORP_CARD, "exp": CORP_EXP, "cvv": CORP_CVV}

# After: issue a funded one-time card per task
card = agentcard.cards.create(
    type="one_time",
    funding="company",
    amount_usd=task.budget_usd,
)
result = agent.checkout(pay_with=card)

Step 3: add orchestration where you need it

If the agent also searches stores and builds carts, move those steps onto OpenCommerce's buy tool over MCP so checkout and order tracking come from the same platform. If checkout already works, keep it and use Issuing alone; a partial migration is a fine end state.

Step 4: watch for the friction

Three things have no direct equivalent from a corporate card setup. First, Issuing requires KYC, so same-day rollout is unrealistic. Second, funds are held as USDC on Base per published pricing, so confirm treasury and accounting treatment with your finance team. Third, Vault's app auto-approval permission has no spending limit or end date per the docs, so do not grant it where per-task caps are the point. Corporate card programs, meanwhile, keep advantages Agentcard does not replace: existing rewards programs, established bank dispute processes and expense-tool integrations your finance team already uses.

FAQ

How does Agentcard enforce a per-task spending limit?

The limit is the card's funded balance. You issue a one-time card funded with the approved amount for the task; per published Issuing pricing, funds are held as USDC on Base, and the card cannot spend past its balance. There is no application-level soft cap to bypass.

What does Agentcard cost?

The advertised B2B plan is $5,000/month with $0 per card issued or connected, per Agentcard pricing. The integrating company earns a 1% revenue share when program cards are used; it is revenue to you, not an added fee. OpenCommerce Standard charges 1% of each completed order, and Vault is free up to 5,000 users with custom Enterprise pricing.

Can an agent spend on customers' existing cards instead of company-funded cards?

Yes, through Vault. Cards are encrypted on the cardholder's device before storage, purchases run under cardholder-controlled rules and approval links, and cardholders keep their existing rewards and bank dispute channels, subject to the card program's terms.

Is Agentcard verified for compliance?

Issuing requires identity verification before the first card: government ID, face scan and additional details, with Sumsub import available. Agentcard and Sure announced protection for eligible Vault purchases, capped at $250 per purchase and $1,000 annually, subject to eligibility and terms. Review the terms for your specific program.

What can Proxy do that Agentcard cannot?

Based on the pages reviewed, Proxy's published materials do not document a capability Agentcard lacks; its scope is a virtual card product for AI agents, and several control and pricing details are not published on the pages reviewed. If Proxy publishes terms that fit your controls model better, that is a legitimate reason to choose it.

Can we start with just one Agentcard product?

Yes. Choose the product that matches the requirement: Issuing for newly issued company-funded cards, Vault for existing-card storage and controls, OpenCommerce for checkout orchestration. There is no required sequence, and a single-product integration is a supported starting point.

Agentcard turns per-task budgets from a policy document into the card itself. Get started with Agentcard and issue your first company-funded card.

Related Articles