> For the complete documentation index, see [llms.txt](https://docs.trybasket.live/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.trybasket.live/baskets-and-discovery/exploring-baskets.md).

# Exploring baskets

This page explains how to scan baskets quickly and separate official products from creator products.

### What discovery should show

Every basket card or list item should make these fields obvious:

* creator identity
* fixed or managed status
* high-level thesis
* key holdings or category

### Official versus creator baskets

| Basket type | What it signals                          | Main question                             |
| ----------- | ---------------------------------------- | ----------------------------------------- |
| Official    | Basket curates the methodology           | Does the index design make sense?         |
| Creator     | An external creator curates the strategy | Does the strategy and creator make sense? |

### What to scan first

| Signal            | Why users care                             |
| ----------------- | ------------------------------------------ |
| Creator handle    | Identifies who stands behind the basket    |
| Official badge    | Distinguishes Basket-curated products      |
| Fixed or managed  | Shows whether the recipe can change        |
| Theme or category | Helps users filter strategies              |
| Major holdings    | Helps users sanity-check the thesis        |
| Fees              | Shows whether creator economics are active |

### Fast read flow

{% stepper %}
{% step %}

### Filter the basket type

Decide whether you want an official basket or a creator basket first.
{% endstep %}

{% step %}

### Check the trust model

Look for fixed versus managed before you care about the theme.
{% endstep %}

{% step %}

### Check the idea

Make sure the thesis, holdings, and category actually match.
{% endstep %}

{% step %}

### Open the detail page

Only click through after the basket already looks legible in discovery.
{% endstep %}
{% endstepper %}

### What a good discovery surface does

It helps users reject the wrong basket quickly.

It also helps the right basket explain itself in one scan.


---

# 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://docs.trybasket.live/baskets-and-discovery/exploring-baskets.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.