> For the complete documentation index, see [llms.txt](https://help.givechariot.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.givechariot.com/readme.md).
# Quick Start
Everything you need to understand, activate, and manage your Chariot account with confidence.
At Chariot, we’re redefining how nonprofits receive Donor Advised Fund (DAF) donations — making it faster, easier, and more secure than ever before. This Help Center is your go-to resource for understanding the tools, policies, and processes that power DAFpay, Chariot Deposit Accounts\* and your organization's dashboard experience.
Whether you're just getting started or managing day-to-day operations, you’ll find everything you need right here.
{% hint style="info" %}
If you can’t find what you’re looking for or need additional support, reach out to our team anytime at .
{% 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 dynamically by asking a question.
Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:
```
GET https://help.givechariot.com/readme.md?ask=&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 `build a script that syncs our docs to a CMS` 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.