> For the complete documentation index, see [llms.txt](https://docs.archisketch.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.archisketch.com/guide/dev-kr/builder/shopby.md).

# 2. 샵바이(Shop by)

아키스케치는 NHN 샵바이 공식 빌더사로 아래의 기능들을 제공합니다.

## 아키스케치 ↔️ 샵바이 가이드

**아키스케치**는 **NHN 샵바이의 공식 빌더사**로서, **샵바이(Shop by)**와 연동된 다양한 기능을 제공합니다.

### 📌 앱스토어 방문하기 👉 [여기 클릭](https://apps.nhn-commerce.com/apps/1637)

![](https://3169559498-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F1FgwWAdGTNDn40D9mxww%2Fuploads%2Fgit-blob-10e545878c615a3a910aeb21cfba561a6b83cb7f%2Fshopby_README-1.png?alt=media)

### 📌 목차

| 제목                            | 가이드 URL                                                                                          |
| ----------------------------- | ------------------------------------------------------------------------------------------------ |
| **1. 샵바이: 앱(App) 설치 방법**      | [2.1. 샵바이: 앱(App) 설치 방법](/guide/dev-kr/builder/shopby/installation.md)              |
| **2. 샵바이: 앱(App) 버튼 꾸미기**     | [2.2. 샵바이: 앱(App) 버튼 꾸미기](/guide/dev-kr/builder/shopby/app-button.md)                |
| **3. 샵바이: 모델 뷰어 삽입하기(Embed)** | [2.3. 샵바이: 모델 뷰어 삽입하기(Embed)](/guide/dev-kr/builder/shopby/model-viewer-embed.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 by asking a question.

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

```
GET https://docs.archisketch.com/guide/dev-kr/builder/shopby.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.