> For the complete documentation index, see [llms.txt](https://docs.mithril.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.mithril.ai/account-and-billing/mithril-referral-program.md).

# Mithril Referral Program

Give Mithril credits, get Mithril credits 🎁 \*

Refer organizations that would benefit from early access to Mithril, and once they are accepted, they will receive $500 in credits. Once an organization you refer spends at least $2,500 on Mithril, you will also receive $500 in credits as a thank-you!

## How it works

1. Have your referral request access to Mithril by submitting our [waitlist form](http://mlfoundry.com/waitlist) and adding your organization's name in the “How did you hear about Mithril?” field.
2. Once accepted off the waitlist, your referral will receive an invitation from Mithril to create an account, which will be pre-provisioned with $500 in credits.
3. Once the referred organization spends at least $2,500, your organization will receive $500 in credits.

Thank you for your support - we can't wait to continue building with you!

{% hint style="info" %}
*\*The referral program is subject to terms and conditions. Credits expire 3 months after issuance. The program does not apply to* Mithril *Institute partners.*
{% endhint %}

<br>


---

# 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.mithril.ai/account-and-billing/mithril-referral-program.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.
