> For the complete documentation index, see [llms.txt](https://docs.pancakeswap.finance/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.pancakeswap.finance/kr/archive/legacy-products.md).

# 레거시 제품

레거시 제품의 진입점 및 참고 자료

* [NFT 마켓플레이스](https://pancakeswap.finance/nfts)
* ~~게이밍 마켓플레이스 (2023년 10월 17일)~~ 2025년 9월 18일 제거됨
* [Pottery](https://pancakeswap.finance/pottery) (2023년 11월 3일)
* [트레이딩 리워드](/kr/archive/legacy-products/archived-trading-reward.md) (2024년 8월 23일)
* [심플 스테이킹](https://pancakeswap.finance/simple-staking) (2025년 3월 10일)
* [PancakeSwap 퀘스트](/kr/archive/legacy-products/archived-pancakeswap-quest.md) (2025년 2월 28일)
* [리퀴드 스테이킹](https://pancakeswap.finance/liquid-staking)
* [팀 리더보드](https://pancakeswap.finance/teams)
* PancakeSwap 미니 프로그램
* [옵션](/kr/archive/legacy-products/archived-options.md)
* [LP 히스토리 페이지](https://pancakeswap.finance/farms/history)
* [포지션 매니저 ](/kr/archive/legacy-products/archived-position-manager.md)(2025년 6월 21일)
* [Polygon zkEVM](https://legacy-zkevm.pancakeswap.finance/liquidity/positions) (2025년 9월 30일)
* [브릿지](https://pancakeswap.finance/bridge) (2025년 11월 6일)
* [veCAKE 상환](https://pancakeswap.finance/cake-staking/redeem) (2026년 1월 15일)


---

# 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.pancakeswap.finance/kr/archive/legacy-products.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.