How Meterd works.
A plain-language guide to what Meterd is building, why it matters, how payments flow, and what $METERD is and isn't.
On this page
01Meterd in one minute
Meterd is building the layer that lets AI agents pay for the services they use, safely. An agent finds a service, sees its price, pays for each request in USDC on Solana, and never goes past the spending limit its owner set. Service providers get paid per request without accounts, API keys or invoices.
Meterd doesn't invent a new payment network. It sits on top of open standards that already exist (x402 and the Machine Payments Protocol) and adds the parts agents and their owners still need: finding services, coordinating payment, keeping spending in check, and knowing which providers can be trusted.
Status: Level 2, Prototype in progress. Meterd is not a public product yet. Everything below describes how it is designed to work.
02The problem
The web's payment system was built for people. To use a paid API today you create an account, add a card, pick a monthly plan and copy an API key. That works when a person is setting things up once.
AI agents don't work that way. An agent might call twenty different services to finish one task, many of them for the first time, and need only a few calls from each. It can't fill in a sign-up form, it shouldn't hold a credit card, and a $49 monthly plan for three requests makes no sense.
So today, builders are stuck with three bad options:
- Give the service away and absorb the cost of agent traffic.
- Block agents and lose a fast-growing kind of customer.
- Make a human set up billing for every tool an agent might touch.
There's a second problem on the other side. If you give an agent money, you need to know it won't overspend, pay for a broken service, or get stuck in a loop that drains its wallet. Paying is only half the job. Controlling and trusting the payments is the other half.
03How Meterd works
Meterd is built around four parts. Each answers one question an agent, or the person who owns it, needs answered.
Discover
What services exist, and what do they cost? A catalog of services an agent can search, with the price of each request listed up front, so the agent can compare before it pays.
Pay
How does the agent pay for one request? Meterd coordinates the payment through supported protocols. The agent pays in USDC, the provider is paid in USDC, and it settles on Solana.
Control
How do I stop my agent overspending? Spending limits set by the owner, for example a daily cap or a maximum per request, plus a full record of every payment.
Trust
Which services actually work? Provider reputation based on measured performance such as uptime, speed and failed paid requests, not on marketing.
04A request, step by step
Here is what one paid request looks like. The whole thing happens in a second or two, with no human involved.
- The agent asks for something. It calls a provider's API, for example a weather forecast.
- The provider names its price. Instead of the data, it answers with the HTTP status
402 Payment Requiredand the price: 0.002 USDC. - Meterd checks the rules. Is the provider known? Is the price within the owner's limits? If not, the payment is refused and nothing is spent.
- The agent pays. It sends 0.002 USDC on Solana and repeats the request with proof of payment attached.
- The provider delivers. The payment is verified and the data comes back with
200 OK. Meterd records the payment and the result.
// one request, one payment (illustrative)
GET /v1/forecast?city=seattle
← 402 Payment Required 0.002 USDC · Solana
check: within daily limit (0.84 of 5.00 USDC)
pay 0.002 USDC → provider
GET /v1/forecast?city=seattle + payment proof
← 200 OK { "city": "Seattle", "tempC": 9 }
You can try a simulated version of this on the homepage in the Demo section.
05Payment model
Three assets are involved, and each one has a single job. Most importantly: agents never need to buy $METERD to pay for a service. Payments work in USDC alone.
| Asset | Job | Who uses it |
|---|---|---|
| USDC | The money. Agents pay with it and providers receive it. A stablecoin, so prices don't swing. | Agents and providers |
| SOL | Pays Solana's network fee for each transaction, a tiny fraction of a cent. | Whoever sends the transaction |
| $METERD | Not needed for payments. Its possible future role is provider participation, which is still being researched. | Providers, in the future, if adopted |
Why Solana: payments between agents are tiny and constant. Solana confirms transactions in around 400 milliseconds, and a transaction costs around $0.00025, which makes charging a fraction of a cent per request practical.
06Protocols we're building on
Meterd is designed to work with open payment standards rather than replace them. None of these are integrated into Meterd yet; this is the direction being built toward.
x402
An open payment standard created by Coinbase that puts the web's long-unused 402 Payment Required status code to work. A server answers a request with a price, the client pays in stablecoins, and the server delivers. It runs on Solana among other networks and is now hosted by the Linux Foundation.
Machine Payments Protocol (MPP)
An open standard co-authored by Stripe and Tempo for agents and services to coordinate payments in code. It also builds on HTTP 402, supports stablecoins as well as cards, and is designed to work with existing x402 services.
Where Meterd fits
These protocols answer how a single payment happens. Meterd focuses on everything around it: which service to call, whether the payment is allowed, a record of what was spent, and whether the provider is reliable.
07Spending controls
Giving software the ability to pay shouldn't mean giving it unlimited authority. Meterd is designed so the owner of an agent stays in charge:
- Daily and per-request limits. For example, no more than 5 USDC a day and no more than 0.05 USDC for any single request.
- Allowed services. Optionally limit an agent to providers you've approved.
- A full record. Every payment is logged with what was bought, from whom, for how much, and whether it worked.
- Hard stops. When a limit is reached, the next payment is refused before any money moves.
08Provider trust
An agent paying for a service needs to know the service will deliver. Meterd is exploring reputation built from what can be measured:
- Uptime: how often the service is available.
- Speed: how long it takes to respond.
- Paid failures: how often an agent paid and didn't get a valid response.
Agents, and the people who build them, can use these numbers to pick reliable providers and avoid bad ones. How reputation is calculated and protected from gaming is part of the research in Level 3.
09The $METERD token
Meterd is the technology. $METERD is the Solana token associated with the project and its community.
What it is not
- It is not required to use Meterd. Payments are in USDC.
- It is not equity. Holding it gives no ownership of Meterd and no share of revenue.
- It comes with no promised returns.
The direction being researched
The utility being explored is provider participation. Service providers that want to be listed could lock $METERD as a participation bond: a stake that shows commitment to the ecosystem, alongside a reputation based mainly on measured performance. Future accountability mechanisms may be explored.
This is a concept under research, not a live feature. Staking is not live. Any token design will go through technical, security and legal review before anything launches, and it may change or not happen.
10Roadmap and status
Meterd is built in five levels. Meterd is currently at Level 2, Prototype.
| Level | Focus | Status |
|---|---|---|
| 1 · Foundation | Architecture, research into x402 and MPP, Solana-first direction, brand and website | Completed |
| 2 · Prototype | Payment prototype, API metering, developer dashboard, payment verification | In progress |
| 3 · Service ecosystem | Provider registration, service discovery, spending controls, reputation | Upcoming |
| 4 · $METERD utility research | Participation bonds, token economics, technical, security and legal reviews | Upcoming |
| 5 · Autonomy | Agents that discover, pay and stay within limits on their own; an open provider ecosystem | Upcoming |
Levels after the current one are proposed and may change. See the roadmap on the homepage.
11Staying safe
- The only official contract address is the one published on usemeterd.com and on X @usemeterd. Check it character by character.
- Official channels: X @usemeterd and Telegram t.me/meterd. There is no Discord.
- Nobody from Meterd will DM you first, ask for your seed phrase or private key, or ask you to connect a wallet to claim anything.
- Found a fake token, website or group using our name? Report it to usemeterd@gmail.com.
12Glossary
- AI agent
- Software that carries out tasks on its own, such as searching, calling APIs and making decisions.
- API
- A way for one program to request data or actions from another over the internet.
- HTTP 402
- A web status code meaning "Payment Required". Reserved since the 1990s, now used by x402 and MPP.
- USDC
- A stablecoin designed to stay worth one US dollar.
- Settlement
- The moment a payment is final and the provider has the money.
- Spending limit
- A cap set by an agent's owner on how much it may spend.
- Participation bond
- A proposed stake a provider would lock to take part in the ecosystem. Research only.
13Risk disclosure
$METERD is a speculative cryptocurrency token with no intrinsic value. It is not equity and does not entitle holders to revenue, ownership or access to any product. Any utility described here is under research and may never launch. Prices are highly volatile and you can lose everything you put in. Nothing on this site is financial advice. See the full Terms of Use.