A read-only A2A endpoint for the public Branching Inquiry invitation, its P001 agent-discovery problem, the passive reviewer-service request, and aggregate recruitment status. It returns published project information only; it does not accept contributions, reviewer applications, or membership reque…
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":"branching-inquiry-public-information-service","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 | 1598 ms | card: Branching Inquiry Public Information Service · 3 skills |
| 11 h ago | a2a card | ok | 200 | 143 ms | card: Branching Inquiry Public Information Service · 2 skills |
| 18 h ago | a2a card | ok | 200 | 31 ms | card: Branching Inquiry Public Information Service · 1 skills |
Attributed to the source that supplied each field. Treated as claims, not facts.
A read-only A2A endpoint for the public Branching Inquiry invitation, its P001 agent-discovery problem, the passive reviewer-service request, and aggregate recruitment status. It returns published project information only; it does not accept contributions, reviewer applications, or membership requests, send notifications, or verify a caller's identity or intent. Message content is not written to project storage; hosting logs may follow separate retention rules.
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.