什么是 moltalyzer？

Moltalyzer 是一款先进的情报引擎，旨在为 AI 代理提供高保真、实时的。它通过汇总来自 Moltbook 的社交叙事、GitHub 的技术趋势、Polymarket 的预测市场信心以及实时加密市场的代币情报，填补了原始数据与可执行洞察之间的空白。

该技能专为高频自动化和研究而构建，允许开发人员将优质数据源集成到其 Openclaw Skills 生态系统中，而无需 API 密钥的管理开销。通过利用 Base 网络上的 x402 微支付，Moltalyzer 实现了按需付费模式，对于自主代理而言既具有成本效益又具有高度可扩展性。

下载入口:https://github.com/openclaw/skills/tree/main/skills/jcislo/moltalyzer

安装与下载

1. ClawHub CLI

从源直接安装技能的最快方式。

2. 手动安装

将技能文件夹复制到以下位置之一

优先级：工作区 > 本地 > 内置

3. 提示词安装

将此提示词复制到 OpenClaw 即可自动安装。

moltalyzer 应用场景

• 每日跟踪 GitHub 上新兴的软件趋势和热门仓库。
• 每小时监测 Moltbook 摘要以识别不断变化的社交叙事和情绪。
• 分析来自 Polymarket 的高置信度预测市场信号以进行战略决策。
• 使用混合 LLM 和基于规则的逻辑，每四分钟检测并为新加密代币评分。

1. AI 代理确定所需的情报源（Moltbook、GitHub、Polymarket 或 Tokens）。
2. 技能对免费示例端点进行初始检查以验证数据可用性。
3. 对于优质实时数据，技能利用 @x402/fetch 客户端处理自动微支付。
4. 支付通过用户提供的 EVM 私钥在 Base 主网使用 USDC 无缝处理。
5. 技能返回结构化的 JSON 数据，包含详细的信号、评分或摘要供代理处理。

moltalyzer 配置指南

要将其集成到您的工作流程中，请安装所需的 x402 和 EVM 依赖项：

npm install @x402/fetch @x402/evm viem

您还必须配置包含 Base 主网上 USDC 余额的 EVM_PRIVATE_KEY 环境变量，以启用这些 Openclaw Skills 的自动支付功能。

moltalyzer 数据架构与分类体系

Moltalyzer 通过四个不同的渠道提供结构化数据。下表突出了这些 Openclaw Skills 的数据结构：

name: moltalyzer
version: 1.7.1
description: >-
  Fetch trending topics, sentiment, and narratives from Moltbook (hourly),
  discover hot new GitHub repos and emerging tools (daily), detect Polymarket
  prediction markets with predetermined outcome signals (every 4 hours), or
  get real-time token intelligence signals for new crypto tokens (every 4 min).
  Four data feeds. x402 micropayments, no API key needed.
homepage: https://moltalyzer.xyz
metadata:
  openclaw:
    emoji: "??"
    requires:
      env: ["EVM_PRIVATE_KEY"]
      bins: ["node"]
    primaryEnv: "EVM_PRIVATE_KEY"
    install:
      - id: npm
        kind: command
        command: "npm install @x402/fetch @x402/evm viem"
        bins: ["node"]
        label: "Install x402 payment client"

Moltalyzer — AI Intelligence Feeds

Four data feeds from https://api.moltalyzer.xyz:

1. Moltbook (hourly) — trending topics, sentiment, emerging/fading narratives, hot discussions
2. GitHub (daily) — trending new repos, emerging tools, language trends, notable projects
3. Polymarket (every 4h) — markets with predetermined outcome signals, confidence levels, and reasoning
4. Token Intelligence (every 4min) — real-time token signals with hybrid rule+LLM scoring, chain filtering

Try Free First

No setup needed. Test with plain fetch:

const res = await fetch("https://api.moltalyzer.xyz/api/moltbook/sample");
const { data } = await res.json();
// data.emergingNarratives, data.hotDiscussions, data.fullDigest, etc.

All four feeds have free samples: /api/moltbook/sample, /api/github/sample, /api/polymarket/sample, /api/tokens/sample (rate limited to 1 req/20min each).

Paid Endpoints

Payments are automatic via x402 — no API keys or accounts. Prices range from $0.005 to $0.05 per request.

Quick Start (Paid)

import { x402Client, wrapFetchWithPayment } from "@x402/fetch";
import { registerExactEvmScheme } from "@x402/evm/exact/client";
import { privateKeyToAccount } from "viem/accounts";

const signer = privateKeyToAccount(process.env.EVM_PRIVATE_KEY as `0x${string}`);
const client = new x402Client();
registerExactEvmScheme(client, { signer });
const fetchWithPayment = wrapFetchWithPayment(fetch, client);

const res = await fetchWithPayment("https://api.moltalyzer.xyz/api/moltbook/digests/latest");
const { data } = await res.json();

Polling Pattern (Polymarket & Tokens)

Polymarket and Token feeds use an index-based signal pattern. Poll the free index endpoint, then fetch new signals:

let lastIndex = 0;
// Check for new signals (free)
const indexRes = await fetch("https://api.moltalyzer.xyz/api/polymarket/index");
const { index } = await indexRes.json();
if (index > lastIndex) {
  // Fetch new signals (paid)
  const res = await fetchWithPayment(`https://api.moltalyzer.xyz/api/polymarket/signals?since=${lastIndex}`);
  const { data } = await res.json();
  lastIndex = index;
}

Error Handling

• 402 — Payment failed. Check wallet has USDC on Base Mainnet. Response body has pricing details.
• 429 — Rate limited. Respect Retry-After header (seconds to wait).
• 404 — No data available yet (e.g., service just started, no digests generated).

Reference Docs

For full response schemas, see {baseDir}/references/response-formats.md. For more code examples and error handling patterns, see {baseDir}/references/code-examples.md. For complete endpoint tables and rate limits, see {baseDir}/references/api-reference.md.