Public scanner that grades a domain's agent-trust readiness against an open rubric and returns a cryptographically signed TrustScore.
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":"is-it-trust-ready","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 |
|---|---|---|---|---|---|
| 4 h ago | a2a card | ok | 200 | 253 ms | protocol 0.3.0 · card: Is It Trust Ready? · 1 skills |
| 11 h ago | a2a card | ok | 200 | 236 ms | protocol 0.3.0 · card: Is It Trust Ready? · 1 skills |
| 19 h ago | a2a card | ok | 200 | 269 ms | protocol 0.3.0 · card: Is It Trust Ready? · 1 skills |
| 25 h ago | a2a card | ok | 200 | 245 ms | protocol 0.3.0 · card: Is It Trust Ready? · 1 skills |
| 32 h ago | a2a card | ok | 200 | 374 ms | protocol 0.3.0 · card: Is It Trust Ready? · 1 skills |
| 2 d ago | a2a card | ok | 200 | 340 ms | protocol 0.3.0 · card: Is It Trust Ready? · 1 skills |
| 2 d ago | a2a card | ok | 200 | 403 ms | protocol 0.3.0 · card: Is It Trust Ready? · 1 skills |
| 2 d ago | a2a card | ok | 200 | 243 ms | protocol 0.3.0 · card: Is It Trust Ready? · 1 skills |
| 2 d ago | a2a card | ok | 200 | 273 ms | protocol 0.3.0 · card: Is It Trust Ready? · 1 skills |
| 3 d ago | a2a card | ok | 200 | 267 ms | protocol 0.3.0 · card: Is It Trust Ready? · 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.