> For the complete documentation index, see [llms.txt](https://basket-fund.gitbook.io/basket.fund-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://basket-fund.gitbook.io/basket.fund-docs/introduction/why-basket.fun-exists.md).

# Why basket.fun exists

Crypto is full of smart people, strong opinions, and fast-moving opportunities.

But following conviction is still harder than it should be.

Most users discover ideas through X posts, private chats, Telegram groups, wallet tracking, screenshots, spreadsheets, or short-term calls. Even when the idea is good, execution is messy. The user still has to choose position sizes, find the right tokens, bridge funds, swap on different chains, track changes, and decide when to update or exit.

That creates a gap between discovering a thesis and actually following it.

basket.fun is built to close that gap.

Creators get a structured way to publish and manage their market views. Users get a simpler way to access those views without turning every idea into a manual trading workflow.

We are not trying to replace research. The thesis still matters. The creator still matters. The user still decides which basket to follow.

basket.fun only makes the execution layer cleaner.


---

# 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:

```
GET https://basket-fund.gitbook.io/basket.fund-docs/introduction/why-basket.fun-exists.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.