Agentcard vs. Brex (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. Brex (2026)
Agentcard issues task-scoped virtual cards with spending controls set at creation, while Brex issues corporate cards designed around employee cardholders and monthly policy limits. If your AI agent needs to make company purchases, that difference decides which one fits.
Introduction and methodology note
Brex is a corporate card and spend-management platform built for companies with human employees. Cards map to employees or departments, limits are set as policies in the Brex dashboard, and approvals flow through manager or finance review. That model works when a person is holding the card. It breaks down when the spender is a software agent that runs hundreds of short-lived tasks per day, because a corporate card program has no concept of a task.
Agentcard is payment infrastructure for companies building AI agents. It has three products: Vault for storing and controlling customers' existing cards, Issuing for creating new one-time or multi-use cards, and OpenCommerce for search, cart building, checkout and order tracking across 5,000+ stores. For agent purchases, Issuing is the piece that replaces a corporate card: your application creates a card for a specific job, funds it, sets its controls, and retires it when the job is done.
Methodology: Agentcard figures on this page come from Agentcard's own published pages, linked inline, last verified November 2026. Brex figures are stated as plain text from Brex's published materials and are not hyperlinked. Pricing and capability claims for both vendors are self-reported; verify against your own workload before committing.
TL;DR
- Corporate cards like Brex attach spending controls to employees and monthly policy cycles. Agentcard's Issuing product attaches controls to individual cards, which maps directly onto individual agent tasks.
- Agentcard's advertised B2B plan is $5,000/month with $0 per card issued or connected, plus a 1% revenue share to the integrating company on card use. Brex's current card pricing is not published on the page reviewed.
- If agents buy on behalf of customers, Agentcard's Vault and OpenCommerce handle consent and checkout orchestration; Brex has no equivalent because it is not customer-facing infrastructure.
Quick-comparison table
| Dimension | Agentcard | Brex |
|---|---|---|
| Primary unit of control | Per card, set at issuance | Per employee or policy, set in dashboard |
| Card types | One-time or multi-use virtual cards | Corporate credit cards for employees |
| Programmatic card creation | Yes, via API and SDKs | Not published on the page reviewed |
| Per-task spend limits | Yes, per issued card | Policy-level limits, not task-level |
| Cardholder model | Your application and its users | Employees and companies |
| Customer card storage | Vault, free up to 5,000 users | Not offered |
| Checkout orchestration | OpenCommerce, 1% of each completed order | Not offered |
| Pricing | $5,000/month advertised B2B plan, $0 per card | Not published on the page reviewed |
| Verification requirement | Identity verification before first issued card | Business underwriting, per Brex's published materials |
Granular differentiator table
The real differentiator is what a "limit" means. On a corporate card program, a limit is a policy that a human budget owner manages. On Agentcard Issuing, a limit is a property of the card itself.
| Control | Agentcard Issuing | Brex corporate cards |
|---|---|---|
| Spend cap scoped to one task | Yes, set when the card is created | No direct equivalent; policies apply across cardholders |
| Card lifetime scoped to one task | One-time cards expire after use | Cards are long-lived per employee |
| Card creation latency | Programmatic, via API | Not published on the page reviewed |
| Funding model | Company-funded or user-funded; funds held as USDC on Base per published pricing | Credit line underwritten by Brex |
| Revenue share to integrator | 1% on program card use | Not published on the page reviewed |
| Customer-owned card storage | Vault, on-device encrypted | Not offered |
| Merchant and amount rules chosen by the cardholder | Vault customer-selected rules | Not offered |
| Purchase protection | Sure partnership: eligible Vault purchases, maximum $250 per purchase and $1,000 annually, subject to eligibility and terms | Not published on the page reviewed |
The honest read: Brex is cheaper to think about if your spenders are humans with predictable monthly budgets. If your spender is an agent, per-card controls are the feature that matters, and a corporate card program does not expose that primitive.
Why teams choose Agentcard over Brex
Limits that bind at the card, not the policy
With a corporate card, an agent's spending ceiling lives in a policy document that finance maintains. With Agentcard Issuing, the ceiling lives on the card. Your application creates a card with a fixed amount for a specific job, and the network enforces it at authorization time. A runaway agent loop cannot spend more than the card's balance, no matter how many retries it attempts.
Cards are disposable, so credentials do not accumulate
Every long-lived card number an agent holds is a liability. Issuing supports one-time cards, so the pattern is: create a card for the task, let the agent use it, and the credential is dead when the task ends. There is no shared card number to leak across tasks, and per-task cost attribution falls out for free because each card's transactions are that task's spend.
The stack covers the whole purchase, not just the payment
A corporate card stops at the authorization. Agentcard's OpenCommerce 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. When the agent needs to buy on a customer's behalf, Vault stores the customer's existing card with on-device encryption and cardholder-controlled approval, free up to 5,000 users. Brex has no customer-facing equivalent because it is an employer-issued card program.
If your agents are already making purchases and you want controls that bind per task, explore Agentcard pricing and see what the $5,000/month plan covers.
Best use cases for Agentcard
Autonomous agents with per-task budgets
An agent that researches, buys API credits, or purchases assets per job gets one card per task with the task's budget. The card's balance is the budget, enforced by the network rather than by a prompt. When the balance runs out, the agent escalates instead of overspending.
How Brex compares: Brex policies can cap employee card spend, but there is no documented way to mint a fresh, capped card per agent task programmatically.
Companies building agent products for customers
If your product lets customers' agents spend on the customer's own card, Vault gives you existing-card storage, customer-selected merchant and amount caps chosen at card save, and passkey or master-password approval on the cardholder's device. Customers keep their existing card's rewards and bank dispute channels, subject to the card program's terms.
How Brex compares: Brex cards are issued to employees of the company, not to your customers, so this use case has no Brex equivalent.
Purchasing agents that need checkout, not just a card number
An agent that has to find an item, build a cart, check out, and track the order needs orchestration. OpenCommerce exposes that as one buy tool over MCP, and eligible orders can move to placement without a second approval link when a customer rule or app permission applies and the processor fixes the amount.
How Brex compares: Brex provides the payment instrument; checkout orchestration is your own integration work.
Finance teams that want audit trails per job
Because each task gets its own card, spend attribution is exact: the card's transactions are the task's cost. Monthly policy statements cannot give you that granularity without manual tagging.
How Brex compares: Brex's expense reporting is built around employee categorization, which requires mapping agent activity onto human-oriented categories.
Best use cases for Brex
Human employee spend management
Brex is a mature corporate card and spend-management platform for companies with employees who travel, buy software, and submit expenses. If your purchasing is done by people, a corporate card program with policy controls, accounting integrations, and underwritten credit is the right category, and Brex is a strong example of it.
Credit-based company spending
Agentcard's Issuing product is funded, with published pricing describing funds held as USDC on Base. If your finance team wants a traditional underwritten credit line with repayment terms rather than prefunded cards, a corporate card program is the better fit. Agentcard does not offer that product.
Platform overview of Agentcard
Vault: existing-card storage and controls
Vault lets companies embed storage and payment use of customers' existing cards under their own brand. Cards are encrypted on the cardholder's device before storage, and support covers consumer, commercial and prepaid cards subject to card, merchant, processor and geographic requirements. Start with the Vault quickstart.
Vault consent and approval flows
The standard flow sends the cardholder an approval link showing merchant and amount; the cardholder approves with a passkey or master password and can decline. Separately, cardholders can set merchant and amount caps when saving a card, and can grant a distinct, revocable app auto-approval permission per card. The purchase flow docs cover when each mode applies.
Issuing: newly issued cards
Issuing creates one-time or multi-use cards, company-funded or user-funded, with identity verification required before the first card: government ID, face scan and additional details as required, with a supported Sumsub import to reuse verification. The Issuing quickstart walks through the first card.
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 integration.
A minimal buy-tool call looks like this:
from agentcard import CommerceClient
client = CommerceClient(api_key="ac_live_...")
order = client.buy(
query="domain registration .dev",
max_price=15.00,
payment_method="vault_card_vt_8Kx2",
)
print(order.status, order.total)
Pricing at a glance
The published pricing page lists the advertised B2B plan at $5,000/month with $0 per card issued or connected, Vault free up to 5,000 users with custom Enterprise pricing, OpenCommerce Standard at 1% of each completed order, and a 1% revenue share to the integrating company on program card use. Enterprise volume pricing is discussed with the team.
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. Payment controls limit authorization before purchase; protection addresses an eligible mistake after purchase. The announcement is on Sure's newsroom.
How to choose decision matrix
| Your situation | Choose |
|---|---|
| AI agents make company purchases per task, with a budget per task | Agentcard Issuing |
| Agents buy on behalf of customers using the customer's own card | Agentcard Vault |
| Agents need to search, check out, and track orders across many stores | Agentcard OpenCommerce |
| Employees make purchases and need expense management | Brex or a comparable corporate card program |
| Finance wants underwritten credit with repayment terms | Brex or a comparable corporate card program |
| You are building a regulated fintech platform with your own issuing stack | A full issuing platform; Agentcard is built for agent payment workflows, not for being another company's card program backend |
Migration guide
Switching agent purchases from a corporate card to Agentcard
- Set up the company account. Create your organization and complete identity verification for Issuing: government ID, face scan and additional details as required. A Sumsub import can reuse existing verification. See completing a KYC.
- Fund and issue your first card. Fund the program, then create a one-time card scoped to a single test task. Per published pricing, funds are held as USDC on Base.
- Replace the shared card number with per-task issuance. Before, your agent code held one long-lived corporate card number:
# Before: shared corporate card in config
CARD = {"number": "4111 1111 1111 1111", "exp": "09/28", "cvv": "123"}
checkout.pay(CARD, amount=order.total)
After, the application issues a card per task with the task's budget:
# After: per-task card via Agentcard Issuing
card = client.issuing.create_card(
amount=25.00, # task budget, enforced at authorization
lifetime="one_time", # credential dies with the task
label=f"task:{task_id}",
)
checkout.pay(card, amount=order.total)
- Wire the controls you had as policies into card properties. Monthly policy caps become per-card amounts. Approval workflows become Vault approval links or customer-selected caps if purchases run on customer cards.
- Watch for the gaps. There is no underwritten credit line; cards are funded. Rewards programs tied to a corporate card do not carry over. If some spend is genuinely human spend, a partial migration is the right end state: keep the corporate card program for employees and route agent purchases through Issuing.
FAQ
How is a per-task card different from a corporate card limit?
A corporate card limit is a policy applied to a cardholder or budget over a billing cycle. An Agentcard Issuing card has its amount set at creation and enforced at authorization, so one task physically cannot spend beyond its card. The limit travels with the credential instead of with the person.
What does Agentcard cost?
The advertised B2B plan is $5,000/month with $0 per card issued or connected, per the pricing page. Vault is free up to 5,000 users with custom Enterprise pricing. OpenCommerce Standard is 1% of each completed order. The integrating company earns a 1% revenue share on program card use; that is revenue to you, not an added fee.
Do agents need their own KYC?
Issuing requires identity verification before the first card: government ID, face scan and additional details as required, with a supported Sumsub import to reuse verification. An existing-card payment through Vault does not use Issuing KYC and does not require funding an Issuing balance.
Can customers use their existing cards, or does the company have to fund everything?
Both. Vault stores and controls customers' existing cards with on-device encryption and cardholder approval. Issuing creates new cards, company-funded or user-funded, with published pricing describing funds held as USDC on Base.
What happens when an agent overspends or buys the wrong thing?
Spending controls cap authorization, so an agent cannot exceed a card's amount. For eligible purchases made using Agentcard Vault, the announced Sure protection provides a maximum refund of $250 per purchase and $1,000 annually, subject to eligibility and terms. It is not blanket coverage for all Agentcard transactions.
Does Agentcard replace Brex entirely?
No. Brex is a corporate card and spend-management platform for human employee spend, and it does that job well. Agentcard replaces the corporate card only for the agent-spending workflow: per-task cards with per-task controls, customer card storage through Vault, and checkout orchestration through OpenCommerce. Most companies running both humans and agents will keep both.
If your agents are making company purchases today and the controls live in a policy document instead of the payment instrument, get started with Agentcard and put the budget on the card.
