> For the complete documentation index, see [llms.txt](https://docs.anedot.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.anedot.com/get-started/anedot-101/about-anedot.md).

# About Anedot

Anedot is a donation and fundraising platform for U.S.-based nonprofits, churches, ministries, and political campaigns.

Anedot is a donation and fundraising platform for U.S.-based not-for-profit organizations. We work with nonprofits, churches, ministries, political campaigns, and education institutions. Tools help you collect donations, manage donor data, and optimize giving across web, mobile, and email.

Founded by CEO Paul Dietzel, Anedot has been trusted by thousands of organizations since 2010 and has processed billions of dollars in donations. We are a fully remote, U.S.-based team. Our tagline is “Here to Help”—human support plus features such as one-click giving, customized landing pages, and integrations with tools you already use.

## What Does “Anedot” Mean — and How Do You Say It?

The name is inspired by two words:

* **Antidote** — a remedy or cure
* **Anecdote** — a short, interesting story about a real event or person

It is also an anagram of **donate** (ANEDOT ↔ DONATE).

Pronounce it with the long “O” from *donate*: **A-neh-doat** (rhymes with *antidote*).


---

# 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.anedot.com/get-started/anedot-101/about-anedot.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.