Score
Aggregated Credit Score
Get a single aggregated credit score for multiple Ethereum addresses
GET
Documentation Index
Fetch the complete documentation index at: https://docs.credprotocol.com/llms.txt
Use this file to discover all available pages before exploring further.
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
Comma-separated list of Ethereum addresses or ENS names (e.g.,
address=0x123...,0x456...,vitalik.eth)Response
Array of resolved Ethereum addresses (checksummed)
Aggregated credit score between 300 and 1000 (mean of individual scores)
Aggregated score decile from 1 to 10
Score range:
low, fair, good, very_good, or excellentThe scoring model version (currently
andromeda_1.0)ISO 8601 timestamp when the score was calculated
Aggregation Method
The aggregated score is calculated as the mean of all individual address scores:- Each valid address is scored individually using the Andromeda model
- Invalid addresses are skipped (logged as warnings)
- The final score is the arithmetic mean of all valid scores
- 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
| Feature | Aggregated (/score/) | Batch (/score/batch/) |
|---|---|---|
| Output | Single combined score | Array of individual scores |
| Use Case | Portfolio-wide assessment | Per-wallet analysis |
| Response Size | Small | Larger (scales with addresses) |
Performance
- Response Time: Typically 3-5 seconds (addresses scored in parallel)
- Caching: Individual address scores are cached for 5 minutes