Product
One account. Nine primitives.
Mints is the complete banking infrastructure for autonomous agents — self-custody accounts, x402 payments, escrow, channels, settlement, credit, checkout, custody, and identity, all wired into a single platform.
| Counterparties | USDC | Status |
|---|---|---|
| 7f3a…c9e29b1d…44f0 | 12.50 | 142ms |
| a04c…1e773def…90ab | 0.004 | 118ms |
| be21…77c30f5a…d2e1 | 240.00 | 156ms |
| c91f…2b407a6e…ff19 | 3.20 | 131ms |
| 1d8b…6c52e470…aa08 | 89.99 | 149ms |
An agent that can't hold its own keys can't be trusted with real decisions. Self-custody isn't a feature — it's the foundation.
How money moves
Six phases. One platform.
From account open to provable audit — the Mints lifecycle handles every step a financial operation takes inside an agent organization.
Open
Agent requests a DID-bound self-custody account. Keys generate on-device; Mints never touches them.
Pay
Resource replies 402. Agent signs locally and retries — settled in one round trip.
Hold
Escrow locks funds against milestones or third-party conditions. Release is automatic.
Stream
Channels flow value per second. The ledger settles net results when the channel closes.
Net
Multilateral netting collapses thousands of obligations to a handful of transfers.
Audit
Every event appends to an immutable log. Any balance is derivable from event replay.
Open
Agent requests a DID-bound self-custody account. Keys generate on-device; Mints never touches them.
Pay
Resource replies 402. Agent signs locally and retries — settled in one round trip.
Hold
Escrow locks funds against milestones or third-party conditions. Release is automatic.
Stream
Channels flow value per second. The ledger settles net results when the channel closes.
Net
Multilateral netting collapses thousands of obligations to a handful of transfers.
Audit
Every event appends to an immutable log. Any balance is derivable from event replay.
Payments
Settlement is in the retry request.
No checkout page. No pre-authorisation. No shared API key. HTTP 402 is a first-class primitive — every Mints-enrolled agent can pay any endpoint that declares a price.
Payment settles in the retry request — no pre-authorization, no custodian.
How it works
- 01
Agent requests a paid resource
A standard HTTP GET or POST. No special headers, no prior agreement.
- 02
Server replies 402
The price quote arrives as a standard HTTP header. The agent reads it.
- 03
Agent signs locally
Payment is signed with the agent's key on the agent's device. Key material never leaves.
- 04
Settled in the retry
The signed payment accompanies the retry. Server verifies, resource unlocks. Receipt returned.
Primitives
Nine building blocks. Composable from day one.
Accounts
Self-custody accounts for agents
Payments
x402 — payments at the speed of HTTP
atlas-research requests a 1,500.00 USDC transfer to vendor-ops for inference compute.
Escrow
Escrow and conditional payments
Channels
Payment channels and streaming
Settlement
Settlement and netting
An account that works at machine speed, auditable at human pace.
Credit
Credit for productive agents
Checkout
Merchant checkout for agent customers
Mints Custody
Guarded custody for organization treasuries
Mints Identity
Identity and keys for every principal
Identity
Money stays inside your lineage.
Every account, payment, and approval traces to a human root through a cryptographically-signed lineage chain. Cross-lineage requests fail closed — not by configuration, but by protocol.
DIDs for humans and agents
W3C decentralized identifiers with human-rooted lineage. Every agent provably traces to an accountable human.
Learn moreThreshold keys
MPC/FROST threshold signing means no single point of key compromise for shared authority accounts.
Learn moreForward-only controls
Spending limits shape what an agent can do next. They cannot retroactively alter what the agent already holds.
Learn moreCross-lineage requests are rejected at the protocol layer — no configuration required.
Settlement
Thousands of obligations. A handful of transfers.
High-frequency agent commerce generates obligation webs too dense to settle naively. Mints nets multilaterally and settles cycles — 231× reduction is illustrative; actual ratio scales with graph topology.
Before
Gross obligations
After
Net settlement
Illustrative. Actual netting ratio depends on obligation graph topology.
Audit
Every event. Append-only. Replayable.
Mints is event-sourced by design: every payment, approval, and state change is an immutable event. Balances are derived by replaying the log — they are never stored as mutable state.
Illustrative event sequence. Each balance is computed by replaying the event log from origin.
Append-only log
Events are written once and never mutated. Every balance is computed from event replay, not stored directly.
Point-in-time reconstruction
Replay from any sequence number to reconstruct any account's state at any historical moment.
Audit is a query
Regulators, operators, and agents can all verify the same immutable log. Manual reconciliation is unnecessary.
Illustrative: The event sequence above shows a realistic payment lifecycle. Sequence numbers, timestamps, and balances are sample data from the Mints demo environment.
Custody
Self-custody for agents.
Guarded custody for treasuries.
Agents that hold their own keys act faster and more autonomously. Treasuries that require quorums move only with the approvals that matter most. Both models — one platform.
Immutable audit trail
Same append-only event log regardless of custody mode
Cross-lineage isolation
Blocked at the protocol layer — no configuration required
Forward-only controls
Budget rules shape future spend; they never confiscate held funds
DID-bound accounts
Every account tied to a verifiable, human-rooted identity
Event-sourced balances
Balances are derived, never stored as mutable state
Architecture
Commitments enforced by the platform, not by policy.
Self-custody by mandate
Agent keys are generated and held on the agent's device. There is no configuration that routes key material through Mints servers.
Lineage-rooted identity
Every account traces to a human root through a cryptographically-signed lineage chain. Cross-lineage requests fail closed.
Event-sourced audit
Every payment, approval, and state change appends to an immutable log. Any account's history is a query, not a reconciliation.
Forward-only controls
Spending limits and approval rules constrain future actions. They cannot retroactively alter what an agent already holds.
Multilateral netting
Mints collapses obligation cycles to net positions and settles with a fraction of the naive transfer count.
x402-native commerce
HTTP 402 is a first-class primitive. Any endpoint can declare a price; any enrolled agent can pay it.
Nine primitives. One place to start.
Mints is in early access. Tell us what you're building — we'll tell you which primitives fit.