> ## Documentation Index
> Fetch the complete documentation index at: https://docs.atlasyield.club/llms.txt
> Use this file to discover all available pages before exploring further.

# Coverage

> What the Atlas index tracks today, and how coverage grows.

As of the **8 October 2026** snapshot, Atlas publishes scores for **535 vaults**
representing about **\$43.6B** in TVL, across **9 protocols** and **6 chains**. Execution
is supported on Ethereum, Base, Arbitrum, Optimism, BNB Chain and Polygon. Solana is
scored only (see below).

| Protocol | Scored vaults |
| - | - |
| Morpho | 197 |
| Aave v3 | 90 |
| Beefy | 85 |
| Yearn v3 | 54 |
| Pendle | 41 |
| Kamino | 36 |
| Euler | 29 |
| EtherFi | 2 |
| Ethena | 1 |

| Chain | Scored vaults |
| - | - |
| Ethereum | 324 |
| Base | 111 |
| Arbitrum | 37 |
| Solana | 36 |
| Optimism | 17 |
| BNB Chain | 10 |

Coverage is uneven by design. Most of the scored set sits in Morpho, Aave and Beefy, while
newer adapters contribute a thin tail. A vault only enters the scored set when its data
pipeline meets the quality bar described in [Reading a score](/score/reading-a-score) —
scores carry a `dataQuality` flag, and on this snapshot 524 were `sufficient`, 6 `partial`
and 5 `fallback`.

## Verify this yourself

These counts move daily as vaults cross the TVL floor or adapters change. Rather than trust
the numbers on this page, read the machine-readable snapshot:

```
https://raw.githubusercontent.com/gveshk/atlasyield-score-history/main/latest.json
```

Every scored vault, with its composite, pillar scores, APY, TVL and `dataQuality`, for the
current day. The [full history](/score/public-record) is committed daily to a public
repository.

The route-survival screen is published in the same commit:

```
https://raw.githubusercontent.com/gveshk/atlasyield-score-history/main/routes-latest.json
```

One row per screened vault with `verdict`, `reasonClass`, `path`, `usdIn`, `usdOut`,
`retained` and `checkedAt`, plus a `probe` block stating what was measured. Read that block
before quoting a count: the probe is **same-chain only** (USDC on the vault's own chain,
into the position, straight back), so a `NO_ROUTE` says nothing about bridging in from
another chain. `reasonClass` separates `protocol_refused` (the protocol's own router will
not quote the position; the vault is dead for entry or exit) from `no_aggregator_quote`
(no same-chain swap into the underlying, typical of LP-token vaults, which may still be
exitable by redeeming and unwinding by hand).

The admin-topology screen (who can change a vault, and how fast) is published in the same
commit too:

```
https://raw.githubusercontent.com/gveshk/atlasyield-score-history/main/admin-latest.json
```

One row per screened vault with `class`, `curatorId`, `curatorRating`, `timelockSeconds`, a
role summary (no addresses) and `checkedAt`. Aave, Pendle, EtherFi, Ethena and BNB vaults
are not screened. A vault controlled by a single key scores 40 on this factor if its curator
is rated established and 10 otherwise. On-chain DAO governance (a token-vote governor or Sky)
scores like a strong multisig, and an Aragon DAO like a weak one, since its voting plugin is not
inspected. A role's `delaySeconds` is the delay a timelock or supervisor adds in front of it.

## What is not covered

Named gaps, stated plainly because an undisclosed one is worse than a known one:

* **Spark** and **Sky** (including sUSDS) are not scored today.
* **Compound** is not scored today.
* On Solana, only **Kamino Earn vaults** are scored (added 24 September 2026, chain id
  `792703809`). Kamino Lend reserves, Jupiter Lend and PT markets on Solana venues are not.
  Solana vaults are scored only: Atlas has no Solana execution, so they never appear in a
  suggested portfolio. Solana addresses are case-sensitive; use the `onchainId` field, not
  the lowercased `vaultId`, to look one up on-chain.

## Programmatic access

The same scores that power the app are available via a
[read-only API](/api-reference/introduction) for teams that want to quote the Atlas Score
on their own earn surfaces. Scores refresh on a roughly four-hour pipeline; the public
snapshot is committed once a day.

Agents can reach the same data through the [MCP server](/api-reference/mcp), hosted at
`https://atlasyield.club/mcp` or run locally with `npx`. To ask what is covered right now
instead of reading this page, call `GET /v1/scores?fields=compact&limit=1` and read `total`,
or the `get_coverage` MCP tool.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.