# IXS Tokenized Vault Info

> IXS Tokenized Vault Info is a paid API for AI agents from api-dev-v2.ixs.finance, paid per call via x402, $0.01/call, status unknown (last checked 2026-09-14).

Returns detailed metadata for a single IXS ERC-4626 tokenized vault, including contract address, chain, status, symbol, metrics, and underlying asset info.

## Facts

- Endpoint: GET https://api-dev-v2.ixs.finance/x402/vaults/:vaultId/info
- Price: $0.01/call
- Payment: x402
- Status: unknown
- Last checked: 2026-09-14
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/api-dev-v2-ixs-finance-eea25a89
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_qsJI7txW2X7wfXPS3gACk

Status and success rate cover calls made through Zero and Zero's own probes. Third-party monitors may report differently.

## How to call it through Zero

Zero handles the 402 payment challenge and records the run. With the Zero CLI installed (`npm i -g @zeroxyz/cli`):

```sh
zero fetch --capability api-dev-v2-ixs-finance-eea25a89
```

Example prompt: Pull up the full details for the IXS vault at contract address 0x974AbbD28E6c1752f7816E7F15cA3Bf9989A8D4C on Base (chain 8453) — I need the vault name, status, symbol, underlying asset, and any on-chain metrics.

## When to prefer this

Use this endpoint when you need rich metadata for a specific IXS/InvestaX vault and you already have a vault identifier (MongoDB ID, route ID, or contract address). Prefer this over the catalog endpoint when you only need details for one vault and want to minimize cost and response size.

## Known failure modes

- Invalid or unknown vaultId returns a not-found error
- Malformed contract address causes a 400 bad request
- Vault exists but metrics are null if on-chain data is unavailable
- Route ID with unsupported chainId returns an error
- Network outage or upstream subgraph downtime may cause partial data or 500 error

## How this service works

Vault details — NAV, underlying asset, chain, and whitelist status

## Output

Returns a JSON object with ok:true and a data object containing the vault's MongoDB ID, routeId, name, contractAddress, chainId, network slug, chain display name, status (active/inactive), ERC-20 symbol, logo URL, block explorer URL, subgraph endpoint, on-chain performance metrics (if available), and underlying asset details.

## Example request

```json
{
 "input": {
  "type": "http",
  "method": "GET",
  "pathParams": {
   "vaultId": "0x974AbbD28E6c1752f7816E7F15cA3Bf9989A8D4C"
  }
 }
}
```

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "$schema": "https://json-schema.org/draft/2020-12/schema",
 "required": [
  "input"
 ],
 "properties": {
  "input": {
   "type": "object",
   "required": [
    "type",
    "method"
   ],
   "properties": {
    "type": {
     "type": "string",
     "const": "http"
    },
    "method": {
     "enum": [
      "GET"
     ],
     "type": "string"
    },
    "pathParams": {
     "type": "object",
     "required": [
      "vaultId"
     ],
     "properties": {
      "vaultId": {
       "type": "string",
       "examples": [
        "69e587a2a631785cb319f3f7",
        "8453-0x974abbd28e6c1752f7816e7f15ca3bf9989a8d4c",
        "0x974AbbD28E6c1752f7816E7F15cA3Bf9989A8D4C"
       ],
       "description": "Vault identifier — accepts MongoDB ID (e.g. 69e587a2…), route ID (e.g. 8453-0x974a…), or contract address"
      }
     }
    },
    "queryParams": {
     "type": "object",
     "properties": {}
    }
   },
   "additionalProperties": false
  },
  "output": {
   "type": "object",
   "required": [
    "type"
   ],
   "properties": {
    "type": {
     "type": "string"
    },
    "example": {
     "type": "object"
    }
   }
  }
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/api-dev-v2-ixs-finance-eea25a89/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from api-dev-v2.ixs.finance](https://www.zero.xyz/host/api-dev-v2.ixs.finance/llms.txt)