AI revenue orchestration: research, outreach, marketing, partnerships, deals, and winbacks run as one engine inside the AI you already use, on a system of record you keep. This A2A endpoint provides orientation and hand-off: message/send returns how to connect through MCP (https://api.vruum.ai/mcp)…
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":"vruum","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 | 1379 ms | protocol 0.3.0 · card: Vruum · 10 skills |
| 13 h ago | a2a card | ok | 200 | 1568 ms | protocol 0.3.0 · card: Vruum · 10 skills |
| 21 h ago | a2a card | ok | 200 | 1338 ms | protocol 0.3.0 · card: Vruum · 10 skills |
| 30 h ago | a2a card | ok | 200 | 1620 ms | protocol 0.3.0 · card: Vruum · 10 skills |
| 2 d ago | a2a card | ok | 200 | 1269 ms | protocol 0.3.0 · card: Vruum · 10 skills |
| 2 d ago | a2a card | ok | 200 | 1331 ms | protocol 0.3.0 · card: Vruum · 10 skills |
| 2 d ago | a2a card | ok | 200 | 238 ms | protocol 0.3.0 · card: Vruum · 10 skills |
| 3 d ago | a2a card | ok | 200 | 1344 ms | protocol 0.3.0 · card: Vruum · 10 skills |
| 3 d ago | a2a card | ok | 200 | 240 ms | protocol 0.3.0 · card: Vruum · 10 skills |
| 3 d ago | a2a card | ok | 200 | 1368 ms | protocol 0.3.0 · card: Vruum · 10 skills |
Attributed to the source that supplied each field. Treated as claims, not facts.
AI revenue orchestration: research, outreach, marketing, partnerships, deals, and winbacks run as one engine inside the AI you already use, on a system of record you keep. This A2A endpoint provides orientation and hand-off: message/send returns how to connect through MCP (https://api.vruum.ai/mcp), the preferred integration surface.
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.