← Back to Skills Marketplace
davidtaikocha

Etherscan

by David · GitHub ↗ · v1.0.0
cross-platform ⚠ suspicious
476
Downloads
0
Stars
0
Active Installs
1
Versions
Install in OpenClaw
/install etherscan-api
Description
Use when you need to query Etherscan API V2 for onchain activity, contract metadata, ABI/source retrieval, proxy implementation discovery, and transaction/lo...
README (SKILL.md)

Etherscan API V2

Overview

Use this skill to fetch onchain data from Etherscan-compatible explorers using the unified V2 API.

Core model:

  • One base URL: https://api.etherscan.io/v2/api
  • One API key
  • Switch chains via chainid

Explorer URLs relevant to this workspace:

  • Ethereum mainnet: https://etherscan.io/
  • Ethereum hoodi: https://hoodi.etherscan.io/
  • Taiko mainnet: https://taikoscan.io/
  • Taiko hoodi: https://hoodi.taikoscan.io/

Read first:

  • references/network-map.md
  • references/endpoint-cheatsheet.md
  • references/rate-limits.md
  • references/explorer-url-patterns.md

Required Inputs

Collect these before querying:

  • ETHERSCAN_API_KEY
  • Target chainid
  • Address / tx hash / block range
  • Endpoint intent (activity, logs, source, ABI, status)

Deterministic Workflow

  1. Pick chainid from references/network-map.md.
  2. Choose endpoint by intent from references/endpoint-cheatsheet.md.
  3. Build request on https://api.etherscan.io/v2/api with required params.
  4. Parse status, message, result.
  5. If contract endpoint returns proxy metadata (Proxy == "1"), follow Implementation.
  6. For large history, paginate (page, offset) and/or narrow block ranges.

Method Selection

Goal Module / Action
Address normal tx history account / txlist
Address internal tx history account / txlistinternal
ERC20 transfer history account / tokentx
Event logs logs / getLogs
Contract ABI contract / getabi
Contract source + proxy fields contract / getsourcecode
Contract deployer + creation tx contract / getcontractcreation
Tx execution status transaction / getstatus
Tx receipt status transaction / gettxreceiptstatus

Quick Commands

Set key once:

export ETHERSCAN_API_KEY="\x3Cyour_key>"

Get ABI (Taiko mainnet example):

curl -s "https://api.etherscan.io/v2/api?chainid=167000&module=contract&action=getabi&address=\x3Ccontract>&apikey=$ETHERSCAN_API_KEY"

Get source + proxy metadata (Taiko hoodi example):

curl -s "https://api.etherscan.io/v2/api?chainid=167013&module=contract&action=getsourcecode&address=\x3Ccontract>&apikey=$ETHERSCAN_API_KEY"

Get address activity in block window:

curl -s "https://api.etherscan.io/v2/api?chainid=1&module=account&action=txlist&address=\x3Caddress>&startblock=\x3Cfrom>&endblock=\x3Cto>&page=1&offset=100&sort=desc&apikey=$ETHERSCAN_API_KEY"

Get logs for a contract in block window:

curl -s "https://api.etherscan.io/v2/api?chainid=560048&module=logs&action=getLogs&address=\x3Ccontract>&fromBlock=\x3Cfrom>&toBlock=\x3Cto>&page=1&offset=1000&apikey=$ETHERSCAN_API_KEY"

Proxy-Aware Contract Handling

When getsourcecode returns:

  • Proxy: "1"
  • non-empty Implementation

then:

  1. Keep runtime call target as proxy address.
  2. Fetch ABI/source from implementation address.
  3. Decode selectors against implementation ABI.
  4. Re-check implementation before privileged write analysis.

Safety Rails

Never skip these checks:

  • Always set correct chainid; wrong chain silently yields wrong context.
  • Respect plan limits and add client-side throttling/retries.
  • Treat status: "0" as non-success even with HTTP 200.
  • For analytics windows, lock startblock/endblock explicitly.
  • For logs, remember offset max is 1000 per query and paginate.
  • Keep retries idempotent and resume scans from stored cursors/block checkpoints.

Expected Output

Return:

  • exact URL/query used (without exposing secret key)
  • chain (chainid + explorer)
  • endpoint (module/action)
  • parsed status/result summary
  • proxy follow-up decisions (Proxy, Implementation) when contract-related
