Back to Details

bluepages

Compare original and translation side by side

🇺🇸

Original

English
🇨🇳

Translation

Chinese

Bluepages

Bluepages

800K+ verified Ethereum address <> Twitter/X mappings, plus Farcaster.
拥有80万+已验证的以太坊地址与Twitter/X身份映射，同时支持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.
需要Bluepages MCP服务器：
npx -y github:bluepagesdoteth/bluepages-mcp
，或直接调用API（见下文）。推荐使用MCP服务器来使用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
.
需要以下环境变量之一：
  • BLUEPAGES_API_KEY
    （推荐）——费用低20%，速率限制提升2倍。
  • PRIVATE_KEY
    ——用于x402按次付费的以太坊私钥（使用Base链上的USDC支付）。
安全提示：切勿使用主钱包私钥。如果提供
PRIVATE_KEY
，请使用专用的、仅按需充值的代理钱包。
如果使用私钥，你可以选择通过x402按次付费，或使用
get_api_key
和
purchase_credits
这两个MCP工具购买
BLUEPAGES_API_KEY
。
如果不使用私钥，用户需要前往bluepages.fyi/api-keys获取API密钥，并设置
BLUEPAGES_API_KEY
环境变量。

Tools (quick reference)

工具速查

ToolCostDescription
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 itemData for up to 50 items (x402: $2.00 flat/batch)
batch_check_streaming
same as batch_checkFor large lists (100+), shows progress
batch_get_data_streaming
same as batch_get_dataFor large lists (100+), shows progress
check_credits
freeCheck remaining credits (API key only)
set_credit_alert
freeSet low-credit warning threshold (API key only)
get_api_key
freeGet/create API key via wallet signature
purchase_credits
$5–$600 USDCBuy credits via x402 (PRIVATE_KEY only)
工具费用说明
check_address
1积分（0.001美元）检查地址是否存在对应数据
check_twitter
1积分（0.001美元）检查Twitter账号是否存在对应数据
get_data_for_address
50积分（0.05美元）获取地址的完整身份数据（无数据时免费）
get_data_for_twitter
50积分（0.05美元）获取账号的完整身份数据（无数据时免费）
batch_check
40积分（0.04美元）单次最多检查50个条目
batch_get_data
每个找到的条目40积分获取最多50个条目的数据（x402方式：批量固定费用2.00美元）
batch_check_streaming
与batch_check相同适用于大型列表（100+条目），支持进度更新
batch_get_data_streaming
与batch_get_data相同适用于大型列表（100+条目），支持进度更新
check_credits
免费查看剩余积分（仅支持API密钥）
set_credit_alert
免费设置低积分预警阈值（仅支持API密钥）
get_api_key
免费通过钱包签名获取/创建API密钥
purchase_credits
5–600 USDC通过x402购买积分（仅支持PRIVATE_KEY）

Input format

输入格式

  • Addresses: 0x-prefixed, 42-char hex. Case-insensitive.
  • Twitter handles: With or without 
    @
    .
  • 地址：以0x开头的42位十六进制字符串，大小写不敏感。
  • Twitter账号：带或不带
    @
    符号均可。

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.
  • 单次查询：先调用
    check_address
    /
    check_twitter
    （1积分），仅当存在数据时再调用
    get_data_*
    （50积分）。跳过检查步骤会在无数据时浪费积分。
  • 批量查询：始终分两步——先
    batch_check
    ，再仅对找到的条目调用
    batch_get_data
    。相比盲目获取所有数据，这能节省约90%的成本。
  • 大型列表（100+条目）：使用带
    _streaming
    后缀的工具变体，可查看进度更新。

Rate limits

速率限制

  • API Key: 60 req/min
  • x402: 30 req/min
  • Batch: max 50 items per request
  • API密钥：60次请求/分钟
  • x402：30次请求/分钟
  • 批量请求：每次最多50个条目

Alternative: Direct HTTP API

替代方案：直接调用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
bash
undefined
如果MCP不可用，可以直接调用API。身份验证方式取决于你的配置：
  • API密钥：在请求头中传递
    X-API-KEY
  • 私钥（x402）：接口会返回402状态码及支付详情；签名后在请求头中携带
    X-PAYMENT
    重新发送
bash
undefined

With API key

使用API密钥

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"
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](https://bluepages.fyi/docs.html)
curl -X POST "https://bluepages.fyi/batch/check"
-H "X-API-KEY: your-key" -H "Content-Type: application/json"
-d '{"addresses": ["0x...", "0x..."]}'

完整API文档：[bluepages.fyi/docs](https://bluepages.fyi/docs.html)