Build with Glacier21.

You can be calling the API in about ninety seconds.

1. Create a free account and verify your email. Every account ships with 10 free wallet lookups, no credit card.
2. Mint an API key on the API keys page. The full key value is shown exactly once. Copy it and store it somewhere private.
3. Call the endpoint. The example below returns every column the platform has on Vitalik's primary address.

curl -X POST https://api.glacier21.com/v1/wallet \
  -H "Content-Type: application/json" \
  -H "X-API-Key: $GLACIER21_API_KEY" \
  -d '{"wallet": "0xd8da6bf26964af9d7eed9e03e53415d37aa96045"}'

The endpoint accepts EVM and Solana addresses. The chain is detected automatically. Database-cached results return in under 100 ms; cold scrapes typically resolve in 3 to 8 seconds.

Every request to https://api.glacier21.com/v1/wallet must include an X-API-Key header. Keys are minted and revoked from the dashboard. Each key is bound to one account and counts against that account's monthly quota.

X-API-Key: g21_live_4f8c...d2a1
Content-Type: application/json

The dashboard UI itself uses a short-lived Bearer JWT issued by POST /auth/login. That flow is documented in the OpenAPI spec; for direct API consumption you only need the API key.

The wallet lookup endpoint is the core of the API. Send an address; receive a unified profile that merges on-chain attribution with off-chain identity signals.

Request body

{
  "wallet": "string",            // required: an EVM (0x...) or Solana address
  "columns": [
    // Identity
    "wallet", "identity", "tags", "aka", "legalName", "bios",
    "location", "associations", "socialHandles", "emailAddress",
    "phoneNumber", "dateOfBirth",
    // Owned things
    "ownedAssets", "domain", "holdings", "nft", "profileUrl",
    // Documents
    "associatedDocuments", "documentDescription",
    // Sanctions / law enforcement
    "sanctionedBanned", "sanctionList", "sanctionReason",
    "lawEnforcement",
    // Exploits
    "exploitHack", "exploitDescription", "exploitType",
    "exploitAmount", "exploitRole", "exploitName",
    // Context
    "relationship", "verification", "communication", "misc"
  ]
}

columns is optional. Omit it to receive the full profile. Include only the columns you need to reduce response size on high-volume integrations. The Lambda always reads the entity once from DynamoDB, so requesting fewer columns has no effect on query cost or latency, only on response payload. See the column reference below.

Every column is best-effort. When we have no data for a column on a given address, we omit it from the response rather than returning null noise.

The response is a JSON object with a message string and a data array. The array always contains exactly one entry for the requested address.

{
  "message": "Wallet found",
  "data": [
    {
      "wallet": "0xd8da6bf26964af9d7eed9e03e53415d37aa96045",
      "identity": "Vitalik Buterin",
      "tags": ["co-founder", "ethereum"],
      "aka": ["vitalik.eth", "VitalikButerin"],
      "bios": ["Co-founder of Ethereum. Writes at vitalik.eth.limo."],
      "location": "Switzerland",
      "associations": ["Ethereum Foundation"],
      "socialHandles": {
        "twitter": "https://x.com/VitalikButerin",
        "github":  "https://github.com/vbuterin",
        "website": "https://vitalik.eth.limo"
      },
      "ownedAssets": ["vitalik.eth", "vitalik.eth.limo"],
      "misc": ["ENS primary: vitalik.eth"]
    }
  ]
}

Source attribution

Responses are served from our cache when fresh data exists. When the cache is cold or stale, the lookup transparently runs live scrapers in parallel, writes the result back to the cache, and returns the merged profile in the same request. Whether a given response was a cache hit or a fresh scrape is logged but not surfaced in the response body.

The API uses standard HTTP status codes. Errors return a JSON body with a message field describing what went wrong.

Monthly quotas track to your plan. You can monitor consumption in real time on /usage.

Glacier21 publishes a full agent-native surface so autonomous agents can find, understand, and pay for the API without a human in the loop. Point your agent or MCP-aware client at the URLs below.

The MCP endpoint at https://dashboard.glacier21.com/api/mcp speaks JSON-RPC 2.0 over Streamable HTTP (MCP protocol 2025-06-18). Paid operations declare prices via x-payment-info in the OpenAPI spec and a matching https://dashboard.glacier21.com/api/x402/subscribe challenge endpoint for x402 payment.

Stuck on something the docs don't answer? We answer email fast.