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

# Storychat

<figure><img src="/files/RaQShZskvuGMEGGzQWjc" alt=""><figcaption></figcaption></figure>

## Storychat

Welcome to Storychat!

Storychat is a next-generation comprehensive content platform where you can enjoy webtoons and web novels created through AI. Additionally, you can interact directly with characters within any story or even create your own AI characters.

Storychat aims to overcome the limitations of the traditional Web2 content market by leveraging AI and blockchain technology to offer a richer and more diverse array of content.

Storychat provides both consumable content, which can be explored through feeds, and interactive content that allows direct interaction with AI, encompassing a wide range of stories and characters across various universes.


---

# 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://storychat.gitbook.io/storychat/overview/what-we-do.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.