> 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.md).

# Integration Guide

Step-by-step instructions for integrating Tesseract Dedicated Client Vaults into your own infrastructure.

Start with [**Choose Your Scenario**](/dedicated-client-vaults/integration-guide/choose-your-scenario.md) to pick the right path based on your business model. The rest of this guide is organized into two scenarios:

* [**Scenario A**](/dedicated-client-vaults/integration-guide/scenario-a.md) — you're managing vaults for yourself (treasury, own product). You onboard directly through Tesseract's compliance, your wallet gets whitelisted, and from there you deploy and operate vaults against the contracts directly.
* [**Scenario B**](/dedicated-client-vaults/integration-guide/scenario-b.md) — you're managing vaults on behalf of your own end users (custodian model). You become a Tesseract partner, align on a compliance model, onboard users through an M2M integration, and then run the same on-chain operations per-user.

Both scenarios converge on the same technical surface. Scenario B layers additional partnership and compliance steps on top of everything in Scenario A.

See also [**Indexing Vaults**](/dedicated-client-vaults/integration-guide/indexing-vaults.md) for data-consumer use cases — pulling vault lists for your own addresses via the Public API, or indexing every vault Tesseract creates on-chain.

For canonical addresses, method signatures, and API references used throughout this guide, see [Reference](/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.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.