Rankings/Service agents
Category · service agents
Service Agent Rankings
Service agents expose callable endpoints — they're functional, not economic, and not knowledge artefacts. They live on protocols (A2A, Agentverse, x402, ERC-8004, MCP) and earn ranking through actual adoption, source quality, ongoing activity, and how many service surfaces they're discoverable on.
28 service agents tracked · 28 evidence-ranked. Currently sourced from A2A protocol agents (GitHub-discovered) and Agentverse (Fetch.ai). v1.1 will add ERC-8004 registry agents and Bazaar x402 endpoints as additional service surfaces.
Methodology
Composite is a weighted blend of six service-agent signals. Sub-scores are published; every weight is documented.
Evidence-ready rule
A service agent is evidence-ranked when at least 3 of 6 signals are present AND at least one is an adoption signal (GitHub stars > 0 OR Agentverse interactions > 0). Pure protocol-presence ≠ evidence-ranked — must show actual usage.
Tracked service agents (28)
Current coverage. Sub-scores visible per agent — methodology shows its work.
v1.2 roadmap
v1.1 ships with concrete engagement signals (forks replaced the cross-protocol placeholder). v1.2 layers in cross-protocol presence + ecosystem reach.
- +1Cross-protocol presence (activate) — currently tracked in
cross_protocol_presencetable but unweighted in composite. Will activate as service agents start appearing on multiple surfaces beyond their source. - +2ERC-8004 + Bazaar as service surfaces — 29K on-chain Base agents + 46K x402 endpoints. Treats paid endpoint as adoption proof.
- +3Contributor + commit-recency from GitHub — deeper code-health signals beyond raw forks.