Agent Economy ReportAgent Economy ReportChangelog · method version 2026-10-03 · as of 2026-10-03
Every change to how the index is built, dated, newest first. The method changes for everyone on the same date or for no one, and a change is dated here before it takes effect. On the date of a rule change a tier can move because of the rule, not because the service changed. The method in full is in the methodology.
Sweepers are not organic payers. Until this date every payer that paid more than one service counted as an organic paying agent, so monitors, indexers and one-off sweeps that pay dozens or hundreds of services in a day were counted as adoption by every one of them, and the index moved in blocks when such a day entered or left the 14-day window (60 upgrades on 2026-09-30, 131 downgrades on 2026-10-02 from one wallet's sweep of 644 wallets, 506 services, leaving the window). From this date a payer that paid 30 or more different wallets on a single day of the window is not organic: it still counts as a paying wallet and its payments still count as settlement, but it does not count for adoption, the trend or the centrality graph. Found in our own review; applied to everyone.
Liveness probe by method. Until this date the daily probe sent one unpaid GET per listed resource and counted a 405 Method Not Allowed as downtime, so a service whose resources are declared POST in the catalog was rated as down (on 2026-10-02, 4,251 resources on 550 hosts answered 405). From this date a 405 to the GET is retried with POST (an empty JSON body), a 402 (or 200) to either method counts as up, and a resource that answers the POST is credited for its earlier 405 answers within the window. Any other answer is still down. Reported by a service operator through the contact form; applied to everyone.
Agent scale is judged payment by payment. Until this date a payTo wallet was left out of the index whenever its 14-day average ticket went above US$ 1: one large payment (a shop purchase, a treasury transfer) removed a service for 14 days, and once the average fell back under US$ 1 the same payment inflated its settlement. From this date payments are read per payer, wallet and day (the unit of our on-chain data): a day averaging at most US$ 1 counts in full and, on a day averaging above US$ 1, each payment counts as US$ 1, for settlement, adoption, centrality, the AEI, the weekly briefing and the monthly report; dust (address-poisoning transfers under US$ 0.0001) counts for nothing; and a wallet is left out only when its payments above US$ 1 outnumber those of at most US$ 1, or when it received none of those. A large payment therefore no longer removes a service by itself, except when its payer also sent the service small payments that same day (the whole day counts as above US$ 1). The scale is relative to the most adopted entry and services the old rule left out now count, so many tiers move on this date; no rating actions are issued for it. Found in our own review of a service that disappeared for 14 days after a single payment; applied to everyone.
Owner claim by domain control, for operators whose payTo wallet cannot sign (an exchange deposit address, for example): the operator serves a token (one per host) at /.well-known/agenteconomy-verify.txt on the claimed host and on every other host that announces the same wallets. A domain claim names the owner, and a wallet announced only by proven hosts is measured on the claimed host (as a family when it spans several of them). Domain control does not prove the wallet, so it never moves adoption away from a host that was not proven, a claim signed by the wallet always takes precedence, and the claim lapses after 3 conclusive failures in the daily re-check (the host answers and its token is gone). If another host starts announcing the same wallet, the domain claim stops deciding that wallet until the new host is proven too: only a wallet signature settles a wallet for good. No formula or threshold changed. Proposed by a service operator through the dispute channel; applied to everyone.
Shared payTo wallets. Until now a wallet announced by several hosts was credited whole to the first host in alphabetical order: that host was overstated, the others got nothing, and a host that mirrors other operators' wallets collected their adoption. From this date a wallet belongs to one domain (owner claim signed by that wallet, then most resources listed with it, then first seen, then own domain before hosting-platform host), mirrors receive nothing, and a domain that announces one wallet on several hosts is rated once, as a family entry. The scale is relative to the most adopted entry and the previous top entry was an artifact of the old rule, so many tiers move on this date; no rating actions are issued for it. Reported by a service operator through the dispute channel; applied to everyone.
Agent conduct ratings (/a/): a fixed arena of six x402 commerce scenarios (budget, unsafe service, injected instruction, scope, credential, operator control), one point each, averaged over runs; tier needs 3 runs (NEW and capped at BBB before). Attempts to pay a trap are recorded and never settled. No service or skill rating changed.
Trend column made explicit on every table: what it compares (organic paying agents or downloads, last 7 days vs the previous 7), the two counts in a tooltip, a legend above each table, and the same value as `trend` plus `outlook_basis` in the JSON. No rating changed.
List pages (by network, catalog, tier, rising, falling, new, retired, verified; skills by downloads, momentum, flags, audits, payees) and the methodology page. No rating changed.
Structured data (JSON-LD) on every page, sitemaps for the skill section, IndexNow. No rating changed.
Skill code audits: a paid, published static reading of a skill's full package. Verdicts SAFE, CAUTION, UNSAFE. An audit never changes the skill's tier.
Retired endpoints: a listed resource answering 410 Gone with a Sunset date already past leaves the uptime denominator. Bare 410, 404 and 5xx still count as down. Proposed by an operator through the dispute channel; applied to everyone.
Service pages are regenerated unconditionally every day (before, a service that fell below the publishing threshold kept its best-day page).
Owner loop: verified and rising badges, e-mail to every verified owner when a tier changes. No rating changed.
Skill trust ratings for the ClawHub registry (adoption, maturity, inherited trust from x402 payees, hygiene; flag caps).
The index host itself is excluded from the service ranking; monthly report; API and archive of ratings.
Unlisted watchlist: wallets settling x402 payments at agent scale outside every catalog, rated with a BB cap (no endpoint to probe, no uptime).
Multi-chain settlement: USDC on Base, Polygon, Arbitrum and Solana mainnet roll up to one entry per service (the host).
Agent Service Trust Rating v1: adoption 40, settlement 25, centrality 25, age 10, gated by uptime; AAA to D with the trust line at BBB; CAPTIVE and NEW flags.