> For the complete documentation index, see [llms.txt](https://docs.nosto.com/techdocs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.nosto.com/techdocs/quick-start-guide/readme/what-nosto-needs.md).

# What Nosto needs

Fundamentally, Nosto needs a replica of the client's product catalog with price and currency information, parent/child relations, categories, custom fields, tags, stock/inventory information, etc..

To achieve the onsite functionalities, Nosto must be able to do these things:

1. Know on which page the users are.
2. Know what data is on a page (what product, what category, …).
3. Know specific things about the current user (on all pages):
   * Shopping cart content
   * Name and email (if logged in)
4. Know about certain events like impressions and clicks.
5. Write content to the page, either from the client- or server side.
6. Access your frontend: [Our crawler must be whitelisted](https://help.nosto.com/en/articles/586911-nosto-s-bot-crawler-s-header-agent-details), you must provide valid product URLs and product images.


---

# 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://docs.nosto.com/techdocs/quick-start-guide/readme/what-nosto-needs.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.