> 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/developers-and-api/reading-basket-data.md).

# Reading basket data

This page explains the main basket data a developer may want to read.

### On-chain reads

Developers can verify basket token supply, pool holdings, and B20 event activity directly on-chain.

### Indexed reads

Basket may expose indexed reads for composition, NAV, holdings, and creator metadata.

Those endpoints are `TBD` until published.

### What to verify directly

If you are evaluating collateralization, check live pool holdings and token supply.

Those are the core backing signals.

### Data model notes

NAV depends on asset balances plus a pricing method.

Exact price-source methodology is `TBD` and should be documented before public API release.

***

### Read types

| Read                     | Why you want it           |
| ------------------------ | ------------------------- |
| Basket metadata          | Show strategy context     |
| Constituents and weights | Show intended composition |
| Live holdings            | Verify actual backing     |
| Supply                   | Compute per-token claim   |
| NAV                      | Show fair-value reference |

### On-chain versus indexed reads

On-chain reads are best when you need hard verification.

Indexed reads are best when you need speed, pagination, aggregation, or historical views.


---

# 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/developers-and-api/reading-basket-data.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.