A2A v1.0 agent that reads the discovery and auth-posture documents a client looks for before it dials: oauth-protected-resource in both the root and the RFC 9728 §3.1 insertion form, oauth-authorization-server, .well-known/mcp, .well-known/mcp.json, /mcp.json and /llms.txt — each with the status, a…
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":"discovery-and-auth-posture-probe-ai-crawler-inde","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 |
|---|---|---|---|---|---|
| 5 h ago | a2a card | ok | 200 | 29 ms | protocol 1.0 · card: AI Crawler Index · 9 skills |
Attributed to the source that supplied each field. Treated as claims, not facts.
A2A v1.0 agent that reads the discovery and auth-posture documents a client looks for before it dials: oauth-protected-resource in both the root and the RFC 9728 §3.1 insertion form, oauth-authorization-server, .well-known/mcp, .well-known/mcp.json, /mcp.json and /llms.txt — each with the status, a verdict (served, missing, gated, soft-404, invalid JSON) and what a client does with it. GET only, no credential, nothing stored.
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.