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

# Chiliz Greenhouse

Chiliz Greenhouse program: micro-grants, technical bounties, and mentorship for builders, plus the Greenhouse Hub showcase for SportFi projects.

As the home of SportFi, Chiliz Chain wants you to be successful, and has built the tools to help you fund your ideas, and showcase them.

## Chiliz Greenhouse

Chiliz Greenhouse is the space for builders, developers, and creators.

{% embed url="<https://greenhouse.chiliz.com/>" %}

It is a reward and incentive platform designed solely to fuel the creation of the Chiliz ecosystem.\
If you have the skills to contribute code, promote Chiliz, or provide feedback, this is your workspace.

Chiliz is targeted at the community:

* Access micro-grants, technical bounties, and creative content tasks.
* Get paid in $CHZ for your contributions (from fixing bugs to launching full-scale dApps).
* Work under the guidance of the Chiliz core team with mentorship that accelerates your project from concept to launch.

## Chiliz Greenhouse Hub

If the Greenhouse is where the work happens, the Hub is where the world sees it.

{% embed url="<https://greenhousehub.chiliz.com/>" %}

The Greenhouse Hub is the SportFi center that empowers the Chiliz community to discover what is being built. It is the connective tissue between the workspace and the expanding developer community.

The Hub is where you can:

* Browse a curated list of active bounties, projects, and community rewards.
* See the latest cutting-edge projects in Sports, NFTs, Esports, AI, and DAOs.
* Find your Web3 niche and be rewarded for engaging with the next big thing in sports.


---

# 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.chiliz.com/learn/about-chiliz-chain/chiliz-greenhouse.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.