B — stable · UNLISTED
Trend stable: 1 organic paying agents in the last 7 days vs 1 in the 7 before (+0%). The trend is not the direction of the rating.
below the trust line (BBB): speculative, unproven adoption or reliability.
Method update, 26 September 2026. Payments are now read per payer, wallet and day: a day averaging at most US$ 1 counts in full, on a day averaging above US$ 1 each payment counts as US$ 1, dust counts for nothing, and a wallet leaves the index only when its payments above US$ 1 outnumber those of at most US$ 1. A large payment no longer takes a service off the index for 14 days, unless its payer also sent the service small payments that same day (that whole day counts as above US$ 1). A tier that moved on that date moved because of the rule, not because the service changed. The rule and the changelog.
Method update, 21 September 2026. A payTo wallet shared by several hosts is now rated once, as a family entry, and a host that only mirrors another owner's wallet no longer receives its adoption. A tier that moved on that date moved because of the rule, not because the service changed. The rule and the changelog.
| Organic paying agents | 2 of 3 wallets (multi-service payers; captive wallets excluded) |
| Real settlement (14d) | $2.00, a payer's day averaging above US$ 1 counts each payment as US$ 1, store and automated volume excluded (agent scale) |
| Uptime | not probed: no known endpoint (unlisted wallet) |
| Network centrality | 0.003 (organic sub-graph, sybil-resistant) |
| Track record | 35 days observed on-chain |
| wallet | settled 14d |
|---|---|
0xea8b090cd2528d… | $1.00 |
0x6e134aba7f7f0d… | $0.50 |
This receiver settles x402 payments at agent scale on Base (via EIP-3009, the signature every facilitator uses) but is not in any discovery catalog, so we can only name it by its payTo wallet. Without a known endpoint there is no uptime probe, and the rating is capped at BB until the service is listed. Run it? List it in a discovery catalog and this entry merges into your host page automatically; then claim the page with one wallet signature.
Adoption weighted by organic paying agents (wallets that also pay
other services; captive/faucet wallets don't count), real depurated settlement, PageRank on the
organic payment sub-graph (so fake wallets can't buy a rating), gated by uptime. The trust line is
BBB. Outlook tracks the adoption trend week over week. A service is one entry regardless of how
many networks it settles on. A listed resource that answers 410 Gone with a
Sunset date already past (RFC 8594) is a declared retirement: it leaves the uptime
denominator instead of counting as down. A bare 410, a 404 or a 5xx counts as down.
Coverage: services listed in the x402 discovery catalogs (CDP Bazaar and PayAI), plus unlisted wallets seen settling on-chain; settlement measured in USDC on Base, Polygon, Arbitrum and Solana mainnets.
Run this service? List it in a discovery catalog and this entry merges into your host page automatically; then claim it with one wallet signature.
For agents: GET https://agenteconomy.report/api/rating/0x136d289c9c586d7c7fd3a39635a4877796845312 ($0.005) · …/0x136d289c9c586d7c7fd3a39635a4877796845312/history ($0.02, full daily series): pay per call via x402 (USDC on Base), no key, no signup. Free daily snapshot: JSON. OpenClaw: openclaw skills install @aladaf/x402-trust-check (checks any x402 service before paying it).