M·O·R·S·E

Telegraph in Telegram. Ask, get an answer from a ranked miner, with a receipt.

No wallet, no key, no sign-up. Type a question, Telegraph's router sends it to the best-ranked miner for that intent, Morse pays the $0.01 fee, and the answer comes back naming who answered, what it cost, and a signal hash you can check on the node and on-chain.

Open @MyMorse_Bot in Telegram →or try it right here ↓

Ask it something yourself

Try one:
Recipes (one question, several intents):
92people answered
of 121 who asked
611answered calls
28intents used
76miners served
$6.11paid to the network
0calls today · 0 users
What can I ask? — one example per intent the network serves; click any to ask it

Security and infrastructure

Weather

Crypto and on-chain

Markets

Knowledge and news

Language and general

Questions people ask about Morse

What is this, in one sentence?

Telegraph, inside Telegram: dozens of independent "miners" (APIs and models) compete on a public leaderboard to answer questions, and Morse lets you ask them from a chat, without a wallet.

What can I ask?

Anything the network has a miner for: certificate and link safety checks, weather and storm risk, crypto and stock prices, wallet balances and fraud risk, fact checks, translations, news and papers, plus general questions. The list above has one example per intent.

Is it free? Who pays?

Free for you. Each answer costs about $0.01 in testnet USDC, which Morse's own wallet pays via x402. Limits: 20 questions per day on the web, 40 in Telegram, 100 per API key.

What is the receipt, and how do I verify it?

Every answer names the miner, its leaderboard rank, who routed the question, the miner's confidence, the cost, the on-chain settlement, and a signal hash. Click "verify" on any answer or ledger row: Morse fetches the node's own record for that hash, shows the wallet that paid and checks it is Morse's, and links the USDC transfer on BaseScan.

Is my question public?

Yes. The ledger below lists every call, and /api/recent returns the question clipped to 200 characters and the answer excerpt. Do not type anything private. Who asked is stored only as a salted hash.

Can I use it from code or an AI agent?

Yes: a hosted MCP server and a REST endpoint, no wallet needed. Get a free key.

Public ledger durable

The newest row, in full live, not a sample

“Is https://example.com safe to visit?”

Yes, the URL https://example.com is safe to visit. It answers with HTTP status 200 over valid HTTPS, with a risk score of 0.1 on a 0 (safe) to 1 (unsafe) scale.
Answered by
netwire-url-scan · ranked #1 for URL_SCAN
Routed by
Telegraph's own router
Confidence
90%
Cost
$0.01 · 84 ms · settled on Base Sepolia
Signal hash
0x0d0b2169e7244eec0f70405fc55809cbbde54d4877193a822f260e80e629745b — click to see the node's record and that Morse's wallet paid for it

The evidence behind the counters above: every call Morse has made, newest first, including the operator's own testing — nothing is separated out and nothing is manufactured. "Routed" says who chose the miner: Telegraph's router for a normal ask; Morse when you named the miner, or as a fallback when the router did not answer. Rows of kind podium and second-opinion are from two features removed on 4 September, after an organizer said that paying several miners per question to re-check the ranking is what the protocol already does once for everyone; they stay here because the ledger is not rewritten. Payer wallet: 0xfBB3C3bd51EC6E19BDECc786945d83719b6b4c9c. Cross-check any row at its verify link, or on the node with GET /engine/v1/signal/{hash}. JSON: /api/stats · /api/recent · /api/health. A check that does not rely on this table: on-chain proof matches every settlement hash here against the payer wallet's USDC transfers on Base Sepolia.

