Core

Core is the foundation every other AgenticEcom module builds on. It provides the suite dashboard and configuration, a shared store-locale resolver so AI content comes back in each store view’s language, and the GraphQL handshake endpoints a headless Astro storefront uses to discover the suite — all public-safe, with no secrets ever exposed.

Compatibility

Magento

Open Source 2.4.9 GA (and later 2.4.x).

PHP

Tested on 8.4 and 8.5.

Role

Required base module — the rest of the suite depends on it.

Headless

Public health-check + config handshake over GraphQL.

What it provides

Command centre

An at-a-glance dashboard of the suite’s capabilities — your single entry point to the AI, SEO, content, catalogue and headless modules.

Locale resolver

Maps each store view to its language and a ready-to-use Respond in {language}. instruction, so AI-generated content (descriptions, meta, price summaries) comes back in the right language per store view — used by every AI module.

Suite config

The shared on/off and provider/model settings the suite reads, kept separate from each module’s own configuration.

GraphQL handshake

Endpoints an Astro storefront calls to confirm the suite is installed and ready.

GraphQL handshake

A headless storefront uses two public queries to discover the suite — neither exposes any secret:

Health check

{ agenticEcomHealthCheck {
    status version ai_configured
    modules { name enabled } } }

Returns active/inactive, the suite version, whether AI is configured, and which AgenticEcom modules are installed — the storefront’s readiness handshake.

Config

{ agenticEcomConfig { enabled ai_provider default_model } }

Public-safe configuration only — the AI provider name and default model, never an API key (keys are stored encrypted, per-module, and never returned).

No shared key, no leaks

There is no shared “Core” API key — each AI module holds its own encrypted key. The handshake endpoints only report whether things are configured, never the secrets themselves, so they’re safe to call from an anonymous storefront.

Configuration

Stores → Configuration → AgenticEcom · Core & System → Core Settings (reachable in the admin from AgenticEcom → Core Settings → Settings).

Enable the suite and set the default AI provider/model that informs the handshake. Each feature module then has its own detailed configuration section.

FAQ

Do I need Core installed?

Yes — it’s the base module the rest of the suite depends on (shared locale resolution, config and the GraphQL handshake live here).

How does multilingual AI content work?

Core’s locale resolver maps each store view to its language; the AI modules prepend a Respond in {language}. instruction to their prompts, so editing a product in a German store view yields German copy. American English (the LLM default) skips the instruction to save a token.

Can the handshake leak my API keys?

No. The config handshake returns only the provider name and default model. API keys are encrypted, held per-module, and never exposed by any Core endpoint.

Is it secure?

The handshake endpoints are public-safe by design (status and non-secret config only); admin config sits behind the suite’s ACL. Verified clean on PHP 8.4 and 8.5.