zScore Docs
  • Core
    • What is zScore
    • How It Works
    • Operational Mechanics
  • For Operators
    • Mainnet
      • Quickstart (Mainnet)
      • Registration (Mainnet)
  • For Protocols
    • Overview
    • zPass
      • Getting Started
      • API Reference
        • Get zScore by Wallet
        • Get Wallets zScore
        • Get Wallets by Protocol
        • Get Protocol Risk Clusters
        • Get wallet analytics by protocol
        • Get Global Protocol Analytics
Powered by GitBook
On this page
  1. For Protocols
  2. zPass
  3. API Reference

Get Wallets zScore

Wallet discovery and filtering API for reputation-based targeting

PreviousGet zScore by WalletNextGet Wallets by Protocol

Discover and filter wallets based on zScore reputation for targeted campaigns, risk assessment, and user segmentation.

Primary Uses:

  • Campaign targeting and user acquisition

  • Lending risk assessment and pool curation

  • Bot filtering and sybil detection

  • User segmentation and growth analytics

Score Ranges:

  • 0-200: High risk wallets (new wallets, potential bots)

  • 200-400: Medium risk wallets (moderate activity)

  • 400-600: Good reputation wallets (active DeFi users)

  • 600-800: High reputation wallets (power users)

  • 800-1000: Excellent reputation wallets (whales, veterans)

Returns: Paginated list of wallets with zScore ratings (0-1000 scale)

Get wallets by zScore range

get

Returns a paginated list of wallets filtered by zScore reputation range and sorted by score.

Authorizations
Query parameters
limitnumber · min: 1 · max: 1000Optional

Maximum number of wallets to return per request.

Default: 100Example: 100
min_scorenumber · max: 1000Optional

Minimum zScore threshold for filtering wallets. Use 300+ for lending, 200+ for campaigns, 400+ for VIP targeting.

Default: 175Example: 300
max_scorenumber · max: 1000Optional

Maximum zScore threshold for filtering wallets.

Default: 325Example: 400
ascbooleanOptional

Sort order by zScore. true = ascending (lowest first), false = descending (highest first).

Default: trueExample: false
Header parameters
x-api-keystringRequired

API key for authentication

Default: cf1cec687fe2938f62d6b53b460b0db9998f64ef612e974980cff8423597ec93
Responses
200
Successfully retrieved wallet list with zScores.
application/json
400
Bad request - invalid parameters
application/json
401
Unauthorized - invalid or missing API key
429
Rate limited - too many requests
get
GET /zpass/api/zscore/wallets HTTP/1.1
Host: api.myzscore.ai
x-api-key: cf1cec687fe2938f62d6b53b460b0db9998f64ef612e974980cff8423597ec93
Accept: */*
{
  "wallets": [
    {
      "walletAddress": "0xca60b689f76b265418a8d5fe6cf42b8cca17c0aa",
      "zscore_f": 100.40774556525164
    },
    {
      "walletAddress": "0x8660a214c427e1a5710e6cb612b2094c9c9ce4ea",
      "zscore_f": 100.54586111318362
    }
  ]
}