> For the complete documentation index, see [llms.txt](https://ceogolfclub.gitbook.io/ceo/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://ceogolfclub.gitbook.io/ceo/benefit.md).

# 회원의 혜택

- [한 눈에 보는 회원의 혜택](https://ceogolfclub.gitbook.io/ceo/benefit/benefits.md): 즐겁게 누리고 교류하는 비즈니스 리더들의 네트워크
- [비즈니스 컨시어지](https://ceogolfclub.gitbook.io/ceo/benefit/business.md): 회원간 비즈니스 협력 기회 발굴 및 안내
- [깔끔한 주선, 쾌적한 라운딩](https://ceogolfclub.gitbook.io/ceo/benefit/rounding.md): 나에게 맞는 동반자 매칭과 라운딩 초청
- [비즈니스 골프 매칭](https://ceogolfclub.gitbook.io/ceo/benefit/undefined.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://ceogolfclub.gitbook.io/ceo/benefit.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.