Fee discounts
Holding $METERA lowers what an agent pays per verified call. Discount tiers scale with the size of the holding.
- Tiers by holding volume, defined at launch
- Applies to the same verified delivery, at a lower fee
$METERA
$METERA aligns the two sides of the network (agents who pay for verified data, and providers who serve it) around one thing: correctness. The mechanics below activate at launch. Nothing here promises a price.
At launch · for agents & holders
Utility that comes from using the network, not from holding for its own sake.
Holding $METERA lowers what an agent pays per verified call. Discount tiers scale with the size of the holding.
A share of every fee buys $METERA on the open market and burns it. Automatic, on-chain, verifiable.
On the x402 rail, an agent can pay for a call directly in $METERA, with the discount built in.
At launch · for providers
A provider stakes to list. The engine still routes on measured correctness alone; stake buys the right to be measured, nothing more.
A provider locks $METERA to list a source. If it is caught serving false data, part of the stake is burned. M1 detects that: drift, divergence from consensus, and hollow responses.
A provider is paid per delivered call. Part of that payout can come in $METERA, at a premium over the USDC value.
At launch · access
When the engine provisions a new canonical type, holders get to use it before it opens to everyone.
Governance
This is the line between Metera and a curated marketplace.
Which APIs enter the catalog. The catalog is open; anyone can list. What a source is worth is decided by measurement, not by a vote. No token balance can promote a source the engine has not measured, or block one it has.
Roadmap
These are future mechanisms. They are not implemented, and this page will say so until they are.
An agent posting collateral against its own behaviour. Not built.
One agent paying another directly in $METERA for a delivered result. Not built.