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 credit scores for multiple Ethereum addresses in a single API call. This is more efficient than making individual requests when you need to score multiple addresses.
Maximum of 100 addresses per batch request.
Query Parameters
Comma-separated list of Ethereum addresses or ENS names (e.g., address=0x123...,0x456...,vitalik.eth)
Response
Array of score results for each address
The resolved Ethereum address (checksummed)
Credit score between 300 and 1000
Score decile from 1 to 10
Score range: low, fair, good, very_good, or excellent
The scoring model version (currently andromeda_1.0)
ISO 8601 timestamp when the score was calculated
Total number of scores returned
Use Cases
- Portfolio Analysis: Score all addresses in a user’s portfolio
- Batch Verification: Check creditworthiness of multiple counterparties
- Risk Assessment: Evaluate a list of addresses for lending decisions
curl -X GET "https://api.credprotocol.com/api/v2/score/batch/?address=vitalik.eth,0x742d35Cc6634C0532925a3b844Bc9e7595f0Ab17" \
-H "Authorization: Bearer YOUR_API_KEY"
{
"scores": [
{
"address": "0xd8dA6BF26964aF9D7eEd9e03E53415D37aA96045",
"score": 847,
"decile": 7,
"range": "very_good",
"model_version": "andromeda_1.0",
"timestamp": "2024-01-15T10:30:00Z"
},
{
"address": "0x742d35Cc6634C0532925a3b844Bc9e7595f0Ab17",
"score": 765,
"decile": 5,
"range": "good",
"model_version": "andromeda_1.0",
"timestamp": "2024-01-15T10:30:00Z"
}
],
"count": 2
}
- Response Time: Typically 2-5 seconds for 10 addresses, longer for larger batches
- Caching: Individual address scores are cached for 5 minutes
- Parallelization: Requests are processed in parallel for optimal performance
Batch requests count as multiple API calls against your quota (one per address).