> For the complete documentation index, see [llms.txt](https://docs.allforclimate.earth/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.allforclimate.earth/collectives/conditions-for-applying.md).

# Conditions for applying

Only very few conditions to apply to be hosted by All for Climate, but here they are:

1. You are a collective, citizen initiative or movement working towards a more sustainable and just future. We welcome a broad range of efforts that support ecological and social well-being.
2. The activities of your collective have a non-profit purpose.
3. You agree to our [principle and values](/principles-and-values.md).
4. You are based in Europe. Since the bank account is based in Belgium, you can only collect euros. International payouts within Europe are not a problem. 
5. When you apply, add at least a second person as an admin of your collective. We advice a team of 3 or 4 administrators. Make sure you have a gender balance in the administrator team.
6. You are willing to participate in the general assemblies of AllForClimate, organised 2 to 3 times a year. Any member of your collective can join, it does not have to be one of the administrators.


---

# 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.allforclimate.earth/collectives/conditions-for-applying.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.