> For the complete documentation index, see [llms.txt](https://wiki.polymaker.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://wiki.polymaker.com/polymaker-wiki/polymaker-wiki-ko/undefined-2/where-to-buy/other-countries.md).

# 기타 국가

### 남미, 아프리카, 아시아, 호주 및 기타 지역

<a href="https://shop.polymaker.com/pages/country-unavailable" class="button primary">직접 판매 배송 가능 지역</a><a href="https://polymaker.com/find-a-reseller" class="button primary">리셀러</a>

<details>

<summary><strong>북미와 유럽 외 지역에서는 Fiberon™과 Panchroma™를 포함한 Polymaker 제품을 어디에서 구매할 수 있나요?</strong></summary>

리셀러 목록은 [여기](https://polymaker.com/find-a-reseller/)에서 확인할 수 있습니다.

거주 지역에서 리셀러를 찾기 어렵거나 도매 주문에 관심이 있다면 <Support@Polymaker.com> 으로 연락해 주세요.

사업 정보, 지역, 예상 주문 규모를 함께 알려 주세요.

</details>

<details>

<summary><strong>북미와 유럽 외 지역에서 Fiberon™과 Panchroma™를 포함한 Polymaker 제품을 도매나 대량으로 구매하려면 어떻게 해야 하나요?</strong></summary>

<Support@Polymaker.com> 으로 이메일을 보내 주세요.

사업 정보, 지역, 예상 주문 규모를 함께 알려 주세요.

</details>

<details>

<summary><strong>북미와 유럽 외 지역에서 리셀러가 되려면 어떻게 해야 하나요?</strong></summary>

<Support@Polymaker.com> 으로 이메일을 보내 주세요.

사업 정보, 지역, 필요 사항, 예상 주문 수량을 함께 알려 주세요.

</details>


---

# 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.polymaker.com/polymaker-wiki/polymaker-wiki-ko/undefined-2/where-to-buy/other-countries.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.