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

# 欢迎来到 Story.fun

Story.fun 将作品观看与作品代币连接起来。你可以了解作品、查看更新安排，并按作品的观看方式开始播放；也可以买卖作品关联的代币。

## 开始观看

* 免费作品：已发布的内容无需连接钱包即可观看。
* 持币观看作品：连接并验证钱包后，相关代币的当前美元价值达到作品门槛，即可观看已开放的内容。

持币观看不消耗、质押或锁定你的代币。观看资格随当前持仓价值变化，并不是购买一次就永久有效的门票。

## 先了解作品，再决定参与

作品页的观看方式、关联代币、发布安排和当前开放状态，决定你能看什么、何时能看。代币可以交易，不代表作品已经开播；持仓达标也不能提前观看未发布内容。

购买代币前，请查看交易费用、价格影响和作品发布条件。代币价格可能变化，交易与观看均不保证回报。

[查看观看规则](/storyfun.launchpad-docs/protocol/viewing-access.md) · [开始使用](/storyfun.launchpad-docs/integration/overview.md) · [了解风险](/storyfun.launchpad-docs/protocol/risk-disclosures.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://storyfun-launchpad.gitbook.io/storyfun.launchpad-docs/protocol/overview.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.