> For the complete documentation index, see [llms.txt](https://docs.cosmik.network/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.cosmik.network/semble/home/faq.md).

# FAQ

Frequently asked questions about Semble

<details>

<summary>What types of content can I share on Semble? Is it only for academic research?</summary>

While we call Semble a "social knowledge network for researchers," we take an expansive view of what "research" means. Semble is designed to be a home for any kind of bookmarking - not just formal academic research, but anyone sharing, curating, organizing, and exploring knowledge!

Rather than restricting content types, we're evolving the feed from purely chronological to more configurable and personalized. This means you'll be able to tailor your experience according to your interests.

Our first step in this direction is the **media types filter** (rolling out soon), which will let you filter for specific content types - like formal research papers if that's your focus, or podcasts, videos, and other media types based on your preferences.

</details>


---

# 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.cosmik.network/semble/home/faq.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.
