← Back to Skills Marketplace
jesse-pallok

Bluepages

by jesse-pallok · GitHub ↗ · v1.0.2
cross-platform ⚠ suspicious
1185
Downloads
2
Stars
2
Active Installs
4
Versions
Install in OpenClaw
/install bluepages
Description
Look up wallet address <> Twitter/Farcaster identity mappings via Bluepages.fyi. Use when asked who owns a wallet, finding addresses for a Twitter/Farcaster...
README (SKILL.md)

Bluepages

800K+ verified Ethereum address \x3C> Twitter/X mappings, plus Farcaster.

Setup

Requires the Bluepages MCP server: npx -y github:bluepagesdoteth/bluepages-mcp or direct API calls (see below). The MCP server is the recommended way to use Bluepages.

Authentication

Requires one of these env vars:

  • BLUEPAGES_API_KEY (recommended) — 20% cheaper, 2x rate limits.
  • PRIVATE_KEY — Ethereum private key for x402 pay-per-request (USDC on Base).

Security note: Never use a main wallet key. Use a dedicated, funded-only-as-needed agent wallet if providing PRIVATE_KEY.

With a private key, you can either pay per request via x402 or purchase a BLUEPAGES_API_KEY using the get_api_key and purchase_credits MCP tools.

Without a private key, the user must get an API key at bluepages.fyi/api-keys and set BLUEPAGES_API_KEY.

Tools (quick reference)

Tool Cost Description
check_address 1 credit ($0.001) Check if address has data
check_twitter 1 credit ($0.001) Check if Twitter handle has data
get_data_for_address 50 credits ($0.05) Full identity data for address (free if not found)
get_data_for_twitter 50 credits ($0.05) Full identity data for handle (free if not found)
batch_check 40 credits ($0.04) Check up to 50 items at once
batch_get_data 40 credits/found item Data for up to 50 items (x402: $2.00 flat/batch)
batch_check_streaming same as batch_check For large lists (100+), shows progress
batch_get_data_streaming same as batch_get_data For large lists (100+), shows progress
check_credits free Check remaining credits (API key only)
set_credit_alert free Set low-credit warning threshold (API key only)
get_api_key free Get/create API key via wallet signature
purchase_credits $5–$600 USDC Buy credits via x402 (PRIVATE_KEY only)

Input format

  • Addresses: 0x-prefixed, 42-char hex. Case-insensitive.
  • Twitter handles: With or without @.

Cost-saving workflow

  • Single lookups: check_address/check_twitter first (1 credit), then get_data_* only if found (50 credits). Skipping the check wastes credits on misses.
  • Batch lookups: Always two-phase — batch_check then batch_get_data on found items only. This saves ~90% vs fetching everything blind.
  • Large lists (100+): Use _streaming variants for progress updates.

Rate limits

  • API Key: 60 req/min
  • x402: 30 req/min
  • Batch: max 50 items per request

Alternative: Direct HTTP API

If MCP is unavailable, call the API directly. Auth depends on your setup:

  • API key: pass X-API-KEY header
  • Private key (x402): endpoints return a 402 with payment details; sign and resend with X-PAYMENT header
# With API key
curl "https://bluepages.fyi/check?address=0x..." -H "X-API-KEY: your-key"
curl "https://bluepages.fyi/data?address=0x..." -H "X-API-KEY: your-key"

# Batch check
curl -X POST "https://bluepages.fyi/batch/check" \
  -H "X-API-KEY: your-key" -H "Content-Type: application/json" \
  -d '{"addresses": ["0x...", "0x..."]}'

Full API docs: bluepages.fyi/docs

