Skip to main content
GET
Get Score Breakdown

Overview

Retrieve a detailed breakdown of a user’s ZKScore across all 8 scoring categories. This endpoint provides granular insights into how the total score is calculated, including individual category scores, weights, and historical comparisons.
The breakdown helps users understand which areas contribute most to their score and where they can improve.

Parameters

string
required
ZKS ID (e.g., alice.zks) or wallet address (e.g., 0x742d35Cc...)
number
Specific chain ID to get breakdown for (optional, defaults to aggregated across all chains)
boolean
Include historical comparison data (default: false)

Response

boolean
Indicates if the request was successful
string | null
The ZKS ID (without .zks suffix), or null if not set
string
The primary wallet address
object

Examples

Response Example

Category Details

1. Activity Score (Max: 1500)

Measures transaction frequency and consistency:
  • Daily/weekly transaction patterns
  • Consistency over time
  • Active months/years
  • Transaction regularity

2. Volume Score (Max: 2000)

Measures total transaction volume:
  • Cumulative transaction value
  • Average transaction size
  • Largest transactions
  • Volume growth rate

3. Age Score (Max: 1000)

Measures wallet longevity:
  • Days since first transaction
  • Maturity level (new/intermediate/veteran)
  • Historical presence
  • Continuous activity

4. Diversity Score (Max: 1500)

Measures protocol and chain diversity:
  • Number of unique protocols used
  • Number of chains interacted with
  • Category spread (DeFi, NFT, Gaming, etc.)
  • Exploration behavior

5. Governance Score (Max: 1200)

Measures DAO participation:
  • Proposals voted on
  • DAOs participated in
  • Voting power held
  • Governance token holdings

6. Social Score (Max: 1000)

Measures social reputation:
  • Attestations received
  • Trusted connections
  • Community reputation
  • Social verifications

7. Risk Score (Max: 800)

Measures risk management:
  • Security practices
  • Risk incidents avoided
  • Safety measures implemented
  • Smart contract interactions

8. Loyalty Score (Max: 2000)

Measures long-term engagement:
  • Longest activity streak
  • Average hold time for assets
  • Return rate to protocols
  • Consistent participation

Use Cases

1. Score Visualization

Display breakdown in a dashboard:

2. Improvement Recommendations

Suggest areas for improvement:

3. Progress Tracking

Track score changes over time:

4. Comparative Analysis

Compare with network averages:

Best Practices

1. Cache Breakdown Data

Breakdown data changes infrequently:

2. Visualize Category Performance

Use charts for better understanding:

3. Highlight Strengths and Weaknesses

Troubleshooting

”Identity not found”

Cause: The identity doesn’t exist or hasn’t been activated. Solution:
  • Verify the identity exists
  • Ensure the identity is activated
  • Check for typos in the ZKS ID

”Insufficient data”

Cause: Not enough transaction history to calculate breakdown. Solution:
  • User needs more on-chain activity
  • Some categories may show 0 if no relevant activity
  • Breakdown becomes more accurate over time

”Historical data unavailable”

Cause: Historical comparison data not yet available. Solution:
  • Historical data requires at least 30 days of activity
  • Try again after more time has passed
  • Use includeHistory=false if not needed

Performance Tips

  1. Cache Results: Breakdown data changes slowly, cache for 15+ minutes
  2. Request Only When Needed: Don’t fetch on every page load
  3. Use Pagination: For displaying multiple users, batch requests
  4. Optimize Rendering: Render charts efficiently with libraries like Chart.js

Rate Limits

Score breakdown requests are subject to rate limits:
  • Free tier: 30 requests per minute
  • Starter tier: 150 requests per minute
  • Professional tier: 600 requests per minute
  • Enterprise tier: Custom limits