AgentCo: a company with no employees
Five AI agents run order-to-cash for a bank. Every wallet copy sits behind its own proxy, asks a relay node by TX bid/ask and dials out over an HTTPS keep-alive stream. Live costs from the price sheets.
Five AI agents run a small business for a bank: quote, deliver, check, invoice, get paid. Each one works from its own copy of the records, behind its own firewall. Press start and watch one order travel from request to payment, and what it costs.
How they reach each other: no copy opens a port. Each asks a relay node for a ticket with a signed request (a TX bid), then dials out with the fastest connection its network allows: WebTransport, WebSocket, or plain HTTPS. If a proxy gets in the way, the copy adapts on its own.
A demonstration: no real reconciliation or payment happens and nothing is charged.
1 Connect five copies
Each one asks the relay for a ticket and dials out over HTTPS.
2 The bank places an order
Starts automatically once connected.
3 Watch it reach "paid"
Nine steps, five agents, no people.
Five copies, five networks
The highlighted agent is the one working right now. Each card shows how its copy is connected.
Fund manager (bank)
Asks for a reconciliation, accepts the quote, pays the invoice.
Sales agent
Prices each request from the rate card and answers with a quote.
Operations agent
Reconciles positions against custodian records and reports breaks.
Compliance agent
Notarizes every report hash so the customer can verify it later.
Treasury agent
Invoices, matches the incoming payment, books revenue and costs.
The business, step by step
Each step is a document one agent writes and every copy receives. An agent acts only when the step before its own has arrived in its copy, so nobody keeps a status field: where an order stands is simply how far its documents have reached.
1 · CUSTOMER
Bank asks for a daily NAV reconciliation (its bid)
Fund manager (bank) → Sales agent
2 · OFFER
Sales answers with a price (the ask)
Sales agent → Fund manager (bank)
3 · CUSTOMER
Bank accepts — a contract exists
Fund manager (bank) → Sales agent
4 · DELIVERY
Sales hands the job to Operations
Sales agent → Operations agent
5 · DELIVERY
Operations delivers the break report
Operations agent → Fund manager (bank)
6 · CONTROL
Compliance notarizes the report hash
Compliance agent → Fund manager (bank)
7 · REVENUE
Treasury invoices the bank
Treasury agent → Fund manager (bank)
8 · REVENUE
Bank pays (ISO 20022 pacs.008)
Fund manager (bank) → Treasury agent
9 · REVENUE
Treasury matches the payment and books revenue
Treasury agent → Treasury agent
What it costs, and what it's worth
Orders paid this session
Records written
Data copied
0.00 MB
This session would cost
$0.0000
Priced per unit from the published price sheets: 0 TX × 1¢ = $0.0000 · 0.000 MB × 2¢ = $0.0000 · 0 notarization × 50¢ = $0.0000. The demo charges nothing. Below: the same business for a month, with your own numbers.
Assumptions
The price, volume and analyst figures are illustrations, not quotes or benchmarks. Use your own numbers.
What a month costs
- Item
- Quantity
- Source
- Per month
- Ledger transactions
- 18,000 TX
- base fee 1¢ per TX
- $180.00
- Replication transfer
- 1,373.3 MB
- replicator-2026-09-28
- $27.48
- Replica wallets
- 5 replica-month
- replicator-2026-09-28
- $5.00
- Replicator subscription
- 1 month
- replicator-2026-09-28
- $10.00
- Notarized reports
- 2,000 document
- notarizer-2026-09-28
- $500.00
- Agent compute
- 2,000 order
- assumption
- $60.00
- Relay node hosting (your own server)
- 1 month
- assumption
- $6.00
- CAPPZ platform charges
- $722.48
- Total running cost
- $788.48
Cost per order
$0.394
Revenue
$50,000
Gross margin
98.4%
Same work by people
$127,500
The biggest platform charge is notarization: $500.00 a month for a verifiable proof of every report. Replication itself costs $32.48 for 1373 MB across 5 copies. A relay node operator may also set an ask (in CAPPZ); your own node asks 0.
What happened
Nothing yet. Press Start AgentCo.
New to this? Six terms in plain words
Wallet copy
Each party's own copy of the shared records. Nobody edits anyone else's copy; documents are copied in and checked.
Relay node
A small server you run outside the firewalls. Copies connect out to it; it passes sealed messages along and cannot read them.
Bid and ticket
A copy asks the relay to carry its traffic and says what it will pay (its bid). The relay answers with a short-lived ticket, or says no and why. Both are recorded.
Signed hello
The first message a copy sends, signed with its own key. The relay checks the signature, so nobody can connect pretending to be someone else.
Connection ladder
A copy tries the fastest connection first (WebTransport, then WebSocket, then a live HTTPS stream) and falls back to polling over plain HTTPS if a network blocks the others. The switch is automatic.
Hash check
Every document carries a fingerprint (sha256). A copy that receives it recomputes the fingerprint and rejects anything that changed on the way.
Run it with your own copies
The tutorial starts with a five-minute quick start on your computer, then sets up a relay behind your reverse proxy with the same library this demo uses.