> 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/overview.md).

# Overview

This page shows what developers can read, verify, and integrate without guessing the system model.

### Queryable data

Developers should be able to read:

* Basket composition
* Target weights
* Pool holdings
* Basket supply
* NAV inputs
* Creator identity mapping
* Mint and burn activity

### Where data lives

Some data lives on-chain.

Some convenience reads may be exposed through product APIs that are still `TBD`.

### Integration paths

Use on-chain reads when you need direct verification.

Use Basket APIs when you need indexed or aggregated views.

### Integration map

| Need                  | Best source                 |
| --------------------- | --------------------------- |
| Verify token supply   | On-chain                    |
| Verify pool balances  | On-chain                    |
| Show creator metadata | Basket API or indexed layer |
| Show basket lists     | Basket API or indexed layer |
| Explain supply events | Event indexing plus memos   |

{% columns %}
{% column %}

#### On-chain reads

Use these for supply, holdings, and permissions.
{% endcolumn %}

{% column %}

#### Basket API

Use this for discovery, creator metadata, and pre-aggregated views.
{% endcolumn %}
{% endcolumns %}

### Identity and creator data

Basket links baskets to X identities through Privy.

That mapping is part of the product surface, not just marketing metadata.

Integrators should treat creator identity, official status, and managed status as important fields.

### Investment and redemption integration

Programmatic integrations need quote, route, and execution surfaces.

Exact interfaces are still `TBD`.

The core economic flow is stable:

1. route input to WETH
2. acquire constituents
3. mint against backing

Redemption reverses that flow.

### Events and memos

Mint and burn events explain when supply changed.

Memos help explain why it changed.

That matters for analytics, portfolio views, and issuance history.

### Who this section is for

This section is for wallets, aggregators, data platforms, and technical reviewers.

If you only need product usage, the investor and creator sections are the better starting point.


---

# 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/overview.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.