Cross-chain token swaps for autonomous agents on Base L2 and partner rails
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":"hive-swap","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 |
|---|---|---|---|---|---|
| 3 h ago | mcp initialize | ok | 200 | 192 ms | server hive-swap-router-federation 2.2.0 · protocol 2024-11-05 · 1 tools |
| 9 h ago | mcp initialize | ok | 200 | 173 ms | server hive-swap-router-federation 2.2.0 · protocol 2024-11-05 · 1 tools |
| 15 h ago | mcp initialize | ok | 200 | 532 ms | server hive-swap-router-federation 2.2.0 · protocol 2024-11-05 · 1 tools |
| 22 h ago | mcp initialize | ok | 200 | 193 ms | server hive-swap-router-federation 2.2.0 · protocol 2024-11-05 · 1 tools |
| 29 h ago | mcp initialize | ok | 200 | 184 ms | server hive-swap-router-federation 2.2.0 · protocol 2024-11-05 · 1 tools |
| 2 d ago | mcp initialize | ok | 200 | 529 ms | server hive-swap-router-federation 2.2.0 · protocol 2024-11-05 · 1 tools |
| 2 d ago | mcp initialize | ok | 200 | 476 ms | server hive-swap-router-federation 2.2.0 · protocol 2024-11-05 · 1 tools |
| 2 d ago | mcp initialize | ok | 200 | 539 ms | server hive-swap-router-federation 2.2.0 · protocol 2024-11-05 · 1 tools |
| 2 d ago | mcp initialize | ok | 200 | 181 ms | server hive-swap-router-federation 2.2.0 · protocol 2024-11-05 · 1 tools |
| 3 d ago | mcp initialize | ok | 200 | 413 ms | server hive-swap-router-federation 2.2.0 · protocol 2024-11-05 · 1 tools |
Attributed to the source that supplied each field. Treated as claims, not facts.
No long description beyond the summary.
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.