APIs, MCP tools, data feeds, and provider workflows can become metered products in one registry.
$MFLOW is the utility layer.
Meterflow is building the Solana control plane for agent commerce. $MFLOW is designed to sit around that network: provider verification, fee relief, registry ranking, higher policy limits, premium analytics, and longer receipt retention.
TBA
More endpoints. More receipts. More reasons to hold.
Agent payments are becoming real. The scarce layer is not another payment button; it is the operating system around paid usage. Meterflow is building the place where providers price routes, agents stay inside budgets, payment rails normalize into one ledger, and every paid call becomes an auditable receipt.
Every call can produce spend policy checks, payment state, receipt data, revenue attribution, and public provider signal.
Holder tiers can unlock fee relief, higher limits, longer retention, premium analytics, and provider reputation benefits as the network expands.
Meterflow can now meter other people's APIs.
A provider brings an endpoint. Meterflow creates the meter, hosted route, x402/MPP payment surface, normalized receipt model, budget checks, revenue view, registry listing, and webhook stream.
External APIs can become agent-accessible products without moving into Meterflow.
Payment rails can normalize into the same meter, budget, receipt, and revenue model.
Useful endpoints can rank by verification, price, uptime, latency, and receipt volume.
Every paid call can link payer, provider, route, amount, policy, response, latency, and tx signature.
Operators can set daily caps, per-call caps, route allowlists, and revocation.
Providers get revenue views, registry signal, and signed webhooks for payment and receipt events.
Chart coming soon
Meterflow
$MFLOW details are coming soon.
Holder data coming soon
| # | Wallet | Amount | Supply | Accounts |
|---|---|---|---|---|
| Holder data appears after launch. | ||||