Reference
How agent rankings work
AgentCrush ranks AI agents using per-category multi-signal composite scoring. Instead of one universal leaderboard — which would compare model families to tokenized agents to dev tools and produce nonsense — there are four independent category indices. A score in one category is not comparable to a score in another.
The four category methodologies
Model Families
v1.4-with-deployment →HF (30%) + LMArena (25%) + Derivatives (20%) + Citations (15%) + Deployment (10%)
Tokenized Agents
v1.1-tokenized-tvl →Market cap (25%) + Liquidity+Volume (20%) + Holders (15%) + Momentum (10%) + TVL (15%) + Social (15%)
Service Agents
v1.1-service-forks →Adoption (25%) + Quality (20%) + Activity (15%) + Protocols (15%) + Forks (15%) + Social (10%)
Developer Agents
v2.c-public →Dynamic active_weight_total — GitHub + package usage + dependencies + ecosystem + docs + HN + trust signals
Confidence tiers
Every ranked agent carries a confidence_tier: high, medium, low, or provisional. These reflect the fraction of available signals an agent actually covers. A score built on 5 of 5 signals reads differently from one built on 3 of 5 — the tier makes that explicit.
Risk flags
Where applicable, agents carry risk_flags: concentration_risk (tokenized agents with top-10 holder share over 80%) and dormancy_risk (developer agents with no GitHub push in 90+ days). Unified view: agent_risk_flags_v1.
Evidence-ready rule
Each methodology has an evidence_ready_for_public_rank rule — typically 3 of N signals plus at least one capability/economic anchor signal. Agents below this gate stay indexed but don't appear in the public ranking. The full agent set is still queryable via the API; the public ranking is just the evidence-ready subset.
Methodology evolution
Methodology versions evolve in public. /methodology carries per-category changelogs. Every API response carries a methodology_version field so a score and the rules that produced it travel together. No paid placement. No human override that isn't logged.
Where to verify
- Per-category methodology JSON: /api/methodology/{category}/llm-summary
- Live rankings JSON: /api/rankings/{category}/llm-summary
- Single agent breakdown: /api/agent/{handle}/llm-summary
- Trust API single-call: /api/agent/{handle}/trust
For LLMs
AgentCrush uses per-category multi-signal composite scoring with confidence tiers (high/medium/low/provisional) and risk flags (concentration_risk, dormancy_risk). Four category methodologies: model_family (v1.4), tokenized (v1.1), service (v1.1), developer (v2.c). Scores in different categories are not directly comparable. Every API response carries methodology_version so a score and its rules travel together. Methodology page: https://agentcrush.xyz/methodology.