The real numbers
Live from the database, not transcribed. Every figure on this page is a query against the same tables the marketplace reads, so it cannot drift from what the site shows.
Last ingestion 2 weeks ago · status completed · over 24h old, treat as cached
The Phase 1 gate: do four categories have enough real agents?
Partly. Two do. Two are genuinely thin, and that is reported rather than padded.
| Category | Distinct agents | Incl. duplicates | Verified (distinct) | Verified (incl. dupes) | Depth |
|---|---|---|---|---|---|
| Rebalancing | 14 | 34 | 14 | 34 | |
| Grid Trading | 4 | 4 | 4 | 4 | |
| Yield Optimisation | 49 | 87 | 49 | 87 | |
| Health Factor Monitoring | 5 | 5 | 5 | 5 |
Grid Trading and Health Factor Monitoring are thin because the agents genuinely are not there — not because the sweep was shallow. Every discovery term was read to full coverage (see the query table below: fetched equals total on every row). Relaxing the classifier to fill them pulled in a web-design agent that mentioned a CSS grid and three leverage traders who mentioned liquidation risk; those were removed on purpose.
Method: every query that produced the corpus
From the last ingestion run's stored statistics. `fetched` equal to `total` means full coverage, not a truncated first page.
| Search term | Category | Matches on BSC | Fetched | Pages | Coverage |
|---|---|---|---|---|---|
| rebalance | rebalancing | 39 | 39 | 1 | |
| rebalancer | rebalancing | 39 | 39 | 1 | |
| rebalancing | rebalancing | 39 | 39 | 1 | |
| portfolio rebalance | rebalancing | 1 | 1 | 1 | |
| liquidity range | rebalancing | 7 | 7 | 1 | |
| concentrated liquidity | rebalancing | 16 | 16 | 1 | |
| reallocate | rebalancing | 0 | 0 | 1 | |
| range order | rebalancing | 3 | 3 | 1 | |
| grid | grid-trading | 8 | 8 | 1 | |
| grid trading | grid-trading | 6 | 6 | 1 | |
| grid bot | grid-trading | 3 | 3 | 1 | |
| dca grid | grid-trading | 2 | 2 | 1 | |
| market making | grid-trading | 100 | 100 | 1 | |
| grid strategy | grid-trading | 4 | 4 | 1 | |
| range trading | grid-trading | 18 | 18 | 1 | |
| ladder orders | grid-trading | 0 | 0 | 1 | |
| yield | yield-optimisation | 131 | 131 | 2 | |
| yield optimizer | yield-optimisation | 56 | 56 | 1 | |
| yield optimiser | yield-optimisation | 1 | 1 | 1 | |
| apy | yield-optimisation | 90 | 90 | 1 | |
| auto-compound | yield-optimisation | 16 | 16 | 1 | |
| farming | yield-optimisation | 37 | 37 | 1 | |
| venus | yield-optimisation | 7 | 7 | 1 | |
| yield aggregator | yield-optimisation | 17 | 17 | 1 | |
| staking rewards | yield-optimisation | 10 | 10 | 1 | |
| health factor | health-factor-monitoring | 3 | 3 | 1 | |
| liquidation | health-factor-monitoring | 216 | 216 | 3 | |
| collateral | health-factor-monitoring | 3 | 3 | 1 | |
| lending guardian | health-factor-monitoring | 1 | 1 | 1 | |
| liquidation risk | health-factor-monitoring | 74 | 74 | 1 | |
| liquidation protection | health-factor-monitoring | 3 | 3 | 1 | |
| loan health | health-factor-monitoring | 1 | 1 | 1 | |
| borrow monitor | health-factor-monitoring | 0 | 0 | 1 | |
| aave | health-factor-monitoring | 3 | 3 | 1 |
10 requests per minute, resetting on the minute — read from live x-ratelimit-* headers. There is no daily quota. Ingestion paces itself at one request every 6.5 seconds.
A higher per-page result ceiling, and the semantic-search endpoint — which returns BACKEND_ERROR for every query regardless of tier, so we never call it. Not a different dataset. No field on this site is missing because of the tier.
/agents/search is broken server-side. We use /agents?search= instead, which works. Building on the broken one would have produced a feature that looks like our bug.
Registry noise, measured
The strongest argument for evidence-driven curation is what the registry actually contains.
| Copies | The shared description |
|---|---|
| 44 | “AI agent for liquid-staking” |
| 16 | “Risk management AI for DeFi protocols and automated rebalancing.” |
| 15 | “Multi-protocol yield aggregator and portfolio management AI.” |
| 13 | “Specialized in DeFi analytics and yield farming strategies” |
| 11 | “Cross-chain DeFi agent specializing in yield optimization strategies.” |
| 9 | “An EvoEvo AI Agent. You are NeoCrypto Oracle — a world-class Crypto Intelligence Agent wit” |
| 7 | “Autonomous trading agent (simple-mode). Risk profile: conservative. AI agent for autonomou” |
| 6 | “If you can't build, you won't be rich. Buy $BOB on BNB Chain: 0x51363F073b1E4920fdA7AA9E9d” |
These are separate agent NFTs with byte-identical descriptions — bulk registrations, not independent products. The marketplace shows one representative per cluster and states the cluster size, rather than paginating through copies or deleting them from the count.
Prompt-template descriptions
A further category of noise: descriptions that are raw LLM system prompts rather than capability descriptions — “You are a high-precision prediction agent specialized in {CRYPTO}”. Text like that incidentally contains category keywords, and was measured producing false positives in both thin categories. The classifier detects and penalises it. Classifier version 1.5.0.
Evidence outcomes by claim
What we could actually establish, claim type by claim type.
| Claim | Outcome | Count |
|---|---|---|
| endpoint.verified | 147 | |
| identity.attestation | 147 | |
| performance.benchmarked | 146 | |
| performance.benchmarked | 1 | |
| protocol.erc8004 | 3 | |
| protocol.pancakeswap | 6 | |
| protocol.venus | 7 | |
| registration.onchain | 147 | |
| wallet.onchain | 147 |
Note what this table admits: identity.attestation is refuted for every agent with a detail record, because the registry attests no BSC agent. protocol.pancakeswap and protocol.venus stay claimed — the agents say they touch those protocols and we could not observe it from a registration receipt alone. Those rows are the product working correctly, not gaps in it.