Wallet Agent — give every AI agent permission once. Not your credit card.
ChatGPT books dinner. Claude orders groceries. Copilot manages your travel. The Wallet Agent is the permission + payment layer they share — so you set rules and a card once, not per-agent.
Free for users · we make money from merchants on completed transactions.
Consumer Bundle — $9/mo
Wallet Agent + Order Agent + Find Agent (auto deal-spotter) + Intent Agent (merchants bid for you). Save $6/mo vs separately.
Discovery extension
- Chrome browser extension
- Surfaces verified AgentPKI merchants in a sidebar when you ask any AI assistant for a local business
- Cryptographically signed catalogs, real menus, current prices
- Free, no account required
Status: built; pending Chrome Web Store approval. Sideloadable for testers today.
Order Agent + Wallet Agent
- Free account · email magic-link sign-in
- Card on file, saved addresses, dietary + service preferences
- Order Agent: ask in plain English ("pizza in Raleigh, under $30") → orders from a verified merchant
- Works for restaurants, cafes, salons, HVAC, contractors, retail — anything our verified merchants offer
- Signed receipts · disputes opened in one click · merchant Fulfillment Agent auto-handles incoming
Status: live in private beta. Merchant directory fills as NC businesses onboard. Try it →
Cryptographic consent layer
- Spending limits per agent ("$50/day on food, $0 on impulse buys")
- Scoped passports — 5-minute tokens authorizing specific agent actions
- Hard-rejected at the protocol level when an agent exceeds scope
- Signed receipts + auto-prepared dispute filings
- Self-custody key option
Status: spec drafting. Unlocks once Order Agent has real volume.
Why this matters
The number of AI agents acting on behalf of people is going up fast. Today each one wants its own login, its own card on file, its own copy of your preferences. That doesn't scale, and there's no way to set "$200/month food budget across all agents."
The Wallet Agent is the permission layer that sits between you and every AI agent — so you give consent once, with cryptographic limits, instead of pasting your credit card into Operator, then Computer Use, then Copilot, then the next one that launches.
This is the consumer-side counterpart to the merchant-side identity work — same cryptographic primitives, opposite end of the transaction.
Tell us your city. We open it when 5+ merchants are live.
Categories open one at a time — restaurants in Raleigh might open before salons in Durham, depending on which merchants sign up first. We'll email you the day yours opens.
Free for users — always. We make money from merchants on completed transactions. No marketing emails; only "your category just opened" when it does.
Common questions
How is this different from Apple Pay or a crypto wallet?
Apple Pay is tap-to-pay for humans. Crypto wallets hold tokens for self-directed transactions. The Wallet Agent is the permission layer for AI agents acting on your behalf — a problem neither of those solves. It issues short-lived, scoped permissions so an agent can transact within your rules without you re-confirming each time.
What's actually working today?
The browser extension that surfaces verified AgentPKI merchants when you chat with an AI assistant. Discovery only — no spending limits, no payment routing, no signed receipts yet. Those depend on the commerce primitives (/quote, /book, /receipt) which we haven't shipped.
What if an AI agent goes rogue and tries to overspend?
Once the consent layer ships, scoped passports are cryptographically bound to your max-value rule. The merchant's verifier rejects any passport that exceeds scope — not "trust us," actual protocol-level rejection. Today (discovery only) this isn't relevant because no spending happens through the extension.
You can see what I buy?
No purchase flow exists yet, so nothing to see. When the consent layer ships, the default will be local signing — we never see purchase content. Self-custody option means even we can't read transaction metadata. We make money from merchant take-rates, not user data.