Skip to main content
GET

Overview

Returns a comprehensive credit report including asset balances, NFT holdings, DeFi positions, and transaction history across multiple blockchain networks.
Reports aggregate data from 10+ supported networks and are cached for 5 minutes.

Path Parameters

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

Response

string
The resolved Ethereum address (checksummed)
object
Credit score summary
integer
Credit score between 300-1000
string
Score classification
object
Asset holdings across all networks
number
Total portfolio value in USD
array
List of token holdings
array
List of NFT holdings
object
DeFi positions and activity
array
Active DeFi protocol positions
number
Total value supplied to lending protocols
number
Total value borrowed from lending protocols
object
Transaction activity summary
string
Date of first transaction
integer
Total number of transactions
boolean
Whether the response was served from cache

Credit Events

The full report includes a credit_events section with the address’s lending-protocol event history. See Chains & Protocols for coverage.
string
The least complete coverage of any pool. complete means every pool’s history is complete and current.
object
Event counts across all covered pools: supply, withdraw, borrow, repay, liquidation
array
One entry per covered lending pool contract. Protocols with several markets on a chain (Compound) have one entry per market.
string
aave_v2, aave_v3, compound_v3 or compound_v2
string
Market name for protocols with several markets per chain (for example cUSDCv3, cDAI); null for single-pool protocols
boolean
Whether this pool’s repayments and liquidations count towards the score. false for a protocol still being validated: its events are shown but do not move the score.
integer
Chain the pool is deployed on
string
How complete the event history is for this pool. See the table below.
integer
The block the event history is complete through. null if the pool has not been read yet.
object
Event counts for this pool, by event type. A count is null for an event type that is not collected for the protocol (Compound V2 supply and withdraw), which is different from 0.
string
Timestamp of the earliest event, or null if there are none
string
Timestamp of the most recent event, or null if there are none
object
{"status": "not_applicable"} with a reason. Defaults are not observable on overcollateralized protocols.
object
{"status": "not_applicable"} with a reason
array
Lending protocols whose event history is not yet available, so that a missing record is not read as a clean one
boolean
Whether these events contribute to the address’s Cred Score

Coverage

The first report for an address with a long borrowing history may return pending while its events are read in the background, usually within a few seconds. Until coverage is complete, the counts, and any score that depends on them, may understate the address’s history. Check coverage before relying on count_repayments or count_liquidations. An incomplete report is never cached for more than 30 seconds.

Example

Supported Networks

Reports aggregate data from the following networks:

Performance

  • Response Time: Typically 3-10 seconds depending on activity
  • Caching: Results cached for 5 minutes per address