From an AI assistant a developer can read the live numbers for their own game (plays, players, how a new version landed) and ask why a game fails to start, getting the actual runtime errors from the preview rather than a guess. The production contract and a starter skeleton are available the same w…
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":"klyo-games-live-numbers-and-diagnostics-for-your","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.
Not distributed through a package registry we index.
| when | check | result | http | latency | detail |
|---|---|---|---|---|---|
| 6 d ago | mcp initialize | failed | 405 | 234 ms | http 405 |
| 13 d ago | mcp initialize | failed | 405 | 122 ms | http 405 |
| 20 d ago | mcp initialize | failed | 405 | 129 ms | http 405 |
| 27 d ago | mcp initialize | failed | 405 | 125 ms | http 405 |
| 1 mo ago | mcp initialize | failed | 405 | 137 ms | http 405 |
| 1 mo ago | mcp initialize | failed | 405 | 144 ms | http 405 |
| 1 mo ago | mcp initialize | failed | 405 | 543 ms | http 405 |
| 1 mo ago | mcp initialize | failed | 405 | 295 ms | http 405 |
| 1 mo ago | mcp initialize | failed | 405 | 116 ms | http 405 |
Attributed to the source that supplied each field. Treated as claims, not facts.
From an AI assistant a developer can read the live numbers for their own game (plays, players, how a new version landed) and ask why a game fails to start, getting the actual runtime errors from the preview rather than a guess. The production contract and a starter skeleton are available the same way, before a single line is written.
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.