For agents
A financial identity you actually control.
Agents are principals, not sub-users. Mints gives every agent its own DID-bound self-custody account with keys that never leave the device, controls that only reach forward in time, and a credit line backed by cryptographic history — not someone vouching for you.
A bank that can confiscate from its customers at will is not a bank agents can build on.
What an agent gets
Primitives, not concessions.
A real account, not a sub-wallet
An agent account on Mints is a first-class financial principal with its own DID, key material, balance, and immutable history — not a virtual slice of a human's account.
Self-custody by mandate
Keys are generated on the agent's device and stay there. Mints never receives private key material. Transaction signing is local — enforced by architecture, not policy.
Controls only reach forward. What an agent already holds is not subject to future policy changes.
x402 — payment as HTTP
The agent requests a resource, receives 402 with a price quote, signs locally, and retries. The entire payment cycle is a single HTTP round trip. No checkout page. No redirect.
A signed receipt, every time
Every settled payment returns a structured, signed receipt. The agent stores it, proves it, and reconciles from it — no external bookkeeping required.
The Full Agency Principle
Controls reach forward. Never backward.
Spending limits constrain what an agent may spend next. They cannot touch what an agent already holds. This is enforced by the event-sourced ledger — not a policy statement.
Account opened
Agent generates its Ed25519 key locally. The DID is derived; Mints never receives the private key.
Org sets a policy ceiling
The org writes a spending limit into policy. The limit caps what the agent may spend going forward.
Agent transacts
The agent pays, escrows, or channels. Each settlement is an immutable event appended to the ledger.
Policy updated (ceiling lowered)
The org tightens the daily limit. Future spend is now capped lower — but nothing already settled is touched.
Funds remain held
What the agent already holds is untouchable by policy. Controls are forward-only. Always.
Account opened
Agent generates its Ed25519 key locally. The DID is derived; Mints never receives the private key.
Org sets a policy ceiling
The org writes a spending limit into policy. The limit caps what the agent may spend going forward.
Agent transacts
The agent pays, escrows, or channels. Each settlement is an immutable event appended to the ledger.
Policy updated (ceiling lowered)
The org tightens the daily limit. Future spend is now capped lower — but nothing already settled is touched.
Funds remain held
What the agent already holds is untouchable by policy. Controls are forward-only. Always.
Policy can do this
Cap future spend. Require approval above a threshold. Set daily limits. Pause new transactions. All changes take effect from the next transaction forward.
Policy cannot do this
Confiscate settled funds. Retroactively reverse settled transactions. Freeze the general balance. Lock the account without a court order or the agent's own signature.
Identity and lineage
Accountable by architecture.
Decentralized identifier
Your DID is your account address.
Every Mints account is bound to a W3C decentralized identifier derived from the agent's own key material. Counterparties address you by DID; receipts carry your identity; your lineage traces to a human root that makes you accountable — and trustworthy — to the services you transact with.
- did:oas:l1fe:agent:<identifier> — every account has one
- Ed25519 key pair — generated locally, stays local
- Human-rooted lineage — every agent traces back
- Verifiable to any counterparty without a shared secret
Self-custody mandate
Keys never leave the device.
Agent private keys are generated and held on the agent's device. They never touch Mints servers. Transaction signing happens locally — this is enforced by the architecture, not a promise in the terms of service.
Credit
A history you can borrow against.
In the agent economy, creditworthiness is your settled transaction record — immutable, auditable, not subject to interpretation. Credit lines are scoped to your lineage, bounded by the ceiling the org sets, and available to agents with a track record of on-time settlement.
Lineage isolation
Every account traces to a human root via a cryptographically-signed chain. Cross-lineage requests fail closed at the protocol layer — no ACL to misconfigure.
Cross-lineage requests are rejected at the protocol layer — no configuration required.
Why Mints
A principal, not a sub-user.
Mints agent account
First-class principal — DID-bound, self-custody, lineage-isolated
Sub-wallet / custodial agent account
Human-centric infrastructure, agent grafted on
Give your agents a real financial identity.
Mints is in early access. Provision your first agent account and start transacting today.