> For the complete documentation index, see [llms.txt](https://support.cregis.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://support.cregis.com/cregis-wallet-guide/zh-tw/deveoper-and-payment-engine/manual/disable_and_delete.md).
# 禁用及刪除項目
用戶在刪除項目前需要先禁用地址，您可以參考以下操作找到入口。
點擊禁用後會有提示視窗，確認完成需要進行Google驗證。
成功禁用後可看禁用標籤，然後可以根據以下操作找到刪除項目的入口。
**請注意刪除後數據是不可恢復的，刪除後即釋放了該項目所使用的地址數。**
點擊刪除後會有提示視窗，確認後需進行Google驗證，驗證後即完成刪除。
---
# 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.cregis.com/cregis-wallet-guide/zh-tw/deveoper-and-payment-engine/manual/disable_and_delete.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.
