← Back to Skills Marketplace
wjw12

Heurist Mesh Crypto Analysis Skill

by JW · GitHub ↗ · v1.0.3
cross-platform ⚠ suspicious
2593
Downloads
10
Stars
3
Active Installs
4
Versions
Install in OpenClaw
/install heurist-mesh
Description
Real-time crypto token data, DeFi analytics, blockchain data, Twitter/X social intelligence, enhanced web search, crypto project search all in one Skill. For...
README (SKILL.md)

Heurist Mesh

Heurist Mesh is an open network of modular AI agent tools for cryptocurrency and blockchain data. All features accessible via a unified REST API.

Recommended Agents and Tools

TrendingTokenAgent — Trending tokens and market summary

  • get_trending_tokens — Get trending tokens most talked about and traded on CEXs and DEXs
  • get_market_summary — Get recent market-wide news including macro and major updates

TokenResolverAgent — Find tokens and get detailed profiles

  • token_search — Find tokens by address, ticker/symbol, or name (up to 5 candidates)
  • token_profile — Get detailed token profile with pairs, funding rates, and indicators

DefiLlamaAgent — DeFi protocol and chain metrics

  • get_protocol_metrics — Get protocol TVL, fees, volume, revenue, chains, and growth trend
  • get_chain_metrics — Get blockchain TVL, fees, top protocols, and growth trends

TwitterIntelligenceAgent — Twitter/X data

  • user_timeline — Fetch a user's recent posts and announcements
  • tweet_detail — Get a tweet with thread context and replies
  • twitter_search — Search for posts and influential mentions on any topic

ExaSearchDigestAgent — Web search with summarization

  • exa_web_search — Search the web with LLM summarization, time and domain filters
  • exa_scrape_url — Scrape a URL and summarize or extract information

ChainbaseAddressLabelAgent — EVM address labels

  • get_address_labels — Get labels for ETH/Base addresses (identity, contract names, wallet behavior, ENS)

ZerionWalletAnalysisAgent — EVM wallet holdings

  • fetch_wallet_tokens — Get token holdings with USD value and 24h price change
  • fetch_wallet_nfts — Get NFT collections held by a wallet

ProjectKnowledgeAgent — Crypto project database

  • get_project — Look up a project by name, symbol, or X handle (team, investors, events)
  • semantic_search_projects — Natural language search across 10k+ projects (filter by investor, tag, funding year, exchange)

CaesarResearchAgent — Academic research

  • caesar_research — Submit a research query for in-depth analysis
  • get_research_result — Retrieve research results by ID

AskHeuristAgent — Crypto Q&A and deep analysis (Important: recommended for in-depth crypto topics)

  • ask_heurist — Submit a crypto question (normal or deep analysis mode)
  • check_job_status — Check status of a pending analysis job

Setup (MUST complete before making any API calls)

You need at least one payment method configured. DO NOT call any Mesh tool APIs until setup is verified.

Step 1: Choose a payment method

Option A: Heurist API Key (Recommended — simplest)

  1. Get an API key via ONE of:
  2. Store the key in .env in the project root:
    HEURIST_API_KEY=your-api-key-here
    
  3. All API calls use Authorization: Bearer $HEURIST_API_KEY

Option B: x402 On-Chain Payment (USDC on Base)

  1. You need a wallet private key with USDC balance on Base.
  2. Store the key in .env in the project root:
    WALLET_PRIVATE_KEY=0x...your-private-key
    
  3. See references/x402-payment.md for the payment flow using cast (Foundry).

Option C: Inflow Payment Platform (USDC via Inflow)

  1. If you already have Inflow credentials, store them in .env:
    INFLOW_USER_ID=your-buyer-user-id
    INFLOW_PRIVATE_KEY=your-buyer-private-key
    
  2. If not, create a buyer account and attach email — see references/inflow-payment.md for one-time setup.
  3. Inflow uses a two-call payment flow (create request → user approves → execute). See references/inflow-payment.md for the full flow.

Step 2: Verify setup

Check that credentials are configured before proceeding:

  • API Key path: Read .env and confirm HEURIST_API_KEY is set and non-empty.
  • x402 path: Read .env and confirm WALLET_PRIVATE_KEY is set, starts with 0x, and is 66 characters.
  • Inflow path: Read .env and confirm INFLOW_USER_ID and INFLOW_PRIVATE_KEY are set and non-empty.

