> For the complete documentation index, see [llms.txt](https://sharelink-docs.toss.im/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://sharelink-docs.toss.im/help/operations.md).
# 운영 안내
쉐어링크 활동 시 지켜야 할 운영 정책을 확인해요.
쉐어링크 활동 시 지켜야 할 기준은 운영 정책에서 확인해 주세요. 이벤트·수수료 정보는 이용 가이드 탭의 공지사항에서 안내해요.
{% hint style="warning" %}
운영 정책을 위반하면 수익금 지급이 보류되거나 계약이 해지될 수 있어요. 권장 문구와 표시 위치는 [대가성 문구 표시 가이드](/disclosure/disclosure.md)에서 확인해 주세요.
{% endhint %}
---
# 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://sharelink-docs.toss.im/help/operations.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.