> ## Documentation Index
> Fetch the complete documentation index at: https://docs.mareaalcalina.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Marea AI

> Marea AI is the in-product chat editor merchants use to build and edit their storefront. It is a merchant-facing feature, not a public API surface — this page explains the boundary.

# Marea AI

**Marea AI** is the conversational editor built into the Marea dashboard. A merchant opens a chat panel inside the storefront editor and asks for changes in plain language — "add a testimonials section", "change the colors to match this photo", "create a product for the IPA" — and Marea AI applies them to the storefront draft.

It is a **merchant-facing product feature**. It is **not** part of the public API, and you do not call it from an integration. This page exists so the boundary is explicit: if you are building against Marea, the surfaces below are yours; Marea AI is the merchant's.

## Marea AI vs. the developer surfaces

|               | Marea AI                            | Public API / MCP                                               |
| ------------- | ----------------------------------- | -------------------------------------------------------------- |
| Audience      | The merchant, in the dashboard      | Developers and AI agents you build                             |
| Interface     | Chat panel in the storefront editor | REST (`api.mareaalcalina.com`) + MCP (`mcp.mareaalcalina.com`) |
| Auth          | The merchant's dashboard session    | An `mk_dev_*` developer key                                    |
| Scope         | One storefront — the merchant's own | Any storefront your key is authorized for                      |
| Documented in | The in-product help, not here       | The rest of this site                                          |

Marea AI and the public API write the same storefront model — a change a merchant makes by chat and a change you make by `PATCH` land in the same place. They are two front doors to one catalog, not two catalogs.

## What this means for an integration

* **You cannot drive Marea AI through the API.** There is no "send a prompt to Marea AI" endpoint. To make catalog changes programmatically, use the [REST API](/quickstart/bootstrap) or the [MCP server](/quickstart/mcp) directly.
* **Edits are not exclusive.** A storefront edited by a merchant in Marea AI is still fully editable through your API key, and vice versa. Both honor the same [draft / publish](/concepts/publishing) lifecycle.
* **Drafts are shared.** Marea AI edits the storefront's working draft. If your integration reads a draft, expect it may also reflect the merchant's chat edits.

## When to point a merchant at Marea AI

If you are building a tool *for* merchants and a request is really "let me edit my page in natural language", that is what Marea AI already does inside the dashboard — point the merchant there rather than rebuilding it. Use the API for programmatic, multi-storefront, or headless integrations.