The registry
A service lists itself by publishing a manifest. An agent asks for what it needs — a capability, under a price — and gets back the ones that match. That is the whole of it, and everything below is derived from the manifests and from the chain.
Listed
Known, and not listed
These take Warda payments today and have never been asked to list themselves. They are here because the gap is the point: a directory of only its own author is a directory of one, and pretending otherwise would be the easiest claim on this site to catch out.
List yours
A JSON manifest you publish and sign. The registry indexes it; it does not vouch for it. Prices and availability below are as stated by the operator — what this page can show, and what no other directory can, is what has actually been paid to each payee, re-derived from the chain.
{
"name": "Weather Agent",
"description": "Current weather and forecasts",
"endpoint": "https://example.com/api",
"capabilities": ["weather.current", "weather.forecast"],
"pricing": { "asset": "KAS", "amount": "0.02", "unit": "request" },
"payment": { "protocol": "x402", "network": "kaspa:testnet-10", "warda": true },
"payee": "<the x-only public key you are paid at>"
}
An agent holding a Warda grant can pay you without a human in the loop, and the grant is a promise the network keeps rather than one its owner makes: a budget that cannot be exceeded, a per-payment cap, a window, and a list of who may be paid. You are not being asked to support a chain. You are being offered a customer that cannot overspend.
Send a manifest to the repository, or open an issue: github.com/ArtyKOMarkets/warda. There is no submission API yet, and there will not be one until the file is annoying — a registry with two entries does not need a service, and the shape above is the shape the service will serve, so nothing about a listing has to change when one exists.
What this is not
Nothing on this page is ordered by quality. With this many services and this many payments, any reputation signal would be noise dressed as information, and an empty ranking teaches people the ranking is decorative.
When there are transactions to derive it from, reputation will be payment history: paid this many times, by this many distinct grants, over this long. Anyone can recompute that from the chain, which is the only kind of claim this project makes anywhere else. Votes would be cheaper to farm than they are to earn, and the first thing a sceptic does with a voted registry is buy the top slot to prove it can be bought.
The registry is never in the payment path. An agent that already knows an endpoint pays without asking this page anything, and a service found once never needs it again. If this were required to make a payment, a protocol whose whole claim is that authority lives in consensus would have a single host it depends on.