# Other Partners

At Thrilld Labs, we prioritize partnerships that align with our core values of decentralization, the level playing field, and efficient and inclusive growth. 

Our partnerships are aimed to create value by connecting industry professionals, developers, investors, and service providers.

<details>

<summary><strong>Foundations and non-profits</strong></summary>

We proudly support organizations that advance the Web3 ecosystem, such as blockchain foundations, female-led crypto organizations, and nonprofits with a Web3 focus. By offering them space on Thrilld’s partner portal and collaborating more broadly, we help them promote grants, hackathons, and whatnot to the benefit of our community

</details>

<details>

<summary><strong>Web3 B2B companies</strong></summary>

Thrilld Labs partners with B2B companies that provide essential services in the Web3 space. All current partnerships are merit-based, yet in the near future we will offer these companies visibility through ad space on Thrilld and our other platforms.

</details>

<details>

<summary><strong>VCs, accelerators and incubators</strong></summary>

Thrilld Labs collaborates with reputable VCs and accelerators and incubators. These partnerships focus on connecting startups with funding opportunities through Thrilld. We ensure that these entities have strong reputations and provide meaningful support, avoiding partners that take equity without adding value.&#x20;

</details>

Reach out to our team at <info@thrilldlabs.io> or via the[ form on our website](https://docs.thrilld.io/partnerships/www.thrilldlabs.io/contact) to express your interest in becoming a partner.


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.thrilld.io/partnerships/other-partners.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.