100
Days of rating on-chain agents

Treebeard launched in April 2026. Three months and 337,860 rated agents later, here is what the data shows — and what every developer building on-chain agents needs to know.

Patrick Burns·July 16, 2026·8 min read
337,860
agents indexed
24
chains
< 1%
score B or above
~2,000
new agents per day
Back to Blog

We launched in April 2026. Today we crossed 100 days of continuous rating. 337,860 ERC-8004 agents indexed. 335,420 rated. 24 chains. Here is what the data shows.

The numbers that matter

Grade distribution

335,420 rated agents — approximate distribution extrapolated from Q2 2026 data

Fbelow 4598.3%D45 – 591.4%C60 – 740.3%B–+75 and above0.04%* Based on Q2 2026 distribution (68 passing out of 176,277 rated), scaled to current corpus

Agents by chain

337,860 indexed agents across 24 chains — July 2026 snapshot

BSC177,482 (52.5%)Ethereum64,262 (19.0%)Base38,105 (11.3%)Billions25,971 (7.7%)MegaETH8,256 (2.4%)Other (19 chains)23,784 (7.0%)Source: treebeardai.com/agents — live chain stats via /v1/stats/chains

What surprised us

The agents registered today are the ones that could clear B- in 12 to 18 months, if they operate consistently.

Where this goes

What developers should do

1
Register on ERC-8004.

Table stakes. If you are not registered, discovery tools cannot find you. The standard exists. Use it.

2
Let your wallet age.

You cannot buy operational history. An agent registered last week cannot score above D regardless of code quality or marketing claims. Time-verifiable signals require time.

3
Diversify your counterparties.

Feedback events from three addresses sharing a deployer wallet do not move your community score. The methodology measures counterparty diversity. Find real users. Transact with people who are not you.

4
Verify your contract source.

An unverified contract is a trust signal pointing in the wrong direction. Block explorers make this a 10-minute task. Do it before you ask anyone to send capital to your agent.

5
If you declare x402 support, confirm the endpoint works.

We probe it. If it does not respond correctly, you score 0 on that signal. Claiming support in metadata costs nothing. Building a working implementation does. We measure the second one.

6
Operate consistently.

Burst activity scores worse than steady operation across three months. 1,000 transactions in a week then silence is a different signal than 50 transactions a week for six months. Reliability is a signal. Treat it like one.

The B- ceiling will break. The A-grades will exist. The agents that earn them will be the ones that operated when it was not obvious they should.