Agentcard funding, valuation and investors

Product & use cases

Illustrative developer/end-user journey based on the official product docs: (1) a commerce app integrates Agentcard Vault or the opencommerce/MCP shopping tool; (2) customer adds their existing payment card once, encrypted on their device, without exposing the full number to the AI agent; (3) an agent searches a supported store and builds a cart; (4) customer approves with passkey or permitted auto-approval rules; (5) payment proceeds on ordinary card rails and the app tracks the purchase; (6) a mistaken payment can follow the card issuer's dispute process, subject to terms. Separate Issuing creates new single/multi-use cards, requires identity verification and maintains USDC-denominated balances. Voice approval remains early access. Verified list prices as at 2026-11-14: Vault Free through 5,000 users, Enterprise custom; Issuing $5,000/month with 1% revenue share; opencommerce Standard 1% of each completed order, enterprise quote-based. Example: $100 in completed orders at a 1% opencommerce platform fee implies $1 platform fee before merchant, payment or other costs. The example is illustrative and not verified realized revenue.

• Consumer personal-shopping agent stores a user's card and requests controlled purchase authorization.
• Company Slack procurement agent obtains approved supplies from merchants using corporate card access.
• Crypto-funded agent needs separate issued cards funded from a balance rather than users' existing payment cards.

Key facts

• $8M seed announced November 12, 2026, from Peak XV, Fin Capital and Y Combinator; investor lead, valuation and legal close date undisclosed.
• Vault Free allows up to 5,000 stored-card users; Vault Enterprise is quote-based.
• Issuing is listed at $5,000/month and a 1% revenue-share arrangement; the company describes USDC balances and KYC, unlike Vault.
• opencommerce Standard advertises 1% of completed orders and a buy tool spanning 5,000+ stores; merchant count is company-reported.

Competitive landscape

Edge: Combines existing-card credential vault and transaction approvals with card issuing and broad-store purchase automation; the architecture addresses agent checkout rather than generative-model quality. No independent evidence of 5,000 integrations' transaction success rates is disclosed.

Investor and issuer sources establish the $8M round but not lead investor, valuation, ARR, transaction volume, or merchant success rates. Vault and Issuing carry different KYC/dispute/residency implications: no KYC for an existing-card Vault path is not a promise that all users of Issuing avoid identity checks. Public pricing says 1% 'revenue share' in Issuing without sufficient detail to infer net margin. Selected client examples such as Orchid, Almanac and Laso are vendor-supplied, not independently measured results. Buyer due diligence should test failed transactions, refunds, agent authorization and card liability.

• Stripe Issuing adjacent

  Mature programmable card issuance; agent-browser checkout and consumer stored-card flows require additional components.

• Marqeta adjacent

  Card issuing and transaction controls, with a different issuer/program onboarding model.

• Sponge direct

  YC agent wallet and merchant payment gateway; funding models and payment rails differ.

• Merchant-specific shopping APIs alternative

  Direct integrations can avoid intermediary purchasing fees but require merchant-by-merchant checkout logic.

Market / IPO context