Skip to main content
GET
https://api.credprotocol.com
/
api
/
v2
/
score
curl -X GET "https://api.credprotocol.com/api/v2/score/?address=vitalik.eth,0x742d35Cc6634C0532925a3b844Bc9e7595f0Ab17" \
  -H "Authorization: Bearer YOUR_API_KEY"
{
  "address": [
    "0xd8dA6BF26964aF9D7eEd9e03E53415D37aA96045",
    "0x742d35Cc6634C0532925a3b844Bc9e7595f0Ab17"
  ],
  "score": 806,
  "decile": 6,
  "range": "good",
  "model_version": "andromeda_1.0",
  "timestamp": "2024-01-15T10:30:00Z"
}

Overview

Returns a single aggregated credit score for multiple Ethereum addresses, combining individual scores into one unified value. This is useful for multi-signature wallets, joint accounts, or portfolio-wide credit assessments.
Unlike the batch endpoint which returns individual scores, this endpoint aggregates all addresses into a single combined score.

Query Parameters

address
string
required
Comma-separated list of Ethereum addresses or ENS names (e.g., address=0x123...,0x456...,vitalik.eth)

Response

address
array
Array of resolved Ethereum addresses (checksummed)
score
integer
Aggregated credit score between 300 and 1000 (mean of individual scores)
decile
integer
Aggregated score decile from 1 to 10
range
string
Score range: low, fair, good, very_good, or excellent
model_version
string
The scoring model version (currently andromeda_1.0)
timestamp
string
ISO 8601 timestamp when the score was calculated

Aggregation Method

The aggregated score is calculated as the mean of all individual address scores:
  1. Each valid address is scored individually using the Andromeda model
  2. Invalid addresses are skipped (logged as warnings)
  3. The final score is the arithmetic mean of all valid scores
  4. Decile and range are derived from the aggregated score

Use Cases

  • Multi-signature Wallets: Assess the combined creditworthiness of all signers
  • Joint Account Holders: Evaluate combined credit for shared wallets
  • Organization Assessment: Score a company’s treasury across multiple wallets
  • Portfolio Credit Rating: Get a single score representing an entire portfolio

Comparison: Aggregated vs Batch

FeatureAggregated (/score/)Batch (/score/batch/)
OutputSingle combined scoreArray of individual scores
Use CasePortfolio-wide assessmentPer-wallet analysis
Response SizeSmallLarger (scales with addresses)
curl -X GET "https://api.credprotocol.com/api/v2/score/?address=vitalik.eth,0x742d35Cc6634C0532925a3b844Bc9e7595f0Ab17" \
  -H "Authorization: Bearer YOUR_API_KEY"
{
  "address": [
    "0xd8dA6BF26964aF9D7eEd9e03E53415D37aA96045",
    "0x742d35Cc6634C0532925a3b844Bc9e7595f0Ab17"
  ],
  "score": 806,
  "decile": 6,
  "range": "good",
  "model_version": "andromeda_1.0",
  "timestamp": "2024-01-15T10:30:00Z"
}

Performance

  • Response Time: Typically 3-5 seconds (addresses scored in parallel)
  • Caching: Individual address scores are cached for 5 minutes