Skip to main content
GET
https://api.credprotocol.com
/
api
/
v2
/
score
/
{address}
curl -X GET "https://api.credprotocol.com/api/v2/score/vitalik.eth" \
  -H "Authorization: Bearer YOUR_API_KEY"

{
  "address": "0xd8dA6BF26964aF9D7eEd9e03E53415D37aA96045",
  "score": 847,
  "classification": "Excellent",
  "model": "andromeda",
  "cached": false,
  "timestamp": "2024-01-15T10:30:00Z"
}

​
Overview

Returns a credit score (300-1000) for the specified Ethereum address based on on-chain activity analysis.
Scores are calculated using the Andromeda scoring model and cached for 5 minutes.

​
Path Parameters

​
address
string
required
Ethereum address or ENS name (e.g., vitalik.eth or 0x742d35Cc6634C0532925a3b844Bc9e7595f0Ab17)

​
Response

​
address
string
The resolved Ethereum address (checksummed)
​
score
integer
Credit score between 300 and 1000
​
classification
string
Score classification: Low, Fair, Good, Very Good, or Excellent
​
model
string
The scoring model used (currently andromeda)
​
cached
boolean
Whether the response was served from cache
​
timestamp
string
ISO 8601 timestamp when the score was calculated

​
Score Ranges

Score RangeClassificationDescription
300-579LowLimited on-chain history or high-risk activity
580-669FairSome positive activity, room for improvement
670-739GoodSolid on-chain history
740-799Very GoodStrong creditworthiness indicators
800-1000ExcellentExceptional on-chain activity and history

​
Scoring Factors

The Andromeda model considers:
  • Wallet Age: How long the address has been active
  • Transaction History: Volume and frequency of transactions
  • DeFi Activity: Lending, borrowing, and liquidity provision
  • Asset Holdings: Token and NFT portfolio value
  • Repayment History: DeFi loan repayments and liquidations
curl -X GET "https://api.credprotocol.com/api/v2/score/vitalik.eth" \
  -H "Authorization: Bearer YOUR_API_KEY"

{
  "address": "0xd8dA6BF26964aF9D7eEd9e03E53415D37aA96045",
  "score": 847,
  "classification": "Excellent",
  "model": "andromeda",
  "cached": false,
  "timestamp": "2024-01-15T10:30:00Z"
}