> For the complete documentation index, see [llms.txt](https://docs.maker.co/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.maker.co/maker-greatstore/get-started/what-is-greatstore.md).

# What is Greatstore

Greatstore is an AI shopping assistant that lives on your storefront. It can search your catalogue, answer questions from documents you give it, and render interactive components inside the chat.

<figure><img src="/files/eZOYcbzxS3DoBbxzY9VG" alt="The admin home — credits, activity, the setup checklist, and weekly insights"><figcaption><p>The admin home — credits, activity, the setup checklist, and weekly insights</p></figcaption></figure>

## Your store, your admin

Every store gets its own admin at **`<your-slug>.greatstore.ai/admin`**. Sign-in uses your **Maker Nav account** — whoever is an admin of the store's organization in Nav can access the Greatstore admin, and inviting teammates happens through Nav's organization management, not in Greatstore itself.

{% hint style="info" %}
Stores are currently provisioned by the Greatstore team — there's no self-serve sign-up yet. Once your store exists, everything in these docs applies.
{% endhint %}

## Two halves

{% columns %}
{% column width="50%" %}
**The admin**, at your store's `/admin`. Where you set the brand and persona, add knowledge, wire up connectors, manage apps, and read back conversations, insights and usage.
{% endcolumn %}

{% column width="50%" %}
**The storefront**, your own site. One script tag puts the assistant there. Shoppers chat with it while they browse.

See [The shopper experience](/maker-greatstore/get-started/the-shopper-experience.md).
{% endcolumn %}
{% endcolumns %}

## What the assistant can draw on

| Source       | Gives it                                                         | Set up in                                                                  |
| ------------ | ---------------------------------------------------------------- | -------------------------------------------------------------------------- |
| Connectors   | Products it can search and look up                               | [How connectors work](/maker-greatstore/connectors/how-connectors-work.md) |
| Knowledge    | Policies, shipping, sizing, care — anything not in the catalogue | [Adding sources](/maker-greatstore/knowledge/adding-sources.md)            |
| Apps         | Components it can render instead of plain text                   | [How apps work](/maker-greatstore/apps/how-apps-work.md)                   |
| Page context | What the shopper is looking at right now                         | [JavaScript API](/maker-greatstore/developer-reference/javascript-api.md)  |

## What you get back

Conversations are recorded under **Chats**, summarised into weekly insights, and metered under **Usage** — credits, conversations, shoppers, messages, and voice minutes.

See [Reading chats](/maker-greatstore/insights-and-usage/chats.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 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.maker.co/maker-greatstore/get-started/what-is-greatstore.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.