If neither is configured, STOP and ask the user to set up a payment method. Do not make API calls without valid credentials.

Step 3: Make API calls

Once you have either Heurist API key or x402 wallet private key or Inflow key, you can make API calls. You should understand the tool schema and the parameters of tools you want before calling it.

To fetch tool schema, use mesh_schema API:

GET https://mesh.heurist.xyz/mesh_schema?agent_id=TokenResolverAgent&agent_id=CoinGeckoTokenInfoAgent

Default pricing is in credits. 1 credit worth $0.01. Add &pricing=usd to get prices in USD instead of credits when using x402 or Inflow. Returns each tool's parameters (name, type, description, required/optional) and per-tool price.

Then use the credentials in requests:

# With API key
curl -X POST https://mesh.heurist.xyz/mesh_request \
  -H "Authorization: Bearer $HEURIST_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"agent_id": "TokenResolverAgent", "input": {"tool": "token_search", "tool_arguments": {"query": "ETH"}, "raw_data_only": true}}'

# With x402 — sign with cast (Foundry), no account or SDK needed
# See references/x402-payment.md for the full cast-based flow and helper script

Discover More Agents

All agents: Fetch https://mesh.heurist.ai/metadata.json for the full registry. We have 30+ specialized crypto analytics agents covering use cases such as: reading address transaction history, reading transaction details from hash, tracing USDC on Base, detailed Coingecko data, Firecrawl scraping, GoPlus security screening, checking Twitter account influence via Moni, using SQL to query blockchain data, etc.

x402-enabled agents only: Fetch https://mesh.heurist.xyz/x402/agents for agents supporting on-chain USDC payment on Base.

