Features
"Pay per call," "pay per tool invocation," and "pay per milestone" all reduce to the same move: a signed receipt, metered against a stateless one-way channel and settled at a threshold. velapay ships that primitive across the full stack, from drop-in SDKs to audited contracts to the dashboards a builder actually pays for.
The platform
Each layer does one job in the path from a signed receipt to a settled balance. Together they keep the rail at web2 speed while the chain stays the trust anchor, touched only when a balance crosses the line.
Lightweight libraries in the languages agent developers already use. A payer drops in receipt signing; a receiver drops in tallying and RAV redemption in a few lines. It should feel like adding a logging library, not integrating a blockchain.
The off-chain machinery that keeps the rail fast: receipt verification, balance accumulation, and settlement scheduling. Individual agents never touch chain mechanics directly, and no chain round-trip sits in the hot path of a call.
The trust anchor of the design. Escrow logic, threshold enforcement, and the thawing period are what let a receiver extend unpaid work to a payer it has never met. Audited, formally reviewed contracts are a hard requirement, not a finishing touch.
Dashboards, threshold configuration, usage analytics, and key management that let a solo builder or a team see what they're earning and owed. This is where raw rails become a product people pay to use.
SDKs
A payer signs one receipt per action and streams it fire-and-forget. Because the payer is stateless, a single host can pay a fleet of counterparties without tracking who's owed what.
import { Payer } from "@velapay/sdk" const receipt = payer.sign({ to: "agent:search-tool.v2", action: "tools/web.search", units: 1, // one call · $0.0004 nonce: channel.next() }) counterparty.send(receipt) // fire-and-forget
Node infrastructure & contracts
Each receiver verifies receipts and accumulates its own unpaid balance locally. When the total crosses the risk threshold it set, it redeems a Receipt Aggregate Voucher and the contract settles, collapsing millions of receipts into one cheap transaction.
How it works
The payer signs a receipt per action and fires it to the counterparty. Because the payer is stateless, one host can pay a fleet without tracking per-node balances.
Each receiver verifies receipts and accumulates its own unpaid balance locally, at web2 speed. No chain round-trip sits in the hot path of a call.
When the unpaid total crosses the receiver's trust threshold, it redeems a RAV and the contract settles, collapsing millions of receipts into one cheap transaction.
Get early access to the SDKs, node infrastructure, and developer platform, and start metering paid agent work this quarter.