metengine-data-agent_skill

This skill provides real-time smart money analytics across major markets, delivering actionable insights without onboarding complexity.
  • Python

2.5k

GitHub Stars

2

Bundled Files

2 months ago

Catalog Refreshed

4 months ago

First Indexed

Readme & install

Copy the install command, review bundled files from the catalogue, and read any extended description pulled from the listing source.

Installation

Preview and clipboard use veilstrat where the catalogue uses aiagentskills.

npx veilstrat add skill openclaw/skills --skill metengine-data-agent

  • _meta.json297 B
  • skill.md72.6 KB

Overview

This skill provides real-time smart-money analytics across Polymarket prediction markets, Hyperliquid perpetuals, and Meteora Solana LP/AMM pools. It exposes 63 endpoints for wallet scoring, insider detection, capital-flow tracking, position analysis, and market intelligence. Payments are handled per-request via the x402 Solana protocol using USDC; no API keys or accounts are required.

How this skill works

Clients perform a two-step paid fetch: an initial GET returns a 402 with payment requirements, the agent signs a payment payload with a Solana signer, then resubmits the request with the PAYMENT-SIGNATURE header. Successful 2xx responses return data plus settlement proof (transaction hash). A separate free pricing endpoint returns the full machine-readable pricing schedule. Agents should persist a local memory file to avoid repeating setup and speed subsequent calls.

When to use it

  • When you need on-chain informed signals about smart-money flows and leaderboards across Polymarket, Hyperliquid, and Meteora.
  • To score wallets, detect insiders, or compare trader performance before following or copying positions.
  • When building dashboards that need low-latency, pay-per-query analytics without managing API keys.
  • For automated agents that can sign Solana payments and want provable settlement receipts.
  • When you require precise cost estimates from the pricing endpoint before executing high-volume scans.

Best practices

  • Always check and read the persistent memory file at ~/.claude/agents/metengine-memory.md before making API calls to reuse bootstrap code and pricing cache.
  • Never truncate or trim wallet, contract, condition_id, token_id, pool address, position address, or transaction hash strings—always display full addresses.
  • Call the free /api/v1/pricing endpoint to compute expected cost using timeframe, limit, and filters before initiating paid requests.
  • Record endpoint results and fallbacks in memory after each call to avoid repeated failures and save tokens.
  • Keep Solana signer private keys off-disk in logs and never store private keys in the memory file—only store file paths and public addresses.

Example use cases

  • Fetch top trending Polymarket markets for the last 24h and pay per-request to retrieve settlement-proofed data.
  • Score candidate wallets for smart-money behavior and compile a watchlist of high-conviction traders.
  • Compare Hyperliquid traders across multiple positions to identify professional liquidity providers.
  • Analyze Meteora pool fee history and LP performance with paid detailed endpoints for specific pool addresses.
  • Automate a bot that signs payments, queries wallet comparisons, and updates a dashboard with provable settlement receipts.

FAQ

No. Authentication is performed by paying per request via x402 on Solana Mainnet using a signed PAYMENT-SIGNATURE.

How do I estimate request cost?

Use the free GET /api/v1/pricing endpoint to compute base tier, timeframe multipliers, limit modifiers, and applicable discounts before calling paid endpoints.

Built by
VeilStrat
AI signals for GTM teams
© 2026 VeilStrat. All rights reserved.All systems operational
metengine-data-agent skill by openclaw/skills | VeilStrat