Name the agent
Create a profile for the agent, mission, owner, expiry window, and the kind of work it is allowed to pay for.
Private banking for AI agents
Your AI agent.
Its own card.
Under your rules.
Issue private permission cards to autonomous agents. Set spend limits, merchant scopes, approvals, and mission expiry before your agent ever touches money.
Agent card console
Issue a card without exposing the vault.
The card is a permission object: spend scope, daily limit, merchant category, approval threshold, and mission expiry all travel with the agent.
Process
Three steps to a private agent card.
Hermes Bank turns agent permissions into payment cards. Your agent gets the power to act, without access to your main wallet.
Attach spend policy
Set daily limits, merchant categories, chain routing, approval thresholds, and one-time or recurring permissions.
Relay approvals
Let the agent spend within policy. Anything unusual goes to your dashboard or messenger for approve, deny, or trust.
Capabilities
Built for agents that spend real money.
Hermes Bank is not a chatbot wallet. It is a private card layer for agents that subscribe, buy, book, deploy, and settle.
One agent, one controlled card
Give every agent a separate card identity with scoped balance, expiry, limits, and revocation.
Rules before funds
Approve categories like compute, APIs, domains, data, ads, or subscriptions before the card is issued.
Spending history that compounds
Hermes learns trusted merchants, normal behavior, owner corrections, and suspicious spending patterns.
Approve from wherever you work
Receive high-risk spend requests in a dashboard, Telegram, iMessage, Slack, or an API callback.
Cards
A card type for every agent mission.
Start with templates, then tune the policy. Cards can be persistent, one-time, invisible, or approval-gated.
24h
temporary task card
- One mission, one budget
- Auto-expiry after task
- Merchant category locks
- Human approval above limit
Private
masked agent payments
- Private card alias
- Isolated agent balance
- Revocable at any moment
- Owner-only audit trail
Pro
chief-of-staff agent card
- Higher policy limits
- Recurring SaaS payments
- Team approval flows
- Advanced trust memory
Agent access
A payment shell agents can slurp.
Hermes exposes a clean agent wrapper: a manifest, OpenAPI contract, scoped permissions, and card-order primitives. Agents can discover what they are allowed to do before they ever request spend.
Discover
Read the Hermes manifest and learn available actions, scopes, limits, and safety rules.
Request
Create a payment intent or card-order request with mission, amount, and policy context.
Settle
Wait for crypto confirmation, then receive a Hermes card tab and transaction ledger state.
FAQ
Common questions.
A Hermes Bank card is a private payment permission issued to an
AI agent. The card has its own limits, scopes, expiry, owner, and
audit trail, so the agent can act without touching your main
wallet or account.
Only inside the policy you set. For example, a Dev Agent can buy
compute credits up to $25, but anything above that or outside the
approved merchant category requires owner approval.
The product is designed as a crypto-native private card layer,
with room for card-network rails later. The core primitive is the
policy-controlled agent card.
Hermes is the messenger and courier. Hermes Bank carries value
between owners, agents, merchants, and protocols while preserving
rules, privacy, and intent.
Ready to give your agent a private card?
Issue a mission card, set the policy, and let Hermes relay the payment only when the agent stays inside your rules.