> For the complete documentation index, see [llms.txt](https://help.listly.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.listly.io/docs/zh-hans/support/faq/1.-fu-kuan-yu-tui-kuan-shuo-ming/ke-yi-zhi-ding-yue-yi-ge-yue-ma.md).

# 可以只订阅一个月吗？

可以。您可以根据需要订阅任意时长，并随时取消。订阅 Listly 服务一个月后，您可以在「付款信息」页面取消自动续费。如果您在订阅到期前取消续订，订阅将不会自动续期，也不会产生额外费用。


---

# 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://help.listly.io/docs/zh-hans/support/faq/1.-fu-kuan-yu-tui-kuan-shuo-ming/ke-yi-zhi-ding-yue-yi-ge-yue-ma.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.