> For the complete documentation index, see [llms.txt](https://hello.kodadot.xyz/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://hello.kodadot.xyz/about-us/alpha-products/web3-merchandise-shop.md).

# Web3 merchandise shop

want let your brand be connected with audience in digital and physical space?

As OGs, we are aware that there were many attempts to launch cryptocurrency shops. However, most of them were uninteresting, with only the Layer1 logo on display. In our case, we have taken advantage of the opportunity to create unique branding for our events and showcase distinctive designs at each conference. Moreover, we have started collaborating with artists and communities. Our merchandise aims to showcase premium designs from artists in our marketplace and support the community. Early adopters who partner with us will benefit from being featured in our shop.

Barely two months in since our February 2023 launch and BOOM - we hit the century mark! That's how we define success.

[Read more about Merchandise shop and find testimonials there](/fandom-toolbox/merchandise-shop.md)


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://hello.kodadot.xyz/about-us/alpha-products/web3-merchandise-shop.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.