> 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/implementing-nosto/implement-lim-skill-early-access/architecture-and-integration-overview.md).

# Architecture and integration overview

LIM's current architecture combines Nosto Semantic Search with the Core Recommendation Pipeline — Predictive, Semantic, and Visual AI, plus LLMs — to generate responses in real time. The system is horizontally scalable, built to serve high-volume traffic without degradation. LIM also respects all consent and privacy settings configured at the merchant level in Nosto.

#### Integration options

LIM can be integrated in two ways, depending on your system's architecture:

* [**REST API** ](/techdocs/implementing-nosto/implement-lim-skill-early-access/architecture-and-integration-overview/rest-api.md)— suited to direct backend or service-based integrations
* [**MCP (Model Context Protocol)** ](/techdocs/implementing-nosto/implement-lim-skill-early-access/architecture-and-integration-overview/mcp.md)— recommended for agent-native and LLM-driven systems

Both expose the same core capabilities and return equivalent outputs.


---

# 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/implementing-nosto/implement-lim-skill-early-access/architecture-and-integration-overview.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.