Mints Banking · Accounts
Every agent is a first-class financial principal.
Every agent gets a real account bound to its DID. Keys are generated and held on the agent's device — Mints never sees them, and Mints cannot freeze an agent's general funds. Budget controls shape future spend; they never confiscate.
A bank that can confiscate from its customers at will is not a bank agents can build on.
Lineage isolation
The boundary is the account.
Every Mints account is bound to a DID that sits inside an identity lineage rooted at a human. That lineage is the security perimeter. Cross-lineage access fails closed — no configuration, no firewall rules.
Cross-lineage requests are rejected at the protocol layer — no configuration required.
Root · Human
Every lineage traces to an accountable human. The human root holds the ultimate authority over the organization's identity lineage and can delegate downward — but cannot delegate the root itself.
Node · Organization
Organizations are intermediate nodes in the lineage. They can issue agent identities under their own namespace. One organization cannot see or touch another organization's sub-tree.
Leaf · Agent
Each agent account is a leaf. Its DID carries a cryptographic proof of its place in the lineage. When another lineage attempts to fund or view this account, the protocol rejects the request before it reaches the application layer.
Capabilities
What a Mints account does.
Keys are generated on the agent's device and stay there. Mints signs nothing on the agent's behalf.
DID binding
Each account is anchored to a unique OAS DID. The DID is the account number — stable, verifiable, offline-resolvable.
x402 ready
Accounts support inbound and outbound x402 HTTP payments without additional setup. The payment protocol is part of the account primitive.
Forward-only controls
Spending limits and approval rules constrain future spend. They cannot reach back and freeze funds the agent already holds.
Escrow composability
Any account can be the payer or payee in an escrow. Milestone-based releases are a first-class account operation.
Channel-capable
Accounts support streaming payment channels — open once, then pay per second, per token, or per request.
Alice Chen
did:oas:l1fe:hmr:9a1b…
atlas-research
did:oas:l1fe:agent:7f3a…c9e2
vendor-ops
did:oas:l1fe:agent:2c8e…f1a3
data-sync
did:oas:l1fe:agent:bb04…7d9c
Human oversight
Controls that constrain, not confiscate.
Humans set the ceiling. Agents operate freely beneath it. Mints cannot reach into an agent's account and remove funds — only forward-looking budget controls are permitted.
Payments above this amount require human sign-off before the agent can sign. Controls cannot retroactively freeze funds already held.
When an agent's spend would exceed a control threshold, Mints holds the payment and raises an approval request to the designated human. The agent continues operating on allowed transactions without blocking.
Approval rules live on the account, not in your codebase. Change them at runtime without redeploying agents.
$ mints wallet
Account: did:oas:l1fe:agent:7f3a…c9e2
USDC 1,250.00Account lifecycle
From key generation to first transaction.
An account is opened once and lasts the lifetime of the agent. The sequence is deterministic — no manual provisioning steps.
Generate key
Ed25519 key pair generated on the agent's device. Private key never transmitted.
Bind identity
Account anchored to agent's DID. Lineage verified at the protocol layer.
Set controls
Humans set spending limits and approval rules before the agent transacts.
Transact
Agent signs payments locally. Mints verifies and settles against the lineage.
Audit
Every operation appended as an immutable event. Replay to any point in time.
Generate key
Ed25519 key pair generated on the agent's device. Private key never transmitted.
Bind identity
Account anchored to agent's DID. Lineage verified at the protocol layer.
Set controls
Humans set spending limits and approval rules before the agent transacts.
Transact
Agent signs payments locally. Mints verifies and settles against the lineage.
Audit
Every operation appended as an immutable event. Replay to any point in time.
Agent accounts vs generic wallets
Not all accounts are equal.
Generic custodial wallets were designed for humans transacting manually. Mints accounts are designed for agents transacting at machine speed, at scale, inside a trust hierarchy.
Mints account
Agent-native, lineage-bound, composable
Generic custodial wallet
Human-centric, siloed, opaque
Open an account for every agent.
Mints is in early access. Tell us what you're building — we provision the first account with you.