> For the complete documentation index, see [llms.txt](https://docs.tesseract.fi/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.tesseract.fi/dedicated-client-vaults/integration-guide/indexing-vaults.md).

# Indexing Vaults

Two different needs, two different answers.

### You just need your own vaults (or your users' vaults)

If all you care about is "give me the vaults for this wallet address, or for this list of wallet addresses" — use the Public API. No indexing, no event processing, no node operations required.

* `POST /vaults/query/by-client-addresses` takes a list of wallet addresses and returns the vaults owned by each.
* `GET /vaults/{vault}` returns full detail for a single vault.

See [Reading Vault Data](/dedicated-client-vaults/integration-guide/scenario-a/reading-vault-data.md) for a walkthrough and [Reference → Public API](/dedicated-client-vaults/reference/public-api.md) for the full endpoint list.

### You want to index every vault ever created

If you need a local view of all vaults created by Tesseract — for partner-wide dashboards, analytics, third-party data services, or anything you don't want routed through our API — index the on-chain `VaultDeployed` event.

* One event per vault, emitted by the [Vault Deployer](/dedicated-client-vaults/reference/contract-addresses.md#vault-deployers-one-per-supported-asset) for each asset.
* The event exposes the new vault's address and its associated manager contracts (access manager, fee manager, withdraw manager, etc.).
* Event schema: [Reference → Contract Methods → Vault Deployer](/dedicated-client-vaults/reference/contract-methods.md#vault-deployer-per-asset).

There is one deployer per supported asset (USDC / WETH / WBTC), so the indexer needs to watch all three contract addresses.

Once you have the vault address, everything else is standard — ERC‑4626 views on the vault, the vault's `WithdrawManager` for scheduled withdrawals, and the Public API for performance / decoded history.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.tesseract.fi/dedicated-client-vaults/integration-guide/indexing-vaults.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.