> 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-zh/ding-dan-bang-zhu/zhi-jie-mian-xiang-xiao-fei-zhe-xiao-shou/mei-guo-zhi-zao-cai-liao.md).

# 美国制造材料

## 优质材料，就在美国本土制造

我们进军美国制造业的扩张，源于我们对可持续发展和持续创新的承诺。我们专注于开发环保解决方案和尖端材料，赋能创作者并减少对环境的影响，同时支持本地产业。

<figure><img src="https://1102955884-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FA2YI9GFoVmpURdSqt1Vr%2Fuploads%2Fgit-blob-53d4899a203619ad7923945b6c7f1a0b83cc3da7%2FPolymaker_-_Demo_-_Final.mp4.01_04_35_00.Still007_700x.webp?alt=media" alt=""><figcaption></figcaption></figure>

### 我们现在所在的位置与未来方向

目前，我们约有 10% 的 SKU 在美国制造，重点是我们最畅销的材料。这只是我们迈向更高本地化生产之旅的开始。到 2025 年，我们计划让 10-15% 的产品线实现国内生产，以提升供应可得性和供应链效率。

Polymaker 的目标是在五年内让 70-80% 的 SKU 在美国生产，并由全自动化生产线提供支持。这一增长将意味着新增 100 多条挤出生产线，并为 100 多名员工创造就业岗位，使 Polymaker 成为美国本土 3D 打印材料领域的领导者。

### 目前在美国制造的材料

PolyLite™ PLA - 白色、黑色、灰色、红色、绿色、黄色、橙色、紫色

PolyLite™ PLA Pro - 白色、黑色、灰色、红色、蓝色、橙色、蓝绿色

PolyLite™ PETG - 白色、黑色、灰色、红色、黄色、蓝色、橙色、半透明

PolyLite™ ABS - 黑色、白色、灰色

PolyLite™ ASA - 黑色、白色、灰色、黄色

**美国制造声明\***

虽然我们正在努力提高我们在大休斯顿地区的制造产出， *但我们不能保证所有订单都能 100% 美国制造。* 本页展示的核心产品线目前正在美国生产，不过在我们扩大运营的同时，部分其他材料仍然是进口的。

## 与 Loyal Moses 一起参观我们的工厂

{% embed url="<https://www.youtube.com/watch?v=bS0hTtDYVuU>" %}


---

# 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-zh/ding-dan-bang-zhu/zhi-jie-mian-xiang-xiao-fei-zhe-xiao-shou/mei-guo-zhi-zao-cai-liao.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.
