Requirements
- Target platform
- OpenClaw
- Install method
- Manual import
- Extraction
- Extract archive
- Prerequisites
- OpenClaw
- Primary doc
- SKILL.md
Query crypto intelligence via Pond3r MCP — curated datasets, SQL queries, protocol metrics, yields, and market analysis. Use when the agent needs DeFi data, stablecoin yields, token opportunities, Polymarket trades, cross-protocol comparisons, or blockchain analytics.
Query crypto intelligence via Pond3r MCP — curated datasets, SQL queries, protocol metrics, yields, and market analysis. Use when the agent needs DeFi data, stablecoin yields, token opportunities, Polymarket trades, cross-protocol comparisons, or blockchain analytics.
Hand the extracted package to your coding agent with a concrete install brief instead of figuring it out manually.
I downloaded a skill package from Yavira. Read SKILL.md from the extracted folder and install it by following the included instructions. Tell me what you changed and call out any manual steps you could not complete.
I downloaded an updated skill package from Yavira. Read SKILL.md from the extracted folder, compare it with my current installation, and upgrade it while preserving any custom configuration unless the package docs explicitly say otherwise. Summarize what changed and any follow-up checks I should run.
Use this skill when the agent needs to query crypto/DeFi data: yields, protocol metrics, token opportunities, market analysis, or blockchain analytics. Pond3r provides an MCP server with read-only SQL access to curated datasets.
API key: Obtain at makeit.pond3r.xyz/api-keys MCP setup: Pond3r must be configured as an MCP server in the runtime (Claude Code, Cursor, Claude Desktop, etc.)
The agent needs MCP tools (list_datasets, get_schema, query) to use Pond3r. Those tools come from the runtime that executes the agent — not from the skill or env vars alone. RuntimeHow to enable Pond3rCursorCursor Settings → MCP Servers → Add server (URL + Authorization header). See MCP Connection below.Claude DesktopAdd Pond3r to claude_desktop_config.json under mcpServers. Restart Claude.Claude CodeRun claude mcp add pond3r-data ... (see below).OpenClaw (Docker/Telegram)Use the CLI scripts below. They call Pond3r MCP via HTTP. Set POND3R_API_KEY in .env; the agent runs the scripts and parses JSON output. No extra info for the agent — the skill is enough. For runtimes with native MCP, add the API key in the MCP server config. For OpenClaw, use the scripts and POND3R_API_KEY in env.
SettingValueURLhttps://mcp.pond3r.xyz/mcpTransportStreamable HTTPAuthAuthorization: Bearer <API_KEY>
Open Cursor → Settings (⌘+,) → MCP Click Add new MCP server Configure: URL: https://mcp.pond3r.xyz/mcp Headers: Authorization: Bearer <YOUR_POND3R_API_KEY> Replace <YOUR_POND3R_API_KEY> with your key from makeit.pond3r.xyz/api-keys Some clients support Authorization: Bearer ${POND3R_API_KEY} if that env var is set Save and restart Cursor so tools load Verify: start a new chat and ask for stablecoin yields — the agent should call list_datasets, get_schema, query
claude mcp add pond3r-data \ --transport http \ https://mcp.pond3r.xyz/mcp \ --header "Authorization: Bearer <API_KEY>"
{ "mcpServers": { "pond3r": { "type": "http", "url": "https://mcp.pond3r.xyz/mcp", "headers": { "Authorization": "Bearer <API_KEY>" } } } }
When MCP tools are not available (e.g. OpenClaw/Telegram), use these scripts. They call Pond3r MCP over HTTP. Requires POND3R_API_KEY in env (e.g. in .env loaded by docker-compose). Scripts live at /opt/pond3r-skill-scripts/ in the Docker image. When running locally, use ceo-agent/skills/pond3r-skill/scripts/ or the workspace-relative path.
node /opt/pond3r-skill-scripts/list-datasets.mjs Output: JSON with all datasets and tables.
node /opt/pond3r-skill-scripts/get-schema.mjs --dataset-id <dataset_id>
node /opt/pond3r-skill-scripts/query.mjs --dataset-id <dataset_id> --sql "SELECT * FROM stablecoin_yields LIMIT 10" Or from file: node /opt/pond3r-skill-scripts/query.mjs --sql-file /tmp/query.sql
Run list-datasets.mjs to discover datasets and table names. Run get-schema.mjs --dataset-id <id> to see columns and types. Run query.mjs --dataset-id <id> --sql "SELECT ..." with valid SQL (SELECT only, bare table names, LIMIT where appropriate). Parse the JSON output and summarize for the user.
Missing required env var: POND3R_API_KEY → Add POND3R_API_KEY to .env and ensure it is loaded (e.g. docker-compose env_file: .env). Pond3r MCP HTTP 401 → Invalid or expired API key; rotate key at makeit.pond3r.xyz/api-keys. Pond3r MCP error: ... → Check SQL syntax, table names, and row limits.
ToolPurposelist_datasetsList all datasets and their tablesget_schemaGet column names, types, descriptions for a datasetqueryExecute read-only SQL against a dataset
SELECT only — write operations are not allowed Bare table names — use SELECT * FROM stablecoin_yields, not fully qualified paths Results capped at 10,000 rows — use LIMIT or WHERE filters for large datasets Cost estimation — queries exceeding tier limits are rejected before running
Protocol Intelligence Track AI agent launches, token graduations, protocol metrics Daily yield farming reports across Aave, Compound, Convex Market Opportunity Detection New tokens on Uniswap with rising liquidity Tokens with <$500K market cap and rising liquidity Polymarket trades with highest volume Risk-Adjusted Analysis Multi-dimensional risk scoring (volatility, liquidity, market structure) Liquidation risk monitoring for DeFi positions Whale activity tracking Cross-Protocol & Cross-Chain Compare USDC yields across Aave and Compound on Arbitrum Bridge volume analysis, ecosystem health comparison Arbitrage opportunity detection Structured Data for Decisions Statistical analysis, trend identification Volume pattern analysis, unusual trading activity Sentiment scoring (Farcaster, influencer activity)
Agent asks in natural language; MCP tools discover schema and execute SQL. Example prompts: "What are the top 5 stablecoin yields on Ethereum right now?" "Show me Polymarket trades from the last 24 hours with the highest volume." "Compare USDC yields across Aave and Compound on Arbitrum."
Discover available data: Call list_datasets to see datasets and tables Understand schema: Call get_schema for the dataset you need Write and run: Use query with valid SQL (SELECT, bare table names, LIMIT where appropriate) Interpret results: Use returned data for analysis, proposals, or decisions
Before answering with Pond3r-backed data: Prefer scripts when MCP tools are unavailable: If list_datasets, get_schema, query are not exposed by the runtime, use the CLI scripts instead. Run node /opt/pond3r-skill-scripts/list-datasets.mjs (or workspace path) with POND3R_API_KEY in env. If neither MCP nor scripts work: Stop and return: Pond3r unavailable: MCP tools missing and scripts failed (check POND3R_API_KEY in env). Do not assume fallback permission: Do not switch to web_search, web_fetch, or other sources unless the user explicitly approves fallback. Return execution evidence: Include the exact commands run and summarize returned dataset/query output. If a call fails, include the exact error message and next remediation step.
SymptomFix"Pond3r MCP not configured"Add MCP server in your runtime (Cursor/Claude) with URL + Bearer header. Restart.Tools still missing after configRestart the app (Cursor/Claude). MCP loads at startup.Agent runs in OpenClaw/TelegramUse the CLI scripts with POND3R_API_KEY in .env. See CLI Scripts.Auth/401 errorsCheck API key is valid, not expired. Rotate if it was ever exposed.
If MCP tools are unavailable, provide only: missing tool names required server URL (https://mcp.pond3r.xyz/mcp) required auth header format (Authorization: Bearer <API_KEY>) If SQL is rejected (tier/cost/limits), rewrite with tighter WHERE/LIMIT and retry. If access/auth fails, report authorization/configuration failure and request key/server verification.
For scheduled reports and structured JSON delivery, use the REST API: Create report: POST https://api.pond3r.xyz/v1/api/reports with description, schedule, delivery_format Get latest: GET https://api.pond3r.xyz/v1/api/reports/{reportId}/latest Headers: x-api-key: <API_KEY> Report format includes executiveSummary, analysis, opportunities. For full API details and response structure, see reference.md.
Never expose API keys in client-side code or public repositories Use environment variables for API keys MCP tools are read-only; no writes to Pond3r datasets Never print secret values in logs, chat, or command output (only report presence/absence) If a secret is accidentally exposed, instruct immediate key rotation before continuing
Code helpers, APIs, CLIs, browser automation, testing, and developer operations.
Largest current source with strong distribution and engagement signals.