Skip to main content
GET

Overview

Returns the wallet’s positions at four dated points: today and 30, 60 and 90 days ago, summed across the covered chains. Each point separates what the wallet holds directly from what it has deposited in lending protocols, how much of that backs a loan, and how much it owes. Use it to see whether a wallet is levering up, deleveraging, or draining assets over the last quarter.
Balances and prices are read as of each point’s block, so a past point reflects that day’s prices, not today’s.
Cost: 6 Cred Units per request.

Path Parameters

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

Response

string
The resolved Ethereum address (checksummed)
string
ISO 8601 timestamp when the history was computed
string
complete when every chain answered at every point, otherwise partial
integer[]
Chains this endpoint cannot read (currently Celo, 42220). They are not part of any point.
integer[]
Present only when coverage is partial: chains the data provider could not answer for at one or more points
array
Four points, ordered today first
string
The point’s date (YYYY-MM-DD, UTC). Past points are taken at 00:00 UTC of that day; today’s point is the current block
integer
0, 30, 60 or 90
number | null
USD value of tokens held directly in the wallet, excluding lending receipt tokens and debt tokens
number | null
USD value of lending-protocol supply positions (Aave aTokens, Compound cTokens). These are the same tokens the summary report’s total_collateral_usd measures
number | null
Equal to deposit_usd while the wallet has debt at that point, otherwise 0: the deposits backing a loan
number | null
USD value of outstanding borrowing (Aave V3 Ethereum variable-debt tokens)
string
complete or partial for this point. When every covered chain is unavailable at a point, its four USD fields are null
array
One entry per covered chain: chain_id, the block_number the point was read at (null for a chain the wallet had not used yet, which contributes zeros), and the chain’s coverage at this point

How the fields relate

asset_in_wallet_usd + deposit_usd - debt_usd is the wallet’s net position at that point.

Data Sources

  • Balances: block-pinned wallet token balances
  • Prices: block-pinned prices; lending receipt and debt tokens are valued through their underlying asset at the same block, never through their own thin DEX pairs
  • Blocks: the last block at or before 00:00 UTC on each date, per chain

Supported Chains

Ethereum, Optimism, BNB Chain, Polygon, Base, Arbitrum, Avalanche, Linea and Robinhood Chain. Celo is listed in not_covered.

Use Cases

  • Leverage trend: compare debt_usd / collateral_usd across the four points
  • Deleveraging check: a falling debt_usd with stable deposits shows voluntary repayment
  • Asset drain: a falling asset_in_wallet_usd ahead of a credit decision
  • Underwriting context: pair with the credit score to size a facility on a quarter of history, not a snapshot

Performance

  • Response Time: 2–10 seconds for a wallet whose past points have not been read before (three past points per active chain); well under a second afterwards
  • Caching: past points are cached per wallet and day, today’s point and the assembled response for 5 minutes
  • Not billed: a 503 (no provider could answer) consumes no Cred Units