> For the complete documentation index, see [llms.txt](https://guide.charityvest.org/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://guide.charityvest.org/for-donors/set-up-a-daf-for-a-client.md).

# For Financial Advisors

Launch a powerful, branded giving experience for clients.

We believe financial advisors are a trusted stakeholder in their clients' philanthropic journey.&#x20;

With [Charityvest for Advisors](https://www.charityvest.org/for-advisors), you can now launch a philanthropic program with a premier white-labeled DAF, custom investment options, automated operations, and collaborative giving resources for all clients. Visit our Advisor Prospective Partner Guide to learn more.

{% embed url="<https://advisorpartnerguide.charityvest.org/>" %}

{% hint style="info" %}
If you would like to explore how Charityvest for Advisors can serve as your firm's philanthropic practice, [request a demo on our website](https://www.charityvest.org/for-advisors) or contact our team at <info@charityvest.org>.
{% endhint %}


---

# 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://guide.charityvest.org/for-donors/set-up-a-daf-for-a-client.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.
