> For the complete documentation index, see [llms.txt](https://wiki.altinyonca.net/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://wiki.altinyonca.net/partner-programi/mevcut-partnerlerimiz-and-basvuru.md).

# Mevcut Partnerlerimiz & Başvuru

AltınYonca bünyesindeki resmi içerik üreticileri ve başvuru adımları.

**Resmi Partnerlerimiz**

Aşağıdaki içerik üreticileri resmi AltınYonca Partner Programı bünyesinde yer almakta ve düzenli olarak sunucumuzda canlı yayın yapmaktadır:

| **Yayıncı**  | **Platform** | **Kanal Bağlantısı**                           |
| ------------ | ------------ | ---------------------------------------------- |
| Helmetfull   | Kick         | [Kanalı İncele](https://kick.com/helmet-full)  |
| MartianDerox | Kick         | [Kanalı İncele](https://kick.com/martianderox) |
| BeckyTBM     | Kick         | [Kanalı İncele](https://kick.com/beckytbm)     |

**Nasıl Başvurulur?**

Kriterleri sağladığınızı düşünüyorsanız:

1. Resmi Discord Sunucumuza katılın.
2. Destek bileti (Ticket) kanalından talebi oluşturun.
3. Kanal bağlantınızı, yayın saatlerinizi ve oyun içi kullanıcı adınızı form olarak iletin.
4. Başvurunuz yönetim ekibimiz tarafından en geç 48 saat içinde incelenip yanıtlanacaktır.


---

# 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://wiki.altinyonca.net/partner-programi/mevcut-partnerlerimiz-and-basvuru.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.