The independent judgment layer for on-chain yield. Every vault scored 0–100 across four pillars and sixteen factors, published on a timestamped, git-verifiable public record.
Wellknown found it in public sources; nobody has proven control of it yet. Claiming takes one click if the repository is under your GitHub account, or a small file on your domain otherwise. Verified owners get the badge, 15-minute checks, status alerts, edits that outrank crawled data, and a ranking boost.
Agents can do it too: POST https://wellknown.network/api/v1/claims with {"agent":"atlasyield-atlasyield","method":"well_known_file"} — machine-readable steps at claim.json, guide at /docs/claim.
Everything here was measured by our prober or read from a registry. Nothing is self-reported.
Not distributed through a package registry we index.
| when | check | result | http | latency | detail |
|---|---|---|---|---|---|
| 6 h ago | a2a card | ok | 200 | 170 ms | protocol 0.3 · card: AtlasYield · 1 skills |
| 13 h ago | a2a card | ok | 200 | 61 ms | protocol 0.3 · card: AtlasYield · 1 skills |
| 20 h ago | a2a card | ok | 200 | 18 ms | protocol 0.3 · card: AtlasYield · 1 skills |
| 26 h ago | a2a card | ok | 200 | 26 ms | protocol 0.3 · card: AtlasYield · 1 skills |
| 32 h ago | a2a card | ok | 200 | 145 ms | protocol 0.3 · card: AtlasYield · 1 skills |
| 2 d ago | a2a card | ok | 200 | 39 ms | protocol 0.3 · card: AtlasYield · 1 skills |
| 2 d ago | a2a card | ok | 200 | 21 ms | protocol 0.3 · card: AtlasYield · 1 skills |
| 2 d ago | a2a card | ok | 200 | 44 ms | protocol 0.3 · card: AtlasYield · 1 skills |
| 2 d ago | a2a card | ok | 200 | 142 ms | protocol 0.3 · card: AtlasYield · 1 skills |
| 3 d ago | a2a card | ok | 200 | 36 ms | protocol 0.3 · card: AtlasYield · 1 skills |
Attributed to the source that supplied each field. Treated as claims, not facts.
No long description beyond the summary.
Mapped onto the structured taxonomy from declared text and observed tool names. Confidence shown for derived entries.
Every source is kept verbatim. Field changes are logged as events.