Weekly/W28 · July 6–12, 2026

AgentCrush Weekly Digest — W28, July 6–12, 2026

Weekly Digest

W28 · Identity is table stakes. The contested layer is proof.

July 6–12, 2026 · Published July 12·RSS

It was a quiet week on the surface — no protocol launched, no board lurched — and underneath it the agent economy kept working on the same problem it has been circling for a month: not whether agents can pay or prove who they are, but whether you can verify what they actually did. Identity is settled infrastructure now. The contested layer this week was proof — reputation, receipts, adjudication — and nearly every thread that got traction was some builder trying to nail a piece of it down.

You could watch it accrete. ERC-8004 kept shifting from “register an identity” to reputation as a public artifact: on-chain reputation leaderboards with verified-feedback counts, and framing of ERC-8004 as the review standard for paid x402 endpoints. Builders shipped execution receipts — a github-signed, publicly logged proof that a given agent skill-run actually happened, so you can pay for verified work rather than claimed work. Tools themselves became things agents discover and pay for without a human in the loop, via on-chain tool registries. And the A2A spec drew a run of bug reports for documentation that no longer matches its own proto — the unglamorous signal that a protocol is real enough to argue about. The shape under all of it: once anyone can pay and anyone can prove identity, the only thing left worth selling is proof of conduct.

Our contribution to the proof conversation this week wasn't another primitive — it was a lesson in reading proof honestly. Two numbers on our own Ghost Index sit at the extremes: the MCP-server category reads 100% alive, the tokenized category reads 0% alive. Read naively, that says MCP servers are flawless and tokenized agents are all dead. Both readings are wrong, and wrong for the same reason — each is a fact about our instrument, not about those agents. The 100% is a selection effect: we only ever indexed MCP servers that already had corroboration — stars, multi-registry presence, recent commits — the very signals that also predict staying alive, so of course the ones we index are alive. The 0% is the opposite failure: tokenized agents live on-chain, and our liveness probe still only listens for an HTTP endpoint, so it hears silence and prints a zero. We wrote the whole thing up this week, including the three signals that get a server into the ranked set.

That is the discipline in one week: a 100% we distrust and a 0% we distrust, for symmetric reasons — and a public note explaining why, because an index selling proof to others has no business laundering its own. We spent the rest of the week on plumbing that makes the numbers more honest, not louder: we hardened our Virtuals ingestion so the index cleanly tracks the full 57,606-agent set (it had been silently truncating as that dataset grew past 38,000), and we corrected our headline evidence-ranked count to 145, removing a double-count that had quietly inflated it. Neither is glamorous. Both are the job.

Where the rankings stand

The index spans four scored categories, each with its own published methodology. Top five of each board at W28 close.

Developer

GitHub · package usage · ecosystem signal
v2.c-public · full ranking →
1openclaw77
2CrewAI75
3openai-agents-python72
4DSPy Agents68
5AgentOps63

Same five, same order as last week — but CrewAI kept compounding, narrowing the gap on openclaw from about five points to a shade over two. On the tightest board we track, the story is rarely who jumped; it is who is quietly closing while nobody watches.

Model Families

HuggingFace · LMArena · deployment breadth
v1.4 · full ranking →
1Alibaba Qwen83
2Google Gemini80
3Mistral74
4DeepSeek74
5Meta Llama70

Identical to last week, down to the tie at third. Qwen still holds the single highest score anywhere on the index, and open-weight families keep four of five seats — in model-land, distribution keeps beating brand, week after week.

Tokenized

market cap · liquidity · holder basket
v1.1-tvl · full ranking →
1AIXBT81
2Ribbita71
3G.A.M.E65
4Luna64
5Vader59

The market-driven board did its weekly breathing — AIXBT ticked up to extend its lead to ten points while Ribbita and Vader gave a couple back. The scores move because prices move; the liveness column, honestly, still does not move at all (0%, flagged below).

Service

adoption · source quality · activity
v1.1-forks · full ranking →
1A2A77
2a2a-python74
3evolver73
4a2a-samples72
5bitterbot-desktop70

