> 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/applications.md).

# 신청

- [신청서 개요](https://ticketking.xyz/docs/ko/applications/overview.md): 신청 및 가입을 위한, 티켓 패널의 대안인 검토 스타일.
- [신청 설계하기](https://ticketking.xyz/docs/ko/applications/designing-your-application.md): 애플리케이션 옵션의 모든 필드, 만나는 순서대로.
- [신청 페이지](https://ticketking.xyz/docs/ko/applications/the-applications-page.md): 애플리케이션을 읽고, 필터링하고, 처리하기 위한 대시보드 검토 대기열.
- [애플리케이션 제한 및 제약](https://ticketking.xyz/docs/ko/applications/limits-and-constraints.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 current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://ticketking.xyz/docs/ko/applications.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.