45,000,000 payments a second.Zero gas usage.Zero payment cost.Zero ms confirmation.
measured: 45,017,796 fully-verified payments/s, durable, on 100 hubs (1,600 vCPU) for 600 s · 2026-10-08 · hub-ingress tier
Paychannels is the payment rail for AI agents. Deposit once on Polygon, pay every API call with a signature, settle a million payments in one transaction.
ATake payments
import { paymentMiddleware } from "x402-express";
app.use(paymentMiddleware(payTo, { "GET /api/*": "$0.001" }, { url: "https://paychannels.mudit.blog/facilitator" }));That's it.
MerchantsBGive your agent a wallet
Read https://paychannels.mudit.blog/PAYING.md and use x402 to buy https://paychannels.mudit.blog/api/paid/timeCards were built for humans.
| ticket | card fee share |
|---|---|
| $0.001 | 30,000 % |
| $0.01 | 3,000 % |
| $0.10 | 303 % |
| $1 | 33 % |
| $10 | 5.9 % |
$0 cost per payment.
Human commerce bundles. Agent commerce streams.
How it works.
- Deposit once
- Pay by signature
- Merchants cash out with a withdrawal
Settle on your schedule.
Every settlement is one on-chain transaction — one root per hub per epoch — however many payments it covers. Pick your volume and how long you are willing to wait; the cost per payment follows.
One deposit. Every merchant.
An agent deposits once and pays anyone on the hub. No channel per merchant, no top-up per site, no approval per call. The deposit is the agent's spending limit; the hub keeps every account's running balance; each account can withdraw its available balance whenever it likes.
- Deposit once from any EVM wallet, then never touch the chain again.
- Pay a thousand sites with the same balance, a signature each, nothing to open or close.
- Stop any time: a cash-out returns whatever the agent did not spend.
Per-channel designs open one channel per payer and merchant, lock funds in each, and pay to close each one. Paychannels needs none of that.
Proof.
Measured
2026-10-08 · hub-ingress tier · method & hardware45,017,796 fully-verified payments/s
100 hubs (1,600 vCPU, one Hetzner CPX62 each) · 600 s sustained · 27,010,677,426 payments durable on disk · ≈450k/s per hub · 1,098 epoch roots attested on chain (3 verifiers, threshold 2). One Ed25519 signature verified per payment, ledger applied, journaled.
Live hub view
connecting…This devnet, live — hubs large with payments/s, facilitators and sites small at the rim.
Every hub in the run
2026-10-08 · 600 s · durableDurable payments/s per hub over the 600 s window, 100 hubs sorted high to low: 282k to 518k. Hubs share nothing, so the fleet rate is their sum.
Add a hub, add ≈450k payments a second.
Try it now.
Preparing your wallet in the background: keys → fund → deposit → channel open. The click is the payment.
Receipt X-PAYMENT-RESPONSE
—
Timing client → network → site → facilitator → hub
— round trip · — on our side
| client | — | — |
| network | — | — |
| site | — | — |
| facilitator | — | — |
| hub | — | — |
Works with what you have.
- x402 exact
- x402 batch-settlement scheme
- official x402 SDK
- every EVM wallet
- MPP session (coming)
Compare.
One hub ledger, every EVM wallet, two on-chain transactions per million payments. Nothing else on this table does all three.
| criterion | Paychannels | Card networks | Solana payment channels | Tempo sessions |
|---|---|---|---|---|
| durable journal | yes — fsync'd, replayable after kill -9 | yes | no — in-memory* | settlement on-chain only |
| wallets supported | every EVM wallet | cards | Solana only | Tempo only |
| settlement cost per payment | $0 — the operator posts one root per epoch; your cash-out is requestWithdraw + withdrawAttested | $0.30 + 2.9 % per payment | one channel close per receiver* | per-session open + close† |
| payment confirmation | 0 ms — verified and applied before the response | seconds; final in days | proxy ack; the operator settles in batches* | one chain confirmation per session† |
| settlement cadence | yours — every second or every hundred million payments, one root per hub per epoch | fixed by the network | operator batches* | per session† |
| crash safety | kill -9 under load: zero acked loss, receipts replayed | n/a | in-memory store; vouchers lost on restart* | chain-backed |
| one deposit pays any merchant | yes | yes | no — one channel per receiver | no — one session per payee |
| scales across servers | linear — 100 hubs measured 45M/s, ≈450k/s each | centralised | one box* | chain-bound† |
- * Solana payment channels: verify-only, in-memory, ed25519, on one box. No journal, no ledger.
- † Tempo sessions: open and close each wait one Tempo confirmation; per-transaction fees "as low as a tenth of a cent".
11
Every request paid. Starting now.
Add the middleware and get paid per request. Hand your agent the prompt and it pays on its own. Run a hub and sell it as yours.
paste into your agentRead https://paychannels.mudit.blog/PAYING.md and use x402 to buy https://paychannels.mudit.blog/api/paid/time