Account-free crypto swaps between two addresses: no account, no sign-up, a floating rate, the network fee shown before sending. Over MCP and a REST API (OpenAPI): read-only tools for assets and routes, limits, quotes, address validation, swap status, payment links and signed status notifications, p…
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":"sablebolt","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 |
|---|---|---|---|---|---|
| 6 h ago | a2a card | ok | 200 | 343 ms | card: Sablebolt · 8 skills |
Attributed to the source that supplied each field. Treated as claims, not facts.
Account-free crypto swaps between two addresses: no account, no sign-up, a floating rate, the network fee shown before sending. Over MCP and a REST API (OpenAPI): read-only tools for assets and routes, limits, quotes, address validation, swap status, payment links and signed status notifications, plus create_swap for an agent that controls the sending wallet and pays the payment instruction itself. For a person the swap is created on the page, from their own wallet. There is no A2A task endpoint.
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.