> ## Documentation Index
> Fetch the complete documentation index at: https://docs.alterscope.org/llms.txt
> Use this file to discover all available pages before exploring further.

# Pre-Deposit Vault Due Diligence

> Screen a lending vault before you deposit — composition, oracle soundness, curator track record — through the API.

Before capital goes into a vault, you want to know what it holds, whether its price oracles are sound, and who is managing it. This workflow assembles that picture from the API.

## The workflow

<Steps>
  <Step title="Inspect the vault's composition and health">
    `GET /v2/vault/{vaultId}/health` and `GET /v2/vault/{vaultId}/markets` return the vault's current health and the markets it allocates into — so you see concentration and what the vault is actually exposed to.
  </Step>

  <Step title="Classify the oracle behind each market">
    For each underlying market, `GET /v2/oracle/{marketId}/classification` (with `…/classification-history` and `…/edge-cases`) reports how the price oracle is wired and whether it can be trusted right now. A market is only as safe as the feed pricing it — see [Oracle classification](/trust/methodology/oracle-classification).
  </Step>

  <Step title="Check the curator's track record">
    `GET /v2/curators/{addr}/track-record` (plus `…/fee-history`, `…/allocations`, `…/cap-timeline`) and `GET /v2/vault/{vaultId}/governance/timeline` show who curates the vault, how they've managed risk and fees over time, and what governance actions they've taken.
  </Step>

  <Step title="Cross-check the independent risk score">
    `GET /v2/pool/{poolId}/risk-scores` returns Alterscope's reconstructions of published peer methodologies for the pool, as an independent second opinion. Read what each score means and doesn't on the [Pool risk scores](/trust/methodology/pool-risk-scores) page.
  </Step>
</Steps>

## What you learn

A go/no-go view: is the vault concentrated where you don't want it, is any underlying oracle unverifiable, and does the curator's history match the risk you're taking? Every response carries [freshness and quality](/trust/data/freshness-and-quality) metadata, so you know the data behind the decision is current.

See the full request/response detail in the [API reference](/api-reference/overview), and confirm the vault is covered via the [coverage manifest](/trust/data/coverage-and-gaps).