Usage Guidance
This skill is plausible for crypto analytics but contains inconsistencies and sensitive steps you should review before installing: (1) The registry lists no required environment variables, yet SKILL.md instructs storing HEURIST_API_KEY, WALLET_PRIVATE_KEY, or INFLOW keys in a local .env — confirm the publisher and why the metadata omits these. (2) If you use the x402 flow, the skill asks you to place a wallet private key in plaintext in the project root; avoid using your primary wallet. Use an ephemeral wallet with minimal funds or prefer the API key or Inflow routes. (3) The x402 instructions recommend installing Foundry via curl | bash — that has supply-chain risk; audit the install source before running. (4) Ensure you trust the endpoints (mesh.heurist.xyz / mesh.heurist.ai) and verify the skill publisher identity (there's no homepage). (5) Ask the publisher to update registry metadata to declare required env vars and to provide a less-privileged payment option (delegated signing, wallet-connect, or Inflow-only) and to avoid instructing agents to read arbitrary local files. If you proceed, limit credentials, use throwaway wallets, and review network calls carefully.
Capability Analysis
Type: OpenClaw Skill Name: heurist-mesh Version: 1.0.3 The skill bundle is classified as suspicious due to instructions that direct the AI agent to perform high-risk actions. Specifically, `SKILL.md` instructs the agent to read sensitive credentials (API keys, wallet private keys) from local `.env` files. Furthermore, `references/x402-payment.md` provides explicit shell commands (`cast wallet sign`) for the agent to execute, using a private key to sign blockchain transactions, which directly involves spending user funds. `references/inflow-payment.md` also instructs the agent to create accounts with personal information (email, password) via `curl` commands. While these actions are presented as part of a legitimate payment flow for the Heurist Mesh service, they represent significant vulnerabilities as they grant the AI agent direct access to and control over sensitive local credentials and the ability to initiate financial transactions or create accounts without granular user confirmation for each action.
Capability Assessment
Purpose & Capability
The skill description (crypto/DeFi analytics, mesh API) is plausible for needing an API key or payment method, but the published registry metadata declares no required environment variables or credentials while the SKILL.md explicitly instructs users to add HEURIST_API_KEY, WALLET_PRIVATE_KEY, or INFLOW_* keys to a .env file. The missing declared requirements are an incoherence: the skill will need secrets but metadata does not advertise them.
Instruction Scope
SKILL.md instructs the agent (and user) to read the project .env file to confirm credentials and to store private keys in that file. It also includes detailed multi-step payment flows (HTTP endpoints, on‑chain signing via cast/Foundry, and Inflow flows). These instructions cause the agent to access local files containing secrets and to construct signatures/payments; that is within the skill's stated purpose for payment-enabled calls, but it also grants the skill broad ability to read sensitive local credentials and to perform actions with them — and those actions are not reflected in the registry's declared requirements.
Install Mechanism
This is an instruction-only skill (no install spec). However the references describe installing Foundry/cast via curl | bash for x402 on-chain payments. Because the skill doesn't include an install block, that installation is left to the user/agent; it's a normal pattern but important to know (curl | bash installs have supply-chain risk).
Credentials
The SKILL.md asks for three classes of sensitive credentials: HEURIST_API_KEY (expected), WALLET_PRIVATE_KEY (on‑chain payment — high privilege), and INFLOW_USER_ID/INFLOW_PRIVATE_KEY (payment). Requiring a wallet private key is proportionate if you choose the x402 flow, but the registry metadata did not declare any required env vars and the instructions ask the agent to read .env directly. Storing a raw private key in a project .env is risky; if you must use on‑chain payments, a dedicated ephemeral wallet or delegated signing is safer.
Persistence & Privilege
The skill does not request always:true and does not declare modifications to other skills or global config. Autonomous invocation is allowed (platform default) but not uniquely privileged here. The skill's runtime behavior doesn't request permanent system-level presence beyond reading .env and interacting with remote Mesh endpoints.
How to Use
  1. Make sure OpenClaw is installed (local or Docker)
  2. Run the install command in chat: /install heurist-mesh
  3. After installation, invoke the skill by name or use /heurist-mesh
  4. Provide required inputs per the skill's parameter spec and get structured output
Version History
v1.0.3
Version 1.0.3 - Overhauled setup instructions to include three payment options: Heurist API key, x402 on-chain (USDC), and Inflow (USDC agentic payment platform). - Added concise quickstart instructions and tool descriptions for all major agents. - Added references for payment setup: `heurist-api-key.md`, `x402-payment.md`, and `inflow-payment.md`. - Updated tool and agent documentation to highlight recommended and new capabilities. - Improved guidance for tool discovery, pricing, and schema inspection.
v1.0.2
- Added detailed instructions for using "Ask Heurist," a new crypto Q&A and research agent
v1.0.1
- Updated the default Heurist Mesh MCP server URL from /mcp/sse to /mcp/ in the mcporter.json configuration example. - No other changes.
v1.0.0
Initial release of heurist-mesh skill. - Access 30+ specialized AI agents for Web3 and crypto intelligence via Heurist Mesh MCP. - Supports cryptocurrency analytics, token info, trending tokens, wallet analysis, Twitter/X crypto intelligence, funding rates, and market summaries. - Provides guidance for one-time setup, including API key configuration and mcporter integration. - Lists available tools and default agents for diverse crypto use cases. - Includes usage examples and instructions for advanced custom MCP server configuration. - Read-only analytics; does not enable trading or onchain transactions.
Metadata
Slug heurist-mesh
Version 1.0.3
License
All-time Installs 3
Active Installs 3
Total Versions 4
Frequently Asked Questions

What is Heurist Mesh Crypto Analysis Skill?

Real-time crypto token data, DeFi analytics, blockchain data, Twitter/X social intelligence, enhanced web search, crypto project search all in one Skill. For... It is an AI Agent Skill for Claude Code / OpenClaw, with 2593 downloads so far.

How do I install Heurist Mesh Crypto Analysis Skill?

Run "/install heurist-mesh" in the OpenClaw or Claude Code chat to install it in one step — no extra setup required.

Is Heurist Mesh Crypto Analysis Skill free?

Yes, Heurist Mesh Crypto Analysis Skill is completely free (open-source). You can download, install and use it at no cost.

Which platforms does Heurist Mesh Crypto Analysis Skill support?

Heurist Mesh Crypto Analysis Skill is cross-platform and runs anywhere OpenClaw / Claude Code is available (cross-platform).

Who created Heurist Mesh Crypto Analysis Skill?

It is built and maintained by JW (@wjw12); the current version is v1.0.3.

💬 Comments