Vault Detail

GET /v1/vault/{network}/{address}

Get full vault details including risk vectors, APR decomposition, audit status, snapshots, events, and rewards.

Path Parameters

Example

curl https://api.philidor.io/v1/vault/ethereum/0x8eB67A509616cd6A7c1B3c8C21D48FF57df3d458

Response

Includes all fields from the vault list, plus:

• risk_vectors — individual vector scores (asset, platform, governance)
• protocol_version, protocol_website, protocol_launch_date
• audit_status, auditors[], audit_date, audit_report_url
• is_immutable, timelock_seconds
• deployment_timestamp
• snapshots[] — historical TVL and APR data points
• events[] — curator actions, incidents, parameter changes
• rewards[] — reward token breakdown (symbol, APR, type)

Depositability fields

Every vault response — list, detail, batch, and scores — carries the depositability fields below. deposit_status is the canonical signal clients should read; the others provide raw values and operational metadata.

Why this matters. A vault can advertise 20%+ APY while refusing new deposits — the yield is on the existing position and new principal would revert. Always check deposit_status before routing capital.

Recommended logic for integrators:

function shouldRoute(vault: { deposit_status: 'open' | 'closed' | 'unknown' }): boolean {
  switch (vault.deposit_status) {
    case 'open':
      return true; // Verified on-chain right now
    case 'closed':
      return false; // Confirmed maxDeposit == 0 — deposit would revert
    case 'unknown':
      // Indexer hasn't probed this vault on-chain yet (typically Aave/Compound/
      // Uniswap, which aren't ERC-4626). Pick the policy that suits your risk
      // tolerance:
      //   - Conservative routers: skip until status is known.
      //   - Long-tail aggregators: include but do a pre-flight maxDeposit
      //     call from the user's wallet before composing the tx.
      return false;
  }
}

Why might deposit_status be unknown?

Tracking depositability changes

Every time the indexer's sync cycle flips a vault's confirmed is_depositable state from true → false or vice versa, a DepositabilityChange event is appended to the events feed. Subscribe to these via the events endpoint instead of polling vault detail every minute:

curl "https://api.philidor.io/v1/events?eventType=DepositabilityChange&severity=Warning&limit=20"

Severities map to direction:

• Warning — vault went from open → closed. Capital routed since the last cycle would now revert.
• Info — vault went from closed → open. Previously-skipped vault is now accepting deposits again.

The event payload carries { from: "open"|"closed", to: "open"|"closed" }. Null transitions (vault appearing for the first time or dropping out of the indexer's probe set) are not emitted — they're observability noise, not real depositability changes.

Per-protocol detection method:

GET /v1/vault/{network}/{address}/events

Get all events for a vault — incidents, parameter changes, allocation changes, curator actions.

Example

curl https://api.philidor.io/v1/vault/ethereum/0x8eB67A509616cd6A7c1B3c8C21D48FF57df3d458/events

Response

{
  "success": true,
  "data": [
    {
      "id": 1234,
      "event_type": "allocation_change",
      "severity": "info",
      "title": "Market allocation updated",
      "description": "Curator adjusted market weights",
      "tx_hash": "0x...",
      "block_number": 19500000,
      "occurred_at": "2026-02-20T10:00:00Z"
    }
  ]
}

GET /v1/vault/{network}/{address}/markets

Get market allocations for Morpho vaults. Returns collateral risk summary per lending market.

Example

curl https://api.philidor.io/v1/vault/ethereum/0x8eB67A509616cd6A7c1B3c8C21D48FF57df3d458/markets

Only returns data for Morpho protocol vaults. Returns 404 for non-Morpho vaults.

GET /v1/vault/{network}/{address}/strategies

Get strategy details for Yearn vaults. Returns sub-strategy breakdown from ydaemon.

Example

curl https://api.philidor.io/v1/vault/ethereum/0x.../strategies

Only returns data for Yearn protocol vaults.

GET /v1/vault/{network}/{address}/strategy

Get strategy information for Beefy vaults. Returns processed strategy with yield sources, risk flags, and APY.

Example

curl https://api.philidor.io/v1/vault/ethereum/0x.../strategy

Only returns data for Beefy protocol vaults.