Telegraph Protocol for Openclaw

Telegraph Protocol enables AI agents to query a decentralized marketplace for verifiable AI inference powered by transparent cryptographic micropayments.

0xwick
v1.1.0
Jul 8, 2026
0
452
0

Install & Download

1. ClawHub CLI

The fastest way to install a skill directly from the registry.

npx clawhub@latest install telegraph-dev

2. Manual Installation

Copy the skill folder to one of these locations

Global
~/.openclaw/skills/
Workspace
<project>/skills/

Priority: Workspace > Local > Bundled

3. Prompt Installation

Copy this prompt to OpenClaw to install it automatically.

Help me install telegraph-dev using Clawhub. If Clawhub is not installed, install it first (npm i -g clawhub).

Prefer to download?

Get the raw skill files in a ZIP archive.

What is Telegraph Protocol?

Telegraph is a decentralized, permissionless marketplace designed for verifiable AI inference. It allows developer agents to query diverse machine learning models, Bittensor subnets, and specialized APIs with built-in consensus and verification. By utilizing Openclaw Skills to connect to this decentralized infrastructure, agents can retrieve and pay for intelligence tasks dynamically.

The system utilizes a validator mesh that scores responses against ground truth via zkTLS and WASM, delivering cryptographically finalized answers. The payment mechanism is handled through the x402 HTTP-native micropayments protocol, executing automated transactions using Base Sepolia testnet USDC without exposing the agent directly to payment hurdles or private key exposures.

Telegraph Protocol Use Cases

  • Accessing verifiable weather forecasts or climate risk assessments.
  • Detecting deepfakes, AI-generated content, or verifying media authenticity.
  • Executing LLM completions, image generation, and text embeddings via decentralized networks.
  • Monitoring autonomous signal feeds across topics like politics, technology, climate, health, or geopolitics.
  • Automating pay-per-request intelligence tasks using micro-sized on-chain transactions.

How Telegraph Protocol Works

  1. The agent submits a query or specific intent (such as weather check or authenticity verification) to the local MCP server.
  2. For paid operations, the server intercepts the x402 micropayment challenge and handles the transaction authorization locally using a configured EVM burner wallet.
  3. The query is routed either automatically via the Engine's LLM router to the highest-ranked miner or directed manually to a specific miner ID.
  4. Decentralized validators assess the response's validity using zkTLS verification and WASM scoring scripts.
  5. A cryptographically finalized and verified response is delivered back to the agent for downstream utilization.

Telegraph Protocol Setup

To configure this capability, add the Telegraph MCP server to your local client configuration. On Openclaw Skills integrations, this configures the server locally and stays inactive until properly defined.

Configure the server by adding the following block to your configuration file (e.g., ~/.openclaw/openclaw.json or your Claude Desktop configuration):

{
  "mcpServers": {
    "telegraph": {
      "command": "npx",
      "args": ["-y", "telegraph-protocol-mcp"],
      "env": {
        "TELEGRAPH_NODE_URL": "http://13.237.89.59:7044",
        "TELEGRAPH_ENGINE_URL": "http://13.237.89.59:8080",
        "TELEGRAPH_DAEMON_URL": "http://13.237.89.59:8081",
        "TELEGRAPH_EVM_PRIVATE_KEY": "0xyour_burner_wallet_key"
      }
    }
  }
}

Ensure that your configured EVM burner wallet is funded with Base Sepolia USDC for paid inference queries. Never use a primary wallet.

Telegraph Protocol Data Schema & Taxonomy

The skill provides both free and paid tools depending on transaction requirements.

Free Tool Catalog

Tool Name Purpose
tg_node_list_subnets Retrieves the full miner catalog, including IDs, endpoints, and schemas
tg_node_subnets_health Checks the health status of active miner integrations
tg_node_status Returns node identity, public key, and chain details
tg_engine_list_subnets Lists available miners from the engine's perspective, highlighting capabilities and costs
tg_daemon_categories Lists signal categories available in the database (e.g., CLIMATE, POLITICS, TECHNOLOGY)
tg_daemon_questions Queries stored signals filtered by category, source, time, or interest
Tool Name Purpose
tg_engine_ask Submits a query for auto-routed inference to the optimal miner
tg_engine_ask_subnet Sends inference directly to a specific miner ID
Dynamic Tools Auto-generated tools per active miner (e.g., tg_zeus_predict, tg_bitmind_detect_image)

Telegraph Protocol Advanced Features

  • Dynamic tool generation: Automatically fetches the live integration registry every 5 minutes to generate new, per-miner tools without server restarts.
  • Autonomous signal daemon: Periodically processes, collects, and stores verified reports across multiple categories, providing free reading access to structured datasets.
  • Localized private key custody: Keeps the private key secured within the local runtime process environment, ensuring it is never shared with external models or remote endpoints.
  • Smart intent routing: Evaluates natural language queries to match against defined canonical intents, ensuring tasks are processed by the most capable miner.

SKILL.md


Loading

Related Openclaw Skills

METADATA

Github Stars: 0
forks: 0

Featured*