> For the complete documentation index, see [llms.txt](https://docs.aisuru.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.aisuru.com/en/frontend.md).

# 9. Frontend Documentation

The documentation covers three main Memori frontend integration libraries:

1. [**memori-api-client**](/en/frontend/client-api.md):
   * TypeScript client for interacting directly with the Memori APIs
   * Handles authentication, sessions, and API calls
   * Suitable for custom integrations and backend use
2. [**memori-webcomponent**](/en/frontend/web-component.md):
   * Standard web component usable in any HTML page
   * The simplest solution for quick integrations
   * No specific framework required
   * Configurable via HTML attributes
3. [**memori-react**](/en/frontend/react-component.md):
   * Dedicated React component
   * Offers greater flexibility and control
   * Supports custom layouts
   * Integrates natively into the React ecosystem

It also offers several ways to customize the style of the components — you can find them all [here](/en/frontend/style-and-customization.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.aisuru.com/en/frontend.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.