Tools How It Works Token Status Roadmap Apply as Provider GitHub X Discord Read Docs Launch Dashboard
METERFLOW TOKEN

$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.

Contract address TBA
HOLDER THESIS

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.

01 Providers launch paid routes

APIs, MCP tools, data feeds, and provider workflows can become metered products in one registry.

02 Agents create usage

Every call can produce spend policy checks, payment state, receipt data, revenue attribution, and public provider signal.

03 $MFLOW controls utility

Holder tiers can unlock fee relief, higher limits, longer retention, premium analytics, and provider reputation benefits as the network expands.

TECH UNLOCK

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.

GatewayHosted paid routes

External APIs can become agent-accessible products without moving into Meterflow.

Adapterx402 + MPP

Payment rails can normalize into the same meter, budget, receipt, and revenue model.

RegistryProvider discovery

Useful endpoints can rank by verification, price, uptime, latency, and receipt volume.

ReceiptsUsage becomes proof

Every paid call can link payer, provider, route, amount, policy, response, latency, and tx signature.

BudgetsAgent spend limits

Operators can set daily caps, per-call caps, route allowlists, and revocation.

ProvidersRevenue infrastructure

Providers get revenue views, registry signal, and signed webhooks for payment and receipt events.

Every new provider adds more routes. Every route can produce more receipts. Every receipt strengthens the utility layer around $MFLOW.
PriceTBAcoming soon
Market CapTBAcoming soon
24h VolumeTBAcoming soon
PRICE CHART

Chart coming soon

TBA
Chart appears after launch.
TOKEN DETAILS

Meterflow

$MFLOW details are coming soon.

PairTBA
FDVTBA
5m / 1h / 6hTBA
Data sourcesComing soon
HOLDERS

Holder data coming soon

TBA
#WalletAmountSupplyAccounts
Holder data appears after launch.