Usage Guidance
This appears to be a legitimate Etherscan-client instruction set, but the registry metadata is incomplete: SKILL.md expects an ETHERSCAN_API_KEY and suggests saving scan checkpoints, yet the skill manifest declares no environment variables or config paths. Before installing, ask the publisher to (1) declare ETHERSCAN_API_KEY (and its scope) in requires.env/primary credential, (2) confirm where persisted cursors/checkpoints are stored and what filesystem access is required, and (3) ensure the skill redacts the API key from any returned text (SKILL.md says to return the exact URL/query 'without exposing secret key'—verify enforcement). Also prefer creating a least-privilege/limited-rate API key and validate client-side throttling to avoid accidental overuse. If you cannot obtain these clarifications, treat the skill as untrusted and avoid supplying high-privilege API keys.
Capability Analysis
Type: OpenClaw Skill Name: etherscan-api Version: 1.0.0 The skill bundle provides a well-documented interface for querying the Etherscan API V2. All `curl` commands and instructions in `SKILL.md` and reference files are directed at the official `https://api.etherscan.io/v2/api` endpoint and legitimate Etherscan-compatible explorer URLs. The `ETHERSCAN_API_KEY` is explicitly required as an input for its intended use, and there is no evidence of data exfiltration, malicious execution, persistence mechanisms, or prompt injection attempts designed to make the agent perform unauthorized actions or steal sensitive data. The 'Safety Rails' section even promotes good operational security practices.
Capability Assessment
Purpose & Capability
SKILL.md clearly requires an ETHERSCAN_API_KEY and describes API usage across multiple chains, but the registry metadata lists no required environment variables or primary credential. That mismatch suggests the manifest is incomplete or the skill will prompt for/expect secrets without declaring them.
Instruction Scope
Runtime instructions stay focused on querying Etherscan V2 (constructing API URLs, parsing responses, proxy-aware ABI resolution, pagination and throttling). They do not ask to read arbitrary system files or call unrelated endpoints.
Install Mechanism
This is instruction-only with no install spec and no code files — low install risk. Nothing is downloaded or written by an installer according to the manifest.
Credentials
The SKILL.md instructs users to set and use ETHERSCAN_API_KEY, yet requires.env is empty and primary credential is none. The skill also suggests persisting scan cursors/checkpoints but lists no config paths. Requesting/using an API key without declaring it is disproportionate and a registry oversight.
Persistence & Privilege
always:false and disable-model-invocation:false (normal). The guidance to persist cursors/state is reasonable for long scans, but the skill doesn't declare where or how to store that state (no config paths). Confirm expected storage location and permissions before use.
How to Use
  1. Make sure OpenClaw is installed (local or Docker)
  2. Run the install command in chat: /install etherscan-api
  3. After installation, invoke the skill by name or use /etherscan-api
  4. Provide required inputs per the skill's parameter spec and get structured output
Version History
v1.0.0
Initial release of the etherscan-api skill. - Provides a unified workflow for querying on-chain activity, contract metadata, proxy information, and logs across Etherscan-compatible EVM chains using API v2. - Supports fast chain selection via chainid and standardized endpoint selection per intent (activity, logs, ABI, status). - Includes built-in safety and pagination guidance, plus proxy-aware contract decoding. - Offers practical command-line usage examples and reference links for network maps and endpoint cheatsheets.
Metadata
Slug etherscan-api
Version 1.0.0
License
All-time Installs 0
Active Installs 0
Total Versions 1
Frequently Asked Questions

What is Etherscan?

Use when you need to query Etherscan API V2 for onchain activity, contract metadata, ABI/source retrieval, proxy implementation discovery, and transaction/lo... It is an AI Agent Skill for Claude Code / OpenClaw, with 476 downloads so far.

How do I install Etherscan?

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

Is Etherscan free?

Yes, Etherscan is completely free (open-source). You can download, install and use it at no cost.

Which platforms does Etherscan support?

Etherscan is cross-platform and runs anywhere OpenClaw / Claude Code is available (cross-platform).

Who created Etherscan?

It is built and maintained by David (@davidtaikocha); the current version is v1.0.0.

💬 Comments