> For the complete documentation index, see [llms.txt](https://developers-apps-in-toss.toss.im/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://developers-apps-in-toss.toss.im/guide/operation.md).

# 운영

- [미니앱 등록하기](https://developers-apps-in-toss.toss.im/guide/operation/console-workspace.md)
- [미니앱 테스트하기](https://developers-apps-in-toss.toss.im/guide/operation/toss.md): 앱 번들(.ait) 파일을 업로드하고 생성된 테스트용 앱스킴으로 토스 앱에서 최종 테스트를 할 수 있어요.
- [미니앱 버전 관리하기](https://developers-apps-in-toss.toss.im/guide/operation/deploy.md): 출시한 뒤에는 앱인토스 콘솔에서 버전 관리와 업데이트를 할 수 있어요. 필요에 따라 새 번들을 올리거나, 기존 버전을 유지·관리할 수 있어요.
- [사업자 등록하기](https://developers-apps-in-toss.toss.im/guide/operation/register-business.md): 이 문서에서는 사업자 등록이 왜 필요한지, 어떻게 등록하는지를 안내해요.
- [주요 기능 등록하기](https://developers-apps-in-toss.toss.im/guide/operation/function.md): 주요 기능은 사용자가 비게임 미니앱 상세에서 특정 기능으로 바로 들어올 수 있게 해주는 기능이에요. 홈 화면을 거치지 않고 원하는 세부 기능으로 바로 이동해요.
- [대표관리자 변경하기](https://developers-apps-in-toss.toss.im/guide/operation/undefined.md)
- [미성년자 참여하기](https://developers-apps-in-toss.toss.im/guide/operation/console-minor.md)
- [긴급 점검 설정하기](https://developers-apps-in-toss.toss.im/guide/operation/check.md)
- [서비스 종료하기](https://developers-apps-in-toss.toss.im/guide/operation/service-termination.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 dynamically by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://developers-apps-in-toss.toss.im/guide/operation.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 `build a script that syncs our docs to a CMS` 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.