Requirements
- Target platform
- OpenClaw
- Install method
- Manual import
- Extraction
- Extract archive
- Prerequisites
- OpenClaw
- Primary doc
- SKILL.md
Look up wallet address <> Twitter/Farcaster identity mappings via Bluepages.fyi. Use when asked who owns a wallet, finding addresses for a Twitter/Farcaster...
Look up wallet address <> Twitter/Farcaster identity mappings via Bluepages.fyi. Use when asked who owns a wallet, finding addresses for a Twitter/Farcaster...
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.
800K+ verified Ethereum address <> Twitter/X mappings, plus Farcaster.
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.
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.
ToolCostDescriptioncheck_address1 credit ($0.001)Check if address has datacheck_twitter1 credit ($0.001)Check if Twitter handle has dataget_data_for_address50 credits ($0.05)Full identity data for address (free if not found)get_data_for_twitter50 credits ($0.05)Full identity data for handle (free if not found)batch_check40 credits ($0.04)Check up to 50 items at oncebatch_get_data40 credits/found itemData for up to 50 items (x402: $2.00 flat/batch)batch_check_streamingsame as batch_checkFor large lists (100+), shows progressbatch_get_data_streamingsame as batch_get_dataFor large lists (100+), shows progresscheck_creditsfreeCheck remaining credits (API key only)set_credit_alertfreeSet low-credit warning threshold (API key only)get_api_keyfreeGet/create API key via wallet signaturepurchase_credits$5โ$600 USDCBuy credits via x402 (PRIVATE_KEY only)
Addresses: 0x-prefixed, 42-char hex. Case-insensitive. Twitter handles: With or without @.
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.
API Key: 60 req/min x402: 30 req/min Batch: max 50 items per request
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
Writing, remixing, publishing, visual generation, and marketing content production.
Largest current source with strong distribution and engagement signals.