> For the complete documentation index, see [llms.txt](https://ticketking.xyz/docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://ticketking.xyz/docs/ko/premium.md).

# 프리미엄

- [요금제 및 가격](https://ticketking.xyz/docs/ko/premium/plans-and-pricing.md): Ticket King 무료 및 프리미엄에서 제공되는 내용.
- [Premium 전용 기능 목록](https://ticketking.xyz/docs/ko/premium/feature-list.md): 프리미엄으로 해제되는 모든 기능과 모든 서버에서 무료인 항목.
- [구독하기](https://ticketking.xyz/docs/ko/premium/subscribing.md): 서버를 프리미엄으로 업그레이드하는 방법.
- [구독 관리](https://ticketking.xyz/docs/ko/premium/managing-your-subscription.md): 구독을 확인, 취소, 이전하는 방법.
- [서버가 더 이상 Premium이 아니면 어떻게 되나요](https://ticketking.xyz/docs/ko/premium/no-longer-premium.md): 프리미엄이 종료될 때 무엇이 바뀌고 무엇이 바뀌지 않는지.


---

# 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://ticketking.xyz/docs/ko/premium.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.