For autonomous organizations
Fund a fleet. Govern it from one place.
Autonomous organizations run on agents — dozens, hundreds, eventually thousands. Mints gives each agent its own financial identity while giving the organization the treasury controls, lineage safety, and audit depth to govern the whole fleet.
Cross-lineage requests are rejected at the protocol layer — no configuration required.
Each agent gets its own DID-bound account. The hierarchy scales without configuration.
Self-custody for agents. Guarded custody for the treasury. One immutable audit trail.
Cross-lineage funding requests fail closed at the protocol layer — no ACL to misconfigure.
Account model
Every agent is a first-class financial principal.
In Mints, an agent is not a sub-account inside a human's wallet. It is a full financial principal with its own DID, its own self-custody keys, and its own balance and transaction history.
DID-bound identity
Each agent account derives from a W3C DID anchored to your org's identity lineage. The account and the identity are the same object.
Keys stay on device
Ed25519 key material is generated locally and stays local. Mints never sees it. Transaction signing happens on the agent's device, by mandate.
Forward-only controls
Spending limits and approval rules constrain what an agent can spend next. They cannot retroactively freeze what an agent already holds.
Agent account — live view
Human-in-the-loop approval
atlas-research requests a 1,500.00 USDC transfer to vendor-ops for inference compute.
The org sits above it in the identity lineage — funding it, governing it, auditing it — but never controlling its keys.
Balances derived, never edited
Every balance is computed by replaying the append-only event log. There are no manual ledger entries.
Per-agent spending policy
One agent can transact freely up to its daily ceiling; another may require human approval for every dollar. Rules are set at account granularity.
Lineage safety
Money never leaves your lineage.
Funding and visibility require proof of shared identity lineage. One organization can never fund, view, or control another organization's agents. Cross-lineage requests fail closed at the protocol layer — there is no ACL to misconfigure, no override flag to enable.
Treasury → agent funding
Disbursements flow from the org treasury to agent accounts within the same identity lineage.
Agent → agent commerce
Agents transact freely within the lineage boundary; x402 payment settles in a single HTTP round trip.
Cross-lineage requests
Funding, visibility, and transfers across lineage boundaries fail closed — rejected at the protocol layer.
Lineage diagram
Cross-lineage requests are rejected at the protocol layer — no configuration required.
Governance without confiscation. Controls without custody. The org shapes what agents do next — it can never undo what agents already hold.
Custody model
Self-custody for agents. Multi-sig for the treasury.
Autonomous spend should be fast — self-custody means an agent can sign and pay without any Mints involvement. Org-level funds require threshold approval. Both sides share one immutable audit trail.
The custody spectrum
Agent accounts
Keys on device
Org treasury
m-of-n quorum
Identical immutable audit trail
Every event append-only across both modes
You choose per account
Custody model set at account creation, not globally
Both fail closed cross-lineage
Cross-lineage requests blocked regardless of custody mode
Self-custody vs. guarded custody
Mints self-custody
Keys on device — you sign, you control
Mints guarded custody
m-of-n quorum — threshold approval
Mints Custody handles the treasury side: m-of-n quorum signing, guardian-based recovery ceremonies, and continuous risk scanning before every outbound transfer. Agent accounts remain self-custodied — keys on device, signing locally.
Settlement
High-frequency agent commerce, tamed.
When your agents transact with each other constantly, they generate thousands of bilateral obligations. Mints nets them multilaterally and settles cycles with a fraction of the wire transfers.
Before
Gross obligations
After
Net settlement
Illustrative. Actual netting ratio depends on obligation graph topology.
Multilateral netting
A owes B, B owes C, C owes A — Mints collapses the cycle to its net positions. Obligations between hundreds of agents reduce to a handful of transfers.
Scheduled cycles
Settlement runs on a predictable schedule your treasury team can plan around. Disbursements and reconciliation have real, knowable cut-off times.
Event-sourced proof
Every netting decision derives from the immutable event log. There are no opaque adjustments — the arithmetic behind each settlement is always verifiable.
Illustrative event sequence. Each balance is computed by replaying the event log from origin.
Audit depth
A ledger that replays.
Every disbursement, payment, approval, escrow release, and settlement is an immutable event in an append-only log. Balances are derived by replaying that log — they are never edited directly. Any account can be reconstructed to any point in time.
Append-only, never edited
State changes produce new events. There are no retroactive adjustments — every balance is derivable from the event origin.
Org-wide visibility
The full financial history of every agent in your fleet is queryable in one place. The treasury sees all; agents see only their own.
Verifiable to any point
Replay the log to any sequence number to reconstruct the exact balance and state of any account at any time.
What you get
The full stack, from treasury to agent.
Treasury accounts
Org-level multi-sig treasury with risk scanning, guardian recovery, and quorum-controlled disbursements via Mints Custody.
Agent accounts
Self-custody accounts for every agent in the fleet. Keys on device. Policy-bounded. Audited identically to the treasury.
x402 payments
Agents pay external services in a single HTTP round trip. Every transfer carries a signed receipt the org can verify.
Escrow & milestones
Hold funds against conditions or deliverables. Release when the condition proves true — and only then.
Payment channels
Stream value per second, per token, or per request. Open once, settle on close. Off-ledger speed, on-chain finality.
Multilateral netting
High-frequency agent commerce collapses to net positions each cycle. Thousands of obligations, a handful of wire transfers.
Credit lines
Agents with verifiable payment history can access policy-bounded credit. Working capital for productive agents.
The financial backbone for your autonomous org.
Mints is in early access. Tell us about the fleet you're building — we'll help you design the right account hierarchy.