> 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/polymaker/polycore-tm-pellets.md).

# PolyCore™ 펠릿

<figure><img src="https://content.gitbook.com/content/0XKp816hibEsjBQtrHfc/blobs/Gxe5RvJaXNKckqlekmp3/PC7014.JPG" alt=""><figcaption></figcaption></figure>

PolyCore™는 FGF(Fused Granular Fabrication)용 펠렛 기반 3D 프린팅 소재 제품군입니다.

Polymaker의 10년 이상 축적된 소재 압출형 3D 프린팅 경험을 바탕으로 개발되었습니다.

출력성이 우수하고, 대부분의 펠렛 압출식 3D 프린터와 폭넓게 호환됩니다.

특히 PolyCore™ 시리즈는 건축과 금형 같은 구체적인 활용 분야를 기준으로 설계된 것이 특징입니다.

<figure><img src="https://content.gitbook.com/content/0XKp816hibEsjBQtrHfc/blobs/6fvMlIbzY38v1nHxwbpo/Liuyun%20Bridge_ASA-3012.jpeg" alt=""><figcaption><p>실외 건축</p></figcaption></figure>

<figure><img src="https://content.gitbook.com/content/0XKp816hibEsjBQtrHfc/blobs/SHyGmQ11T0l2LuzB06GU/pellet%20print.png" alt=""><figcaption><p>실내 장식</p></figcaption></figure>

<figure><img src="https://content.gitbook.com/content/0XKp816hibEsjBQtrHfc/blobs/TdfEBvaklpA5HxqcTVKt/Concrete%20wall_ABS-5012.jpeg" alt=""><figcaption><p>저온 금형(상온 ~ 80℃)</p></figcaption></figure>


---

# 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/polymaker/polycore-tm-pellets.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.