> For the complete documentation index, see [llms.txt](https://support.corostw.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://support.corostw.com/coros-warranty/repair-price.md).
# 付費維修價格
以下為新台幣含稅價
| 款式 | 更換螢幕 | 更換旋鈕 | 更換主機板 | 更換電池 | 整機更換 |
|---|
| APEX 系列 | | | | | |
| APEX 42mm | 停止維修 | 停止維修 | 停止維修 | 停止維修 | 停止維修 |
| APEX 46mm | 2,200 | 1,000 | 2,800 | 900 | 3,150 |
| APEX Pro | 2,400 | 1,000 | 1,800 | 1,900 | 4,800 |
| APEX 2 | 2,400 | 1,600 | 2,700 | 1,900 | 5,300 |
| APEX 2 Pro | 2,900 | 1,600 | 3,200 | 2,500 | 6,200 |
| PACE 系列 | | | | | |
| PACE 2 | 停止維修
請聯繫客服 | 停止維修
請聯繫客服 | 停止維修
請聯繫客服 | 停止維修
請聯繫客服 | 停止維修
請聯繫客服 |
| PACE 3 | 2,100 | 1,100 | 2,300 | 1,600 | 3800 |
| PACE 4 | 1,800 | 1,100 | 2,300 | 1,600 | 3,800 |
| PACE Pro | 2,400 | 1,800 | 2,700 | 1,900 | 4300 |
| VERTIX 系列 | | | | | |
| VERTIX | 2,700 | 1,600 | 2,600 | 2,500 | 5,400 |
| VERTIX 2 | 3,800 | 2,200 | 4,900 | 2,900 | 6,500 |
| VERTIX 2S | 3,800 | 2,200 | 4,900 | 2,900 | 6,800 |
| 自行車錶系列 | | | | | |
| DURA | 2,800 | 2,600 | 3,300 | 2,800 | 3,800 |
| 訓練感測器 | | | | | |
| POD 2 | | | 2,300 | | |
| HRM | | | 2,550 | | |
| 速度感測器 | | | 500 | | |
| 踏頻感測器 | | | 500 | | |
---
# 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://support.corostw.com/coros-warranty/repair-price.md?ask=&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.