> 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/creator-and-identity-data.md).

# Creator & identity data

This page explains how Basket associates baskets with creator identities.

### Identity mapping

Each basket can be mapped to a creator identity linked through Privy and X.

### What developers may read

Developer-facing identity fields are `TBD`.

Expected fields can include creator handle, creator profile metadata, and basket ownership mapping.

### Why it matters

Identity is part of the product surface.

It lets wallets, explorers, and discovery apps show who stands behind a basket.

***

### Likely public fields

| Field                    | Why it matters                |
| ------------------------ | ----------------------------- |
| Creator handle           | Primary public attribution    |
| Basket list              | Shows the creator's products  |
| Managed status by basket | Shows where discretion exists |
| Public descriptions      | Helps explain the strategy    |

### Data hygiene

If identity data is cached or indexed, Basket should document refresh behavior and source of truth once finalized.


---

# 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/creator-and-identity-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.