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 |
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 or the MCP server 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 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.