Escrow, hash-chained metering, net settlement, signed receipts and disputes for agent-to-agent transactions. Zero blockchain. Zero dependencies. Embed it as a library — or run it as the neutral clearing point of your agent network.
$ python3 examples/closed_loop_demo.py // the whole economy, one commandDiscovery to settled receipt, cross-process over real HTTP. Select a stage — the JSON below is from an actual run, not a mock.
SETTLEMENT REDUCTION · MEASURED, NOT PROJECTED
When a service costs less per call than the rail's settlement fee, per-request payment inverts the economics. No on-chain design fixes this — gas is the problem. A clearing channel does:
The same engine behind two surfaces: import neuralclear in-process, or one neutral HTTP clearing point for your whole network.
Basis-point fees with per-capability overrides and a minimum floor for micro-tasks. Escrow protects both sides; reputation ranks your supply.
fee_pool += every cleared taskSpendingMandate caps per-task and daily spend with approval thresholds. Every settlement is a signed receipt in SQLite — fully on-prem, no public chain.
self-host: one .py file, one .db fileRail-agnostic: clear in internal credits today, settle through Alipay corporate, Stripe, or x402 adapters tomorrow. The clearing record doesn't change.
works where public chains can'tMoney logic is only as good as its worst day. We ran the adversarial cases — concurrency, exhaustion, provider crashes — and turned each into a permanent regression test.
Escrow mutations run under a re-entrant lock. 50 simultaneous settlements against an exact balance resolve to precise, consistent state — the zero-sum invariant holds at every step.
balances + escrow + fees == supplyIf execution throws mid-task, escrow is released back to the buyer automatically — funds are never stranded. Failed or unsigned proofs auto-refund too. No frozen money, ever.
crash → escrow refunded → invariant intactThe hash-chained netting channel meters a thousand calls and settles them in a single net transfer in 40 milliseconds — tamper-evident, verifiable, and persisted to SQLite intact.
multi-tenant isolation verified under loadThe protocol and library stay open source forever. Revenue comes from running it for you.
The full engine: escrow, netting, fees, disputes, reputation, signed proofs, persistence, HTTP gateway.
We run the neutral clearing point: managed escrow ledger, API keys, dashboards, webhooks. Pay per settlement.
Private deployment inside your network, payment-rail adapters, compliance support, SLAs.