> For the complete documentation index, see [llms.txt](https://help.stibee.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.stibee.com/paid-newsletter/settings.md).

# 유료 구독 주소록 설정하기

💬 이 내용은 **스탠다드, 프로, 엔터프라이즈 요금제**에 해당하는 도움말입니다.

## 이 글에서는

스티비 유료 구독 주소록을 통해 유료 뉴스레터 구독 신청을 받을 수 있습니다. 유료 구독 주소록과 구독 폼을 생성하는 방법과 구독료를 변경하는 방법, 그리고 각 구독 상품의 특징에 관해 알아봅니다.

{% content-ref url="/pages/YosdWHp0wE4SLLuAT1T3" %}
[유료 구독 주소록 만들기](https://help.stibee.com/paid-newsletter/settings/create.md)
{% endcontent-ref %}

{% content-ref url="/pages/NfBShklLrmNBVvYoXrvE" %}
[구독 상품 이해하기: 월간, 연간, 일회성](https://help.stibee.com/paid-newsletter/settings/monthly-yearly-one-time.md)
{% endcontent-ref %}

{% content-ref url="/pages/eJbLQmfxeJx1yb6yVtgN" %}
[유료 구독 폼 설정하기](https://help.stibee.com/paid-newsletter/settings/subscription-form.md)
{% endcontent-ref %}

{% content-ref url="/pages/ITlO0jkcyeB5GeCkFmXL" %}
[유료 뉴스레터 구독료 변경하기](https://help.stibee.com/paid-newsletter/settings/subscription-fee.md)
{% endcontent-ref %}

{% content-ref url="/pages/BwwDnHAvQOgXCsmDZPMT" %}
[일반 주소록 → 유료 구독 주소록으로 변환하기](https://help.stibee.com/paid-newsletter/settings/convert.md)
{% endcontent-ref %}


---

# 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.stibee.com/paid-newsletter/settings.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.
