> For the complete documentation index, see [llms.txt](https://docs.mailtrap.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.mailtrap.io/account-and-organization/billing/non-profit-and-open-source.md).

# Non-Profit and Open-Source

Mailtrap offers free plans and discounts for non-profit organizations and open-source initiatives. Learn how to activate non-profit benefits for your account.

We deeply appreciate the valuable work of non-profit organizations and open-source initiatives. To support your efforts, we offer the following benefits:

* **Email Sandbox** – Free access to the Team plan
* **Email API / SMTP** – Free access to the Basic 10K plan
* **Email Marketing** - Free access to the Essential 10K plan
* **Discounted Billing** – All other paid plans are available at a 50% discount

To activate a non-profit plan, please email us at **<support@mailtrap.io>** with the following:

1. A legal document verifying your non-profit or open-source status (e.g., a W-9 form or equivalent)
2. A brief note on which Mailtrap product(s) you intend to use

We look forward to helping your organization thrive.


---

# 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.mailtrap.io/account-and-organization/billing/non-profit-and-open-source.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.