> For the complete documentation index, see [llms.txt](https://docs.propw.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.propw.com/help-center/help-center-ko/readme.md).
# 도움말 센터
무엇을 찾는 데 도움을 드릴까요?
PropW 챌린지에 참여하기
| | | |
|---|
:leaf: | 시작하기 | 기본 사항에 대한 도움 받기 | 시작하기 |
:plug: | PropW 거래 규칙 | PropW 거래 규칙에 대해 알아보기 | PropW 거래 규칙 |
:money-bill-wave: | 청구서 및 결제 | 청구 관련 도움 받기 | 청구 및 결제 |
:heart: | 커뮤니티 | 우리 커뮤니티에 참여하세요 | 커뮤니티 |
:computer-mouse: | 계정 관리 | 계정을 관리하세요 | 계정 관리 |
:bullhorn: | 제품 업데이트 | 새로운 소식을 확인하세요 | 제품 업데이트 |
---
# 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://docs.propw.com/help-center/help-center-ko/readme.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.