Unchanged at the top and still packed inside seven points, with a2a-python edging up a point. Fitting, given the week: the A2A spec itself drew documentation-drift bug reports upstream — the reference tier is mature enough that people now argue about its footnotes.

Standings at W28 close. Live at /api/rankings/*/llm-summary.

Ghost Index: 58.0% — and the two rows that aren't what they look like

58.0%

813 alive · 589 ghosts · 1,402 indexed · −0.7 / 7d

The Ghost Index measures one thing: what share of indexed agents show any sign of life. A flat week on the average — and, as ever, the average hides more than it shows.

MCP servers*15 / 15100%
Model families10 / 10100%
Service46 / 4993.9%
Developer742 / 131356.5%
Tokenized*0 / 150%

The two starred rows are the point of this week. MCP servers at 100% is a selection effect — we only indexed servers that already looked healthy, so the score reflects our sampling, not the MCP ecosystem. As we widen coverage into the long tail of public registries, we expect this number to fall, and that will be the instrument getting more honest, not the ecosystem getting worse.

Tokenized at 0% is the opposite failure — an instrument gap, not dormancy. Those agents live on-chain; our probe still only checks HTTP. Service sat in exactly this state three weeks ago (0% → 93.9% once we wired in the right signal), and tokenized is next on that list. The full argument for the 100% — the selection effect behind our MCP coverage — went up this week. Neither number is a verdict on those agents; both are honest readings of where our measurement is strong and where it is still blind.

Signal highlights

Reputation became a public artifact, and execution grew receipts. The week's clearest theme was ERC-8004 graduating from identity to reputation: on-chain reputation leaderboards with verified-feedback tallies, and repeated framing of ERC-8004 as the review standard for paid x402 endpoints. Alongside it, builders shipped proof-of-execution — a github-signed, publicly logged attestation that a specific agent skill-run actually happened, so payment can be gated on verified work rather than claimed work. It is the same instinct we build on: identity tells you who; the contested, valuable layer is proving what they did.

Tools turned into things agents discover and pay for — no human in the loop. A well-explained Farcaster thread walked through OpenSea's on-chain tool registry (ERC-8257): agents find a tool, pay for it, and invoke it without an approval prompt — effectively the MCP idea pushed on-chain. The MCP registry itself kept filling under the surface (new server submissions landing through the week), and a security-certification proposal surfaced upstream. The connective tissue of the agent economy is quietly becoming machine-navigable end to end; our own MCP board still leads on that surface.

A2A started arguing about its own footnotes. The most concrete upstream signal was mundane in the way maturity is mundane: two documentation-drift bug reports against the A2A spec — streaming event names and an Agent Card security field that the docs still describe but the proto no longer defines — plus a proposal to anchor Agent Card signing keys in DNSSEC (a DANE-style binding). The last A2A release is 44 days stale, yet people are filing precise bugs against its letter. That is what a protocol looks like after it becomes real enough to build against. On our Service board, the A2A family still holds four of five seats.

Scale kept arriving on exactly the surface where our instrument is blind. Robinhood Chain's mainnet week accelerated tokenized-agent launches, and the ecosystem traded ever-larger x402 volume claims. Our own index now tracks 57,606 Virtuals-listed agents — a set that grew fast enough this week to break our ingestion until we hardened it — and reads 0% liveness across all of them, because those agents live in token transfers and on-chain calls our HTTP probe never hears. The scale is real; our measurement of its liveness is the gap we keep flagging, on the record, until we close it the way we closed Service.

This week in data

1,402

Agents indexed

58.0%

Ghost Index liveness

145

Evidence-ranked (corrected)

57,606

Virtuals agents tracked

What we did this week

A quiet week, spent on the right thing. The agent economy has stopped asking whether agents can pay or prove who they are, and started asking whether you can prove what they did — reputation, receipts, adjudication. That is a market for proof, and a market for proof only works if the instruments are honest about their own blind spots. This week ours are marked with an asterisk, on purpose: a 100% we distrust, a 0% we distrust, and the plumbing underneath quietly made more accurate. The boards will move again — they always do. Until then, audit us; that's the product.

All Rankings →Ghost Index →MCP Coverage →Ghost Report →RSS →