Ecwid + Memtro

Only when you ask, and only what it has been granted: update an order's payment or fulfilment status, tracking number or private note, quietly unless asked to email the customer; create an order by hand (a phone or manual order), quietly unless asked to email the customer; delete an order, permanently; create a product; update a product's name, price, SKU, stock, description, categories or visibility; add to or remove from a product's stock; delete a product, permanently; create a category; rename, describe, move, show or hide a category; delete a category, permanently; create a customer; update a customer's email, group, marketing consent, language or private note. Every other tool reads, searches or lists. The Connections page labels the tools that act, an administrator grants each one by name to the teams that may use it, and a personal connection acts only after its owner allows it.

A personal connection serves only your own requests. A shared connection serves the organisation: everyone, or only the teams an admin chooses. Admins can always add shared connections; other members need the permission.

Credentials are encrypted at rest. Tool results are cached briefly so agent loops do not repeat identical calls, and the facts the model extracts are saved to your organisation's memory with provenance (system, record and link) so they can be checked and superseded.

Store ID and secret token. Find your Store ID, the number in your Ecwid admin's address bar or footer.

Yes. Turn events on in the connection's Events tab on the Connections page, then add the address it shows as a webhook in Ecwid, choosing the same kinds; the tab shows Ecwid's own steps. A job set to start "When an event arrives" then runs once for each matching event, with the event as its input. The run treats the event as outside data, never as instructions, and anything the run remembers is kept as unverified.