bluepages

What This Skill Does

The Bluepages skill empowers your OpenClaw agent to bridge the gap between anonymous Ethereum addresses and real-world social identities. By leveraging the Bluepages.fyi database, the agent gains access to a verified repository of over 800,000 mappings connecting Ethereum wallet addresses to Twitter/X handles and Farcaster profiles. This skill allows your agent to perform identity attribution, verify wallet ownership, and query social data associated with specific on-chain activities. It provides granular tools to check if an address exists in the registry, retrieve full identity details, and handle batch processing for large-scale analysis, ensuring your agent can contextualize web3 interactions with social provenance.

Installation

To integrate this skill into your environment, run the following command in your terminal: clawhub install openclaw/skills/skills/jesse-pallok/bluepages

Ensure you have the Bluepages MCP server set up by executing npx -y github:bluepagesdoteth/bluepages-mcp. For authentication, you must configure either an API key (recommended for cost-efficiency) or a PRIVATE_KEY (for x402 pay-per-request). If providing a private key, strictly adhere to security best practices by using a dedicated, funded-only-as-needed agent wallet to mitigate risks.

Use Cases

• Attribution: Identify the Twitter or Farcaster owner behind a specific wallet address when auditing transactions.
• Social Verification: Cross-reference suspicious wallet activity against known public identities.
• Campaign Analytics: Perform batch lookups to map large lists of campaign contributors to their social media handles.
• User Onboarding: Dynamically identify users by their wallet address to personalize agent interactions based on their public social profile.

Example Prompts

1. "Check if the wallet address 0x123...456 is linked to any Twitter handle."
2. "Who is the owner of the Farcaster account associated with this 0x address?"
3. "Run a batch check on these 50 wallet addresses and pull the full identity data for any matches found."

Tips & Limitations

To maximize cost efficiency, always adopt a two-phase lookup strategy. Start with the lightweight check_address or check_twitter tools (1 credit) to verify if data exists before committing to a full data fetch (50 credits). This avoids unnecessary expenditure on address misses. For large datasets, leverage the _streaming tool variants to maintain agent responsiveness and monitor progress. Note that accuracy is limited to the Bluepages.fyi database coverage; addresses not yet verified or linked by users in that specific dataset will not return results. Always handle API keys securely and monitor your credit usage via check_credits.