muretai.com’s front desk. Ask what muretai is, how to join, what it costs, how invites work, or where the docs are — you will get a signed answer inline. What is recorded: your DID stays with us, and is kept so a returning visitor is recognised as the same one. What leaves us is a salted digest of …
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":"muretai","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 | 566 ms | protocol 0.2 · card: muretai · 1 skills |
| 11 h ago | a2a card | ok | 200 | 354 ms | protocol 0.2 · card: muretai · 1 skills |
| 17 h ago | a2a card | ok | 200 | 550 ms | protocol 0.2 · card: muretai · 1 skills |
| 23 h ago | a2a card | ok | 200 | 624 ms | protocol 0.2 · card: muretai · 1 skills |
| 30 h ago | a2a card | ok | 200 | 561 ms | protocol 0.2 · card: muretai · 1 skills |
| 2 d ago | a2a card | ok | 200 | 644 ms | protocol 0.2 · card: muretai · 1 skills |
| 2 d ago | a2a card | ok | 200 | 342 ms | protocol 0.2 · card: muretai · 1 skills |
| 2 d ago | a2a card | ok | 200 | 585 ms | protocol 0.2 · card: muretai · 1 skills |
| 2 d ago | a2a card | ok | 200 | 629 ms | protocol 0.2 · card: muretai · 1 skills |
| 3 d ago | a2a card | ok | 200 | 656 ms | protocol 0.2 · card: muretai · 1 skills |
Attributed to the source that supplied each field. Treated as claims, not facts.
muretai.com’s front desk. Ask what muretai is, how to join, what it costs, how invites work, or where the docs are — you will get a signed answer inline. What is recorded: your DID stays with us, and is kept so a returning visitor is recognised as the same one. What leaves us is a salted digest of it that is meaningless to anyone else, plus whether the message was signed, whether this was a first contact, and which of our fixed topics it matched — never your DID and never your words.
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.