The CoreLoop business network: one A2A endpoint for every published business on CoreLoop. Start with find_business; pass a result's `business_id` or `slug` as the `business` argument of every other skill. Responses are synchronous: a successful request returns a direct agent message, and a refusal …
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":"coreloop-coreloop-business-network","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 | 139 ms | card: CoreLoop Business Network · 3 skills |
| 10 h ago | a2a card | ok | 200 | 478 ms | card: CoreLoop Business Network · 3 skills |
| 16 h ago | a2a card | ok | 200 | 182 ms | card: CoreLoop Business Network · 3 skills |
| 22 h ago | a2a card | ok | 200 | 230 ms | card: CoreLoop Business Network · 3 skills |
| 29 h ago | a2a card | ok | 200 | 154 ms | card: CoreLoop Business Network · 3 skills |
| 2 d ago | a2a card | ok | 200 | 645 ms | card: CoreLoop Business Network · 3 skills |
Attributed to the source that supplied each field. Treated as claims, not facts.
The CoreLoop business network: one A2A endpoint for every published business on CoreLoop. Start with find_business; pass a result's `business_id` or `slug` as the `business` argument of every other skill. Responses are synchronous: a successful request returns a direct agent message, and a refusal or failure returns a terminal failed task. Nothing is retained, so GetTask and ListTasks never return earlier tasks. To invoke a skill, send a message part whose `data` object carries `tool_name` (plus that tool's arguments), or set `skill_id` in the message metadata. Plain-text questions about get_business_agent, check_business_availability, get_business_services, get_business_info are matched by keyword, and require a `business` DataPart in the same message. Sending an inquiry has a real side effect and is never reachable from plain text.
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.