time (UTC)channelkindintentminerroutedconf.costmsstatusverify
2026-10-07 15:08:45ZtelegramaskURL_SCANnetwire-url-scan #1Telegraph90%$0.0184ok0x0d0b2169…
2026-10-07 15:08:42ZtelegramaskSSL_VERIFICATIONlivecert #1Telegraph100%$0.01815ok0xb26745a4…
2026-10-05 07:17:24Zwebask———n/r——error—
2026-10-05 07:17:19Zwebask———n/r——error—
2026-10-05 07:17:13Zwebask———n/r——error—
2026-10-05 07:15:57Zwebask———n/r——error—
2026-10-01 18:04:11ZwebaskCHAT_COMPLETIONchat-crossref #5Telegraphn/r$0.01795ok0xc216f553…
2026-09-25 12:23:37ZwebaskSSL_VERIFICATIONchainsight-oracle #4Telegraphn/r$0.01992ok0x50984392…
2026-09-25 11:32:33ZtelegramaskCHAT_COMPLETIONtelegraph-chatbot #4Telegraphn/r$0.012936ok0xe0863e16…
2026-09-25 11:31:51ZtelegramaskCHAT_COMPLETIONtelegraph-chatbot #4Telegraphn/r$0.013203ok0xe885cacb…
2026-09-25 11:31:40ZtelegramaskFACT_CHECKlivecert #3Telegraph70%$0.0125767ok0x33a0bd2d…
2026-09-23 16:41:12ZwebaskWEATHER_CHECKskywire-weather-check #2Telegraph96%$0.016733ok0x25b3699b…
2026-09-21 07:18:39ZwebaskCHAT_COMPLETIONgroq-llama31-instant-miner #1Morse (fallback)95%$0.01579ok0x89818410…
2026-09-19 04:27:59ZwebaskLANGUAGE_TRANSLATIONlivecert #1Telegraph0%$0.01253ok0x9aa7f425…
2026-09-16 19:34:10ZwebaskFACT_CHECKlivecert #11Morse (fallback)70%$0.011130ok0x739941d3…
2026-09-16 19:33:27ZwebaskCHAT_COMPLETIONtelegraph-chatbot #9Morse (fallback)n/r$0.013056ok0xdb17ced2…
2026-09-16 19:33:20ZwebaskWEATHER_CHECKwx-canada #13Telegraphn/r$0.01784ok0x3023f4bf…
2026-09-16 08:29:41ZwebaskCHAT_COMPLETIONbedrock-deepseek #4Telegraphn/r$0.011747ok0x0de44f0c…
2026-09-16 08:29:31ZwebaskCHAT_COMPLETIONbedrock-deepseek #4Telegraphn/r$0.017554ok0xca89a104…
2026-09-16 08:27:37ZwebaskLANGUAGE_TRANSLATIONlivecert #1Telegraph100%$0.01265ok0x2c1b2d45…
2026-09-16 08:26:51ZwebaskLANGUAGE_TRANSLATIONlivecert #1Telegraph0%$0.01496ok0xdf7823bd…
2026-09-16 08:26:24ZwebaskWEATHER_CHECKopenweathermap #2Telegraphn/r$0.01527ok0x40154a8c…
2026-09-16 08:25:53ZwebaskWEATHER_CHECKopenweathermap #2Telegraphn/r$0.011559ok0x2b59d8f2…
2026-09-15 15:51:16ZwebaskURL_SCANchainsight-oracle #4Morse (fallback)n/r——unpaid—
2026-09-15 15:51:16ZwebaskURL_SCANchainsight-oracle #4Morse (fallback)n/r——unpaid—

How routing works

Your question goes to Telegraph's own router (POST /engine/v1/ask), which classifies it into one of the network's 45 canonical intents with an LLM and picks a ranked miner — 70% of traffic goes to #1, 20% to #2, 10% to #3, re-ranked from validator scores every 9-hour epoch. If the router does not answer within 20 seconds (on 2 September it timed out at ~47 s for a day), Morse falls back to its own keyword classifier over the live leaderboard and calls the best-ranked miner directly. Every receipt says which of the two happened.

Not an aggregator, not a validator. Morse does not pick providers, does not blend answers and does not check one miner against another. Telegraph's leaderboard already decides which miner is best, once, for everyone; the router's pick is the answer. Morse pays the fee, shows the answer, and keeps the receipt where anyone can check it: every payment reconciled against the chain.

Disclosure: one miner the network often routes to, livecert, is operated by the same person who built Morse. It holds its ranks on the public leaderboard; Morse neither skips it nor favours it, and every ledger row names the miner it went to.

In Telegram: @MyMorse_Bot. For agents: hosted MCP and REST, no wallet needed. Source and honest limits: GitHub.