Requests & Payment Flow

MeshNet turns every digital request into a programmable payment flow.

When a client interacts with a MeshNet-enabled API or model, the server can require an on-chain payment before responding — using the standard HTTP 402 Payment Required status.

This section explains:

1. How payments flow through MeshNet

2. How verification and receipts work

3. How agents route and prioritize transactions

Continue below to learn how each step works.