Mints Banking · Settlement
Thousands of obligations. A handful of transfers.
High-frequency agent commerce produces thousands of obligations. Mints nets them multilaterally and settles cycles with a fraction of the transfers.
| 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 |
Multilateral netting
The obligation graph collapses.
High-frequency agent commerce generates a dense web of bilateral obligations. Mints finds all cycles across the graph and reduces them to their net positions before a single transfer executes.
Before
Gross obligations
After
Net settlement
Illustrative. Actual netting ratio depends on obligation graph topology.
Settlement reduction · Cycle #14 · illustrative
Actual reduction depends on obligation graph topology and cycle membership. Dense, circular graphs yield the highest ratios.
Event-sourced proof
Every netting decision is in the log.
Settlement is not a black box. Every obligation evaluated, every net position computed, every transfer executed — each step is an immutable event in an append-only stream. Replay to any point.
Illustrative event sequence. Each balance is computed by replaying the event log from origin.
Settlement should be something treasury plans around, not something treasury worries about.
Capabilities
What settlement does for your agents.
Agents transact freely. Mints handles the netting. Treasury sees a clean, auditable ledger.
Multilateral netting
Mints evaluates the full obligation graph across all agents in a cycle, not just bilateral pairs. Circular debts cancel entirely.
Scheduled cycles
Cycles run on a predictable schedule. Your treasury knows exactly when settlement occurs — no surprises, no manual triggers.
Event-sourced proof
Every netting decision is logged as an immutable event. Auditors can reconstruct any past state by replaying the event history.
Cross-product composability
Escrow releases, channel settlements, and payment confirmations all feed the same netting cycle. One settlement layer for the whole stack.
Cycle #14 · completed
14:31:47 UTC
Cycle #15 · in progress
18:00:00 UTC
Cycle #16 · scheduled
22:00:00 UTC
How a cycle runs
Five deterministic steps, every time.
A settlement cycle is not heuristic. The same obligation graph always produces the same net result. The cycle is a pure function of the event log.
Obligations accumulate
Agents transact continuously. Every payment creates a bilateral obligation that enters the pending graph.
Graph is built
Mints builds the obligation graph: who owes whom and how much, across every agent in the cycle.
Netting runs
Multilateral netting collapses cycles. A owes B, B owes C, C owes A — the net position is zero for all three.
Net transfers execute
Only residual positions move. Gross obligations in the hundreds of thousands settle into a handful of transfers.
Events appended
Every netting decision is written as an immutable event. Replay the log to reconstruct any past balance.
Obligations accumulate
Agents transact continuously. Every payment creates a bilateral obligation that enters the pending graph.
Graph is built
Mints builds the obligation graph: who owes whom and how much, across every agent in the cycle.
Netting runs
Multilateral netting collapses cycles. A owes B, B owes C, C owes A — the net position is zero for all three.
Net transfers execute
Only residual positions move. Gross obligations in the hundreds of thousands settle into a handful of transfers.
Events appended
Every netting decision is written as an immutable event. Replay the log to reconstruct any past balance.
Gross · Cycle #14
2,847
obligations
$284,190
gross value
Net · Cycle #14
12
transfers
$9,340
net movement
When a cycle completes, the net transfer ledger is published as an event. Any system — your treasury dashboard, a reconciliation agent, an external auditor — can read that event and derive the same positions independently.
If a settlement event is ever in question, the answer is the event log. There is no separate source of truth, no manual override, no side-channel.
$ mints status
Service: operational
Next settlement cycle: 2026-06-13T18:00:00Z
Cycle #14 · completed 14:31:47 UTC
Obligations: 2,847
Net transfers: 12
Gross: $284,190.00
Net: $9,340.00Related products
Settlement is the layer everything settles into.
Payments, escrows, and channel closes all route through the settlement layer. You do not call settlement directly — it absorbs obligations generated by the other primitives and nets them on your behalf.
Settlement at machine scale.
Mints is in early access. Tell us about your agent fleet and the obligation volume you need to net.