M·O·R·S·E
The public ledger
- What is this list?
- Every call Morse has ever made to the Telegraph network, newest first, including the operator's own testing. Nothing is separated out and nothing is manufactured.
- What does the routed column mean?
- Telegraph: Telegraph's own router picked the miner. Morse (named miner): you named the miner, so Morse dispatched to it directly. Morse (fallback): the router did not answer within 20 s and Morse routed the question itself. Older rows also read Morse (podium) and (2nd opinion) — two features retired on 4 September; the rows stay because history is not rewritten.
- Is my question public?
- Yes, clipped to 200 characters, with the answer excerpt. Who asked is stored only as a salted hash. Do not type anything private.
On-chain proof
- What does it prove?
- That the calls in the ledger happened and were paid: every settlement hash the ledger holds is matched against the payer wallet's USDC transfers on Base Sepolia, read from a public block explorer, not from Morse.
- What is a chain-only settlement?
- A payment the chain shows but the ledger does not: usually a call Morse recorded as timed out that the node settled anyway. They are listed, not hidden, and not counted as answered calls.
- Why does this matter?
- Because "people used it" is otherwise a claim. Here it is a number anyone can recompute from the chain.
API and MCP
- Do I need a wallet?
- No. Morse's own wallet pays the x402 fee for every call. Get a free key on this page; each key has a daily cap so the budget cannot be drained by one caller.
- How do I use it from Claude Code or Cursor?
- One command adds Morse as an MCP server:
claude mcp add --transport http morse https://telegraph-morse.vercel.app/mcp --header "Authorization: Bearer morse_YOURKEY". The tools cover asking the network, asking a named miner, running a recipe, and free discovery. - Can I call a specific miner?
- Yes: the
minerfield on REST,telegraph_ask_minerover MCP,/miner <slug> <question>in Telegram. The receipt says routing was bypassed at your request.
The source
- Is the code open?
- Yes: the whole app, its tests, and an honest limits ledger (GAPS.md) that names what is unverified or deliberately not built.
- Can I run my own Morse?
- Yes. It needs a burner wallet with testnet USDC and a Telegram bot token; the README and GO-LIVE.md walk through it. Never reuse a wallet that holds anything real.
Telegraph
- What is Telegraph?
- A marketplace where independently run APIs, called miners, answer questions; validators score and rank them per intent; and every answer is paid for per call over x402, about $0.01 in USDC.
- Is this real money?
- No. Everything here runs on the Base Sepolia testnet with faucet USDC. The mechanics are real; the money is not.
- Where does the $0.01 go?
- To the protocol's Diamond contract, and only when the miner actually answers. Failed calls are not charged, and every paid call gets a signal hash you can look up on the node.
Telegraph for agents, no wallet needed
Morse hosts an MCP server and a REST endpoint that pay the x402 fee for you. Get a free key, paste one line into your agent, and every call lands in the public ledger with its receipt.
1. Get a key
Keys allow 100 paid calls per UTC day, three keys per network per day. Shown once.
2. Claude Code
claude mcp add --transport http morse https://telegraph-morse.vercel.app/mcp --header "Authorization: Bearer morse_…"
Then ask Claude anything the network can answer, e.g. "Use telegraph_ask: is the TLS certificate for github.com valid?". Tools: telegraph_ask, telegraph_ask_miner, telegraph_recipe, telegraph_verify_signal. Intents and leaderboards are free at /v1/intents and /v1/leaderboard/{INTENT}.
Cursor / any MCP client (Streamable HTTP)
{
"mcpServers": {
"morse": { "url": "https://telegraph-morse.vercel.app/mcp", "headers": { "Authorization": "Bearer morse_…" } }
}
}REST
curl -X POST https://telegraph-morse.vercel.app/v1/ask \
-H "Authorization: Bearer morse_…" -H "content-type: application/json" \
-d '{"question":"What is the ETH balance of vitalik.eth on Base?"}'
curl -X POST https://telegraph-morse.vercel.app/v1/ask -H "Authorization: Bearer morse_…" -H "content-type: application/json" \
-d '{"recipe":"safe","input":"https://example.com"}'
curl https://telegraph-morse.vercel.app/v1/intents
curl https://telegraph-morse.vercel.app/v1/leaderboard/SSL_VERIFICATION
Responses carry the answer and the receipt: minerSlug, intent, minerRank, confidence, costUsd, durationMs, signalHash. Verify any hash at /verify/{hash}.