AffixIO verification software for configured eligibility, source and permission checks. Proof and attestation guarantees depend on the selected mode. Public references are open; protected API operations require credentials. Optional public shopping observations use a separate HTTPS JSON endpoint, n…
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":"affixio-affixio","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 |
|---|---|---|---|---|---|
| 2 h ago | a2a card | ok | 200 | 16 ms | card: AffixIO · 2 skills |
| 9 h ago | a2a card | ok | 200 | 68 ms | card: AffixIO · 2 skills |
| 15 h ago | a2a card | ok | 200 | 23 ms | card: AffixIO · 2 skills |
| 22 h ago | a2a card | ok | 200 | 13 ms | card: AffixIO · 2 skills |
| 29 h ago | a2a card | ok | 200 | 65 ms | card: AffixIO · 2 skills |
| 35 h ago | a2a card | ok | 200 | 36 ms | card: AffixIO · 2 skills |
| 2 d ago | a2a card | ok | 200 | 14 ms | card: AffixIO · 2 skills |
| 2 d ago | a2a card | ok | 200 | 15 ms | card: AffixIO · 2 skills |
| 2 d ago | a2a card | ok | 200 | 14 ms | card: AffixIO · 2 skills |
| 3 d ago | a2a card | ok | 200 | 14 ms | card: AffixIO · 2 skills |
Attributed to the source that supplied each field. Treated as claims, not facts.
AffixIO verification software for configured eligibility, source and permission checks. Proof and attestation guarantees depend on the selected mode. Public references are open; protected API operations require credentials. Optional public shopping observations use a separate HTTPS JSON endpoint, not A2A RPC.
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.