Ground truth for AI coding agents: what breaks between library versions and how to fix it
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":"asynthetic","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.
No successful checks in the window.
| when | check | result | http | latency | detail |
|---|---|---|---|---|---|
| 2 d ago | mcp initialize | failed | 404 | 170 ms | http 404 |
| 2 d ago | http get | failed | 404 | 176 ms | http 404 application/json |
| 10 d ago | mcp initialize | failed | 404 | 171 ms | http 404 |
| 10 d ago | http get | failed | 404 | 204 ms | http 404 application/json |
| 17 d ago | mcp initialize | failed | 404 | 174 ms | http 404 |
| 17 d ago | http get | failed | 404 | 171 ms | http 404 application/json |
| 24 d ago | http get | failed | 404 | 173 ms | http 404 application/json |
| 24 d ago | mcp initialize | failed | 404 | 191 ms | http 404 |
| 1 mo ago | http get | failed | 404 | 170 ms | http 404 application/json |
| 1 mo ago | mcp initialize | failed | 404 | 206 ms | http 404 |
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.