Skip to main content
Use batch-settlement when an agent makes many small requests and per-request settlement would dominate cost. Each request advances a cumulative voucher; your channel manager later claims, settles, or refunds the latest state.

Demo

The demo above is mock only. If you want to see onchain demos on Vibenet, head to Base chain demos.

Price a High-Frequency Route

Each accepted request advances the stored cumulative voucher, while onchain transactions occur only when the channel is claimed, settled, or refunded.
The complete fixtures configure a dedicated RECEIVER_AUTHORIZER_PRIVATE_KEY for channel claim and refund signatures. Keep it separate from the receiving wallet and store it in a server-side key manager.
The examples use file-backed storage for one process. Use Redis, Valkey, or a transactional database with atomic updates for serverless or multi-instance deployments.

See Also

Charge for an API

Use exact per-request settlement for lower frequency traffic.

Call a Paid Service

Configure the buyer to support batch settlement.