> 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/scenario-a.md).

# Scenario A: Manage Your Own Vaults

You're managing DCVs for yourself — treasury, own product, or direct client use. The technical surface is small: one off-chain prerequisite (KYC + whitelisting), a handful of on-chain calls, and the Public API for reporting.

This scenario is organized in the order you'll actually do things:

1. [**Prerequisites: KYC & Whitelisting**](https://docs.tesseract.fi/dedicated-client-vaults/integration-guide/scenario-a/prerequisites.md) — how your wallet gets on the on-chain whitelist.
2. [**Deploying a Vault**](https://docs.tesseract.fi/dedicated-client-vaults/integration-guide/scenario-a/deploying-a-vault.md) — a single transaction against a Vault Deployer.
3. [**Deposits**](https://docs.tesseract.fi/dedicated-client-vaults/integration-guide/scenario-a/deposits.md) — adding capital to an existing vault.
4. [**Instant Withdrawals**](https://docs.tesseract.fi/dedicated-client-vaults/integration-guide/scenario-a/instant-withdrawals.md) — single-transaction withdrawals covered by liquid balance.
5. [**Scheduled Withdrawals**](https://docs.tesseract.fi/dedicated-client-vaults/integration-guide/scenario-a/scheduled-withdrawals.md) — the three-step flow for larger amounts.
6. [**Strategy Assignment**](https://docs.tesseract.fi/dedicated-client-vaults/integration-guide/scenario-a/strategy-assignment.md) — signing an EIP‑712 message to assign a strategy to a fresh vault.
7. [**Reading Vault Data**](https://docs.tesseract.fi/dedicated-client-vaults/integration-guide/scenario-a/reading-vault-data.md) — using the Public API (and the on-chain ERC‑4626 interface) for reporting.

Throughout, code examples are in TypeScript with [viem](https://viem.sh). The same operations work equally well from ethers.js, foundry-cast, Python web3, or any Ethereum tooling — the contracts are standard.

Canonical addresses and method signatures are in [Reference](https://docs.tesseract.fi/dedicated-client-vaults/reference.md).


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

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

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.
