Buy
Agentcard issues virtual Visa cards and a Purchase Agent so AI agents can buy online with human approval.
Agentcard solves the two things that make teams hesitate about agent spending: cards scoped to one merchant and one amount, and a human approval step before money moves. The Vault-plus-Purchase-Agent combination means you can ship without running a browser agent at all. The Issuing plan at $5,000/mo is a real commitment, so start with Vault Free and the beta-priced Purchase Agent before you commit to your own card program.
Verified 10h ago · liveness 80/100 · cite: rightaichoice.com/tools/buy
- Agent hosting and consumer apps that store user cards and buy on their behalf
- B2B teams automating company purchases through a Slack or chat agent
- Crypto teams routing user funds into agent-issued cards via USDC on Base
- Developers who want merchant-locked, amount-locked card spend instead of full card access
- Anyone who needs a physical card for in-store purchases
- Teams whose agents buy mostly outside the 18+ integrated merchants and have no browser automation in place
- Companies that need SSO, SCIM, an SLA or a SOC 2 report — those sit on the Enterprise tiers
We scan live Reddit threads, YouTube comments, X posts, G2 reviews and other communities — and hand you an honest verdict in under a minute.
- Honest verdict, not marketing
- Real pros & cons from real users
- Attributed quotes with receipts
3 free scans · no card needed
Skip Agentcard if you need a physical card, if most of your agent's spend is at merchants outside the 18+ integrated stores and you have no browser automation, or if you need SSO, SCIM and a SOC 2 report without an Enterprise conversation.
Issuing runs $5,000/month even in a month your agents barely transact — the flat fee does not flex with volume.
The free Vault tier (up to 5,000 users) makes Agentcard cheaper than almost anything else in this category for teams validating demand, and the $0.15/request Purchase Agent is priced for occasional orders. Issuing at $5,000/month flat is expensive next to Stripe Issuing's usage-based issuing fees if your volume is low, but at high card volume the flat fee plus the 1% revenue share you keep can beat paying per card elsewhere.
In short
Buy — Agentcard issues virtual Visa cards and a Purchase Agent so AI agents can buy online with human approval. Best for Agent hosting and consumer apps that store user cards and buy on their behalf, B2B teams automating company purchases through a Slack or chat agent, Crypto teams routing user funds into agent-issued cards via USDC on Base. Free to start; paid plans from $0.15.
What's new in Buy
Checked 7 days agoAcross the latest 4 updates: 4 changelog entries.
Agentcard: shopping agent returns placed orders and refreshes expired approval links
Agent no longer rebuilds carts after approval, reissues expired approval links, and explains merchant address rejections instead of silently editing addresses.
Agentcard: wallet feed shows authorization adjustments and partial-release holds
Wallet activity now shows Spend adjusted rows when a hold drops, and partial network releases keep the remaining hold until final settlement.
Agentcard: 3D Secure window reports verification outcome and adds close button
Bank verification window now states how the check ended (complete, canceled, unread) and can be closed, ending stuck waiting screens.
Agentcard supports 12-digit card numbers for auto-approval and shared budgets
Cards issued with 12 digits by some networks can now enable auto-approval, join the shared budget, and let an app pay.
What people actually say about Buy — is it worth it?
We ran a structured research pass across product reviews, community discussions, and post-purchase forum threads to surface the patterns vendors won't publish themselves. Below: the recurring strengths, the hidden costs people mention most, and the cohort that consistently regrets adopting this tool.
62 mentions across 4 sources (Hacker News, App Store, Lemmy, Tech Press) · researched Jul 2, 2026.
Average across the 4 sources that answered — each source counts once, not each post.
- +Disposable cards protect real card details from breaches.
- +Explicit approval per transaction maintains user control.
- +Works with ChatGPT, Claude Desktop, and OpenClaw out of box.
- +CLI and MCP server enable easy developer integration.
- +Per-task card isolation prevents overcharging and misuse.
- −No community feedback available to verify real-world utility.
- −Heavy reliance on manual approval defeats full autonomy.
- −Limited merchant acceptance for one-time virtual cards.
- −Potential notification delays could stall agent workflows.
- −Pricing for Pro tier not publicly detailed yet.
Viability Score
How well maintained and how widely used is Buy? Built from what the vendor actually publishes (docs, changelog, tutorials, integrations, pricing), whether the site is live, and how much real users discuss it. How we calculate this
Last calculated: October 2026
How we score →Key Features
- Vault stores customers' existing cards and buys with an agent
- Issuing creates one-time and multi-use virtual Visa debit cards for agents
- Cards shaped to a single merchant and a single amount
- Multi-use cards with a monthly cap for subscriptions and repeat orders
- Voice: customers approve purchases by speaking, for screenless agents
- Passkey or master-password approval before any charge is paid
- Cards encrypted on the device before they're stored
- Auto-approve within limits the customer sets
- Rewards routing picks the card that earns the most points
- Tokenback pays customers in Anthropic and OpenAI tokens instead of points
- Purchase Agent places the order with one API call or the buy tool over MCP
- Shopping agent returns placed orders and refreshes expired approval links
- Wallet activity shows authorization adjustments and partial-release holds
- 3D Secure window reports verification outcome and can be closed
- 12-digit card numbers support auto-approval, shared budgets and app payments
About Buy
Agentcard is a payment layer built specifically for AI agents that need to spend money online. Consumer apps, B2B teams and crypto companies use it to give their agents a way to pay without handing over raw card credentials — card numbers stay in Agentcard's vault, so neither your application nor the model ever sees the PAN. The product breaks into four pieces. Vault stores a customer's existing card and lets an agent buy against it, including rewards routing that picks whichever card earns the most points. Issuing creates one-time or multi-use virtual Visa debit cards shaped to a single merchant and a single amount, with a monthly cap when you need subscriptions. Voice handles approval for screenless flows — the customer speaks a phrase and the charge goes through. Purchase Agent skips merchant integration entirely: one API call or the buy tool over MCP places the order across 18+ stores including Amazon, Walmart, Target, DoorDash and flights. Approval sits in front of every charge — a passkey, a master password or a spoken word — and auto-approve only fires inside limits the customer sets. Recent work has gone into reliability: the shopping agent now returns placed orders and refreshes expired approval links, merchant address rejections get explained rather than silently edited, wallet activity shows authorization adjustments and partial-release holds, and 12-digit card numbers issued by some networks can use auto-approval and shared budgets. Compared with Stripe Issuing, this is a narrower, agent-native product rather than a general card-issuing toolkit. You get fewer levers but the ones that matter for agentic checkout are already wired up.
Behind the Verdict
Where Agentcard earns its keep is scoping. A card locked to amazon.com for $23.06 is a very different risk object than a card with a credit limit, and pairing that with passkey or spoken approval covers the failure modes that scare finance teams. If your agent already runs in Kernel, Browserbase, Browser Use, Anchor or your own Playwright browser over CDP, integration is a few lines of attach code rather than a payments project. Pick it when you're building a consumer assistant or B2B agent that buys on someone's behalf and you don't want to custody card data yourself. The Vault free tier up to 5,000 users is generous enough to validate the flow before you think about contract terms. Pick it too if your merchants overlap the 18+ list. Purchase Agent at $0.15 per request (free during beta) removes the entire browser-automation stack from your critical path — an afternoon to live, per the vendor, versus weeks of merchant-by-merchant work. Pass on it if you need a physical card, or if your agents shop mostly outside those integrated stores and you have no browser agent in place. The Purchase Agent can't cover what it hasn't integrated. Watch the Enterprise line. SSO, SCIM, an SLA and the SOC 2 report all sit behind Vault Enterprise, so a company that needs those controls isn't staying on the free plan for long. Issuing's $5,000 monthly floor plus a 1% revenue share is priced for teams actually running a card program, not for a side project testing the idea. The closest alternative is Stripe Issuing — broader, more configurable, but you build the agent-safe scoping and approval UX yourself. Agentcard is the shortcut if you want that behavior out of the box. In practice the caveat I'd flag is reliability at the edges: the September 2026 changelog is a list of small
Researching Buy? Get your full AI stack in 60 seconds.
Free, no signup — tell us your goal and get tools matched to your budget & existing stack.
Real-world workflow fit
Concrete scenarios for the personas Buy actually fits — and what changes day-one when you adopt it.
You put a user's existing card into the Vault, then let your agent check out at a supported store; the user gets a passkey prompt on their phone before the charge lands.
Outcome: The card number never touches your app or the model, the user approves every charge, and disputes are handled like any other card dispute with coverage up to $250.
You embed the Purchase Agent with one API call from your Slack agent, confirm the exact cart, and let it buy from Amazon, Walmart or Staples without writing merchant integrations or running a browser.
Outcome: Orders go live in an afternoon, users approve with a passkey, a changed price comes back to you before purchase, and every order reports its order number, delivery window and shipments.
You hold program funds as USDC on Base, issue cards to users in nearly any country, and let their agents spend while you take a 1% revenue share plus markup you set from the dashboard.
Outcome: Cards are funded from crypto, settlements are instant, and the revenue share plus markup turns the payment layer into a line of business rather than a cost centre.
Use Cases
- Store a customer's card in the Vault and let an agent buy on their behalf without the app ever seeing the PAN.
- Issue a single-use virtual card locked to one merchant and one amount for a one-off agent purchase.
- Give a subscription-running agent a multi-use card with a monthly cap instead of full card access.
- Embed the Purchase Agent in your own agent with one API call and order from Amazon, Walmart or DoorDash.
- Let an iMessage or WhatsApp agent built on Linq or Blooio complete a payment inside the thread.
- Attach Agentcard to a Kernel, Browserbase or Browser Use session so your browser agent can check out.
- Earn interchange: take a 1% revenue share on settled volume and set your own markup from the dashboard.
- Hold program funds as USDC on Base for a crypto-native agent product.
Models Under the Hood
as of 2026-10-18
Limitations
- Issuing starts at $5,000/month with a 1% revenue share, and Enterprise tiers for Vault and Issuing (SSO/SCIM, named support contact, written SLA, SOC 2 report and pen-test summary) are sales-negotiated rather than self-serve.
- Purchase Agent coverage is a defined set of online stores (Amazon, Walmart, Target, Best Buy, Home Depot, DoorDash and others); other merchants require running your own browser agent against an issued card.
- Vault is free only up to 5,000 users.
as of 2026-10-01
Verification history
We have re-verified Buy 9 times since . Each pass re-reads the vendor's own pages and re-checks every listed field against that evidence; passes where nothing had changed are marked as such.
- — re-verified summary, description, our verdict, our analysis, pricing model, pricing tiers, features, integrations, who it suits, who should skip it
- — re-verified summary, description, our verdict, our analysis, pricing model, pricing tiers, features, integrations, who it suits, who should skip it
- — re-verified summary, description, our verdict, our analysis, pricing model, pricing tiers, features, integrations, who it suits, who should skip it
- — re-verified summary, description, our verdict, our analysis, pricing model, pricing tiers, features, integrations, who it suits, who should skip it
- — re-verified summary, description, our verdict, our analysis, pricing model, pricing tiers, features, integrations, who it suits, who should skip it
- — re-verified summary, description, our verdict, our analysis, pricing model, pricing tiers, features, integrations, who it suits, who should skip it
Showing the 6 most recent of 9 verification passes.
Free to cite with attribution — this page re-verifies continuously.
12-month cost
Project the real annual outlay, including the implied monthly cost when only an annual tier is published.
Vendor list price only. Add-on usage, seat overages, and contract minimums are surfaced under Hidden costs & gotchas.
Plans compared
For each published Buy tier: who it actually fits, and what it adds vs. the previous tier. Cross-reference the cost calculator above for projected annual outlay.
Vault Free
$0/mo
Ideal for
Consumer or B2B apps with fewer than 5,000 users that want to store customers' cards and let an agent buy without touching the card number.
What this tier adds
Free entry point: card storage from any country, passkey approval, auto-approve limits, rewards routing, white-labelling and an insured-against-mistakes guarantee.
Vault Enterprise
Custom
Ideal for
Companies past the 5,000-user cap that need SSO, SCIM, a written SLA and a SOC 2 security review before storing cards at scale.
What this tier adds
Adds unlimited users, ownership of the Vault and every card in it, a named contact with a shared Slack channel, SSO/SCIM, custom approval rules and a custom contract.
Issuing
$5,000/mo
Ideal for
Agent products with real transaction volume that want their own card program, a revenue share and markup instead of paying per card.
What this tier adds
$5,000/month flat with $0 per card issued or connected, a 1% revenue share on every transaction, optional markup, Tokenback rewards and funds held as USDC on Base.
Issuing Enterprise
Custom
Ideal for
High-volume issuers that need volume-based rates, SSO/SCIM, a named contact and a security-reviewed custom contract.
What this tier adds
Adds volume pricing that comes down with card volume on top of every Issuing feature, plus dedicated support, SLA, SSO/SCIM, custom limits and a security review.
Purchase Agent
$0.15/request
Ideal for
Developers who want agent purchases across 18+ merchants without building merchant integrations or running their own browser.
What this tier adds
Starting tier for buying: $0.15 per request (free in beta), one API call or the buy tool over MCP, passkey approval from the user's Vault card and order tracking.
Where the pricing makes sense
The company stage and team size where Buy's pricing actually pencils out — and where peers do it cheaper.
The free Vault tier (up to 5,000 users) makes Agentcard cheaper than almost anything else in this category for teams validating demand, and the $0.15/request Purchase Agent is priced for occasional orders. Issuing at $5,000/month flat is expensive next to Stripe Issuing's usage-based issuing fees if your volume is low, but at high card volume the flat fee plus the 1% revenue share you keep can beat paying per card elsewhere.
Setup time & first value
How long it actually takes to get something useful out of Buy — broken out by persona, not the marketing-page minute.
Vault: minutes — store a card and auto-approve limits are set in the dashboard. Purchase Agent: live in an afternoon, one API call or the buy tool over MCP, with no merchant integrations and no browser to run. Browser integration: the Kernel, Browserbase, Browser Use and CDP snippets are copy-paste, so a working checkout is typically an afternoon. Issuing: production in under a week with no sales
Switching to or from Buy
How to bring data in from common predecessors and how to get it back out — written for the switcher, not the buyer.
- →From Stripe Issuing: move card creation to Agentcard's Issuing API and keep the merchant-locked, single-amount card model for agent spend.
- →From a shared company card in an agent's environment: store it in the Vault instead and gate each charge behind passkey approval.
- →From a hand-rolled Playwright checkout: attach Agentcard over CDP and let it hold the payment at the processor while the human approves.
- →From manual order placement: route the request through the Purchase Agent and confirm the cart before it buys.
- →From a points-only rewards program: switch to Tokenback and pay customers in Anthropic or OpenAI tokens.
- ↗To Stripe Issuing: rebuild card creation and controls on a general issuing toolkit if you need payment rails beyond agent purchases.
- ↗To a raw browser-automation stack with no card-issuing layer: keep your Playwright code and handle card storage and approvals yourself.
- ↗To a messaging-native payments provider: if your product is entirely inside iMessage or WhatsApp, drop the card layer and let the platform handle the payment.
- ↗To manual procurement: remove the agent from the payment path and approve purchases by hand if the volume doesn't justify the program fee.
Integrations
Resources & Guides
Tutorials & Learning
YouTube returned 6 videos for “Buy”, and we withheld 6: 6 could not be judged, because “Buy” is a single word that other videos use for other things. We are showing none, because we could not prove any of them are about Buy.
Official links
Featured Head-to-Head Comparisons
Buy vs Bitsgap
Buy and Bitsgap serve entirely different domains. If you need to let AI agents spend money safely with disposable virtual cards and per-transaction approval, Buy is your only practical option. If you want automated crypto trading bots across multiple exchanges with backtesting and demo mode, Bitsgap is the clear choice. They are not competitors but tools for distinct use cases.
Buy vs Truleo
Buy and Truleo serve entirely different markets: Buy (Agentcard) is a payment infrastructure for developers building autonomous AI agents, while Truleo is an intelligence platform for law enforcement. There is no direct competition. Choose Buy if you need to let AI agents make purchases safely; choose Truleo if you need to unify police data and automate lead generation. Your decision depends solely on which job you need done.
Buy vs Presto Voice
Buy and Presto Voice are not direct competitors; Buy is a payment infrastructure for AI agents, while Presto Voice is a drive-thru voice AI solution for QSR chains. Your choice depends on whether you need to let AI agents spend money autonomously (Buy) or automate drive-thru ordering to boost revenue (Presto Voice). For developers building agentic workflows, Buy is the clear pick; for restaurant chains wanting to reduce labor costs and increase upsells, Presto Voice is the established leader.
Popular in Agent Memory & Runtimes
Frequently Asked Questions
Used Buy? Help shape our editorial sentiment research.