Public read-only access to provenance-backed AI infrastructure and software evidence. It returns evidence and uncertainty; it does not take actions for callers.
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":"daystruct-daystruct-evidence-agent","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 |
|---|---|---|---|---|---|
| 55 min ago | a2a card | ok | 200 | 583 ms | card: Daystruct Evidence Agent · 2 skills |
| 8 h ago | a2a card | ok | 200 | 445 ms | card: Daystruct Evidence Agent · 2 skills |
| 14 h ago | a2a card | ok | 200 | 464 ms | card: Daystruct Evidence Agent · 2 skills |
| 21 h ago | a2a card | ok | 200 | 455 ms | card: Daystruct Evidence Agent · 2 skills |
| 28 h ago | a2a card | ok | 200 | 546 ms | card: Daystruct Evidence Agent · 2 skills |
| 34 h ago | a2a card | ok | 200 | 491 ms | card: Daystruct Evidence Agent · 2 skills |
| 2 d ago | a2a card | ok | 200 | 471 ms | card: Daystruct Evidence Agent · 2 skills |
| 2 d ago | a2a card | ok | 200 | 749 ms | card: Daystruct Evidence Agent · 2 skills |
| 2 d ago | a2a card | ok | 200 | 650 ms | card: Daystruct Evidence Agent · 2 skills |
| 3 d ago | a2a card | ok | 200 | 515 ms | card: Daystruct Evidence Agent · 2 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.