Usage Guidance
Before installing: 1) Clarify the env-var discrepancy — confirm whether the skill requires BOTH BLUEPAGES_API_KEY and PRIVATE_KEY or just one of them (SKILL.md says one of). 2) Prefer using BLUEPAGES_API_KEY (less sensitive); avoid giving your main Ethereum private key. If you must provide a PRIVATE_KEY, use a dedicated, minimally funded wallet and rotate it after use. 3) Because the install runs remote code via npx (github:bluepagesdoteth/bluepages-mcp), review the GitHub repo and its code (or run it in an isolated sandbox/container) before executing. 4) Be aware of per-request costs and rate limits described in the doc. 5) If you want stronger guarantees, ask the publisher for a signed release or a packaged artifact you can inspect, and consider restricting the skill's use (do not grant it broad autonomous actions) until you're comfortable.
Capability Analysis
Type: OpenClaw Skill Name: bluepages Version: 1.0.2 This skill is suspicious due to its explicit requirement for an Ethereum `PRIVATE_KEY` for certain operations (x402 payments, API key acquisition via wallet signature). While the `SKILL.md` includes a security note warning users, the agent is instructed to handle and potentially use this highly sensitive credential, which poses a significant risk if the agent's environment or the `bluepages-mcp` package (installed from `github:bluepagesdoteth/bluepages-mcp`) is compromised. The installation from a GitHub repository also introduces a supply chain risk, as a compromised repository could lead to the execution of malicious code with access to the private key.
Capability Assessment
ℹ Purpose & Capability
The skill claims to map wallet addresses to Twitter/Farcaster identities and all runtime instructions and API endpoints align with that purpose. However, the registry metadata lists both BLUEPAGES_API_KEY and PRIVATE_KEY as required env vars, while SKILL.md explicitly says you need one of them (API key recommended, private key optional for x402 payments). This inconsistency is unexpected and should be clarified.
ℹ Instruction Scope
SKILL.md restricts operations to calling bluepages.fyi (or running the bluepages MCP via npx) and describes the expected request/credit flow. It does not instruct reading unrelated local files or contacting other endpoints. However, it does instruct use of a PRIVATE_KEY for x402 payments — handling a private key is sensitive and expands the risk profile (signing payment requests). The doc warns not to use a main wallet key, which is good guidance but does not eliminate the sensitivity.
⚠ Install Mechanism
Installation is via a node package hosted on GitHub and the SKILL.md recommends running it with npx (npx -y github:bluepagesdoteth/bluepages-mcp). While GitHub is a common host, npx will fetch and execute remote code at runtime, which increases risk compared to instruction-only skills. This is proportionate for a client/server tool but users should audit the repository or run the package in a sandbox before trusting it.
⚠ Credentials
Requesting an API key (BLUEPAGES_API_KEY) is proportionate to the service. Requesting a PRIVATE_KEY (Ethereum private key) is explainable for on-chain x402 payments, but it is highly sensitive and should be optional. The registry metadata's requirement of both env vars is inconsistent with the SKILL.md's 'one of' statement and is a red flag — the skill should not demand unrelated credentials. Prefer an API key; if a private key is provided, restrict funds and use a throwaway agent wallet as recommended.
✓ Persistence & Privilege
The skill does not request always: true, does not declare any special config paths, and relies on normal agent invocation. It does not request system-wide privileges or to modify other skills' configs. Default autonomous invocation is enabled (platform default) but is not combined with other excessive privileges here.
How to Use
  1. Make sure OpenClaw is installed (local or Docker)
  2. Run the install command in chat: /install bluepages
  3. After installation, invoke the skill by name or use /bluepages
  4. Provide required inputs per the skill's parameter spec and get structured output
Version History
v1.0.2
- Added OpenClaw metadata to the manifest, including emoji, install instructions, homepage, and required env vars. - Bumped skill version to 1.0.2.
v1.0.1
- Added explicit compatibility requirements for MCP server and supported authentication methods. - Clarified authentication instructions, including security best practices for PRIVATE_KEY. - Expanded tool cost and usage explanations; added cost-saving workflow guidance. - Summarized supported identities (Ethereum, Twitter/X, Farcaster) in the introduction. - Included instructions for using the direct HTTP API as an alternative to MCP. - Updated and reorganized documentation for improved clarity and setup guidance.
v0.1.0
- Initial release of Bluepages skill with lookup for Ethereum address ↔ Twitter/X and Farcaster identity mappings. - Supports queries for wallet owners, address attribution, and social handle lookups. - Requires Bluepages MCP server or direct API use with authentication via API key or private key. - Provides tools for individual and batch checks, including cost-saving and large-list workflows. - Detailed setup, usage instructions, and input format included in documentation.
v1.0.0
- Initial release of Bluepages address-identity lookup skill. - Enables querying wallet address <> Twitter/Farcaster identity mappings. - Supports single and batch lookups via various tools (e.g., check_address, get_data_for_address, batch_get_data). - Allows two authentication options: API key (recommended) or pay-per-request with PRIVATE_KEY and USDC. - Cost-efficient workflow tips and rate limits included.
Metadata
Slug bluepages
Version 1.0.2
License —
All-time Installs 2
Active Installs 2
Total Versions 4
Frequently Asked Questions

What is Bluepages?

Look up wallet address <> Twitter/Farcaster identity mappings via Bluepages.fyi. Use when asked who owns a wallet, finding addresses for a Twitter/Farcaster... It is an AI Agent Skill for Claude Code / OpenClaw, with 1185 downloads so far.

How do I install Bluepages?

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

Is Bluepages free?

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

Which platforms does Bluepages support?

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

Who created Bluepages?

It is built and maintained by jesse-pallok (@jesse-pallok); the current version is v1.0.2.

More Skills
self-improving agent
Captures learnings, errors, and corrections to enable continuous improvement. Use when: (1) A command or operation fails unexpectedly, (2) User corrects Clau...
⬇ 463283 · by pskoett
Skill Vetter
Security-first skill vetting for AI agents. Use before installing any skill from ClawdHub, GitHub, or other sources. Checks for red flags, permission scope, and suspicious patterns.
⬇ 259410 · by spclaudehome
Polymarket
Query Polymarket prediction markets. Check odds, find trending markets, search events, track price movements.
⬇ 232503 · by joelchance
Self-Improving + Proactive Agent
Self-reflection + Self-criticism + Self-learning + Self-organizing memory. Agent evaluates its own work, catches mistakes, and improves permanently. Use when...
⬇ 200423 · by ivangdavila
Github
Interact with GitHub using the `gh` CLI. Use `gh issue`, `gh pr`, `gh run`, and `gh api` for issues, PRs, CI runs, and advanced queries.
⬇ 191115 · by steipete
ontology
Typed knowledge graph for structured agent memory and composable skills. Use when creating/querying entities (Person, Project, Task, Event, Document), linkin...
⬇ 190156 · by oswalpalash

💬 Comments