> 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/who-can-use-anedot.md).

# Who Can Use Anedot?

Anedot accepts applications from U.S.-based nonprofits, churches, ministries, political campaigns, and schools. Every application needs an EIN and an address.

**Anedot** accepts fundraising account applications from U.S.-based organizations. This article lists the organization types we work with and the basic requirements every application must meet.

## Eligible Organizations

Anedot accepts applications from:

* Nonprofit organizations
* Churches and ministries
* Political campaigns and committees
* Colleges, universities, and schools

## Basic Requirements

* Every application requires a valid **United States Tax ID (EIN)** and a physical address.
* Anedot only accepts applications from **U.S.-based** organizations.
* Organizations that aren't tax-exempt may need additional verification by our team.

## Related Articles

* [What Do I Need to Apply for an Account?](https://docs.anedot.com/get-started/apply-for-an-account/what-do-i-need-to-apply-for-an-account.md)
* [Anedot Application](https://docs.anedot.com/get-started/apply-for-an-account/anedot-application.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.anedot.com/get-started/anedot-101/who-can-use-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.
