AgenticEcom Core for Magento 2 — Shared Foundation & AI Hub
AgenticEcom Core is the shared foundation every AgenticEcom module is built on. It provides the unified admin home, the multi-provider AI hub (Google Gemini, OpenAI or Anthropic, with your own key), suite-wide rate limiting and response caching, automatic store-language handling, and a public-safe GraphQL handshake for headless frontends. It installs automatically as a dependency of every AgenticEcom module.
The foundation the whole suite is built on
Every AgenticEcom module shares the same plumbing: one admin home, one way of talking to AI providers, one master switch, and one clean handshake for a headless frontend. AgenticEcom Core is that plumbing. It gives the suite a single, organised place in your admin, a shared AI hub that any module can call with your own API key, and sensible guard-rails — rate limiting, caching and store-language handling — so the modules behave consistently and predictably. You don't usually buy Core on its own: it installs automatically as a dependency of every AgenticEcom module.
Required by every module · Multi-provider AI hub · Bring your own key · Rate-limited & cached · Store-language aware · GraphQL handshake · Magento 2.4.9 · PHP 8.4 / 8.5
| One admin home | Defines the organised AgenticEcom config sections — Core, AI, SEO, Catalog, Sales and Headless — so every module lands in the right place. |
|---|---|
| The AI hub | A single dispatch service that calls Google Gemini, OpenAI or Anthropic — so modules don't each reinvent the API plumbing. |
| Guard-rails built in | Per-minute rate limiting and response caching protect you from runaway API costs and repeated calls. |
| Headless handshake | A public-safe GraphQL health check and config query for an Astro or other decoupled frontend to confirm the suite is live. |
What it does for you
- Keeps your admin tidy — all AgenticEcom settings sit under clear, grouped tabs instead of scattering across the config tree.
- Standardises AI — one hub talks to your chosen provider, so AI modules share consistent behaviour, caching and limits.
- Controls cost — a per-minute rate limit caps how many AI calls can fire, and deterministic responses are cached for an hour.
- Speaks your customer's language — AI output is automatically asked to respond in the store view's language.
How the AI hub works
Bring your own AI key — no shared secret
There is no single AgenticEcom AI key to leak. Each AI module stores its own encrypted provider key in its own settings, and passes it to the hub per request. The hub never holds a shared credential, creates a fresh HTTP client for every call so headers can't bleed between providers, and enforces a per-minute rate limit backed by the cache — so one runaway loop can't quietly burn through your API budget. The GraphQL handshake exposes only public-safe values; your keys never cross the storefront boundary.
What's inside
| Admin home | Defines the AgenticEcom config tabs: Core & System, AI, SEO & Content, Catalog & Products, Sales/Customers/Marketing, Headless & Astro |
|---|---|
| AI providers | Google Gemini, OpenAI and Anthropic, called through one dispatch service |
| Keys | Per-module, encrypted, passed per request — no shared Core key |
| Cost controls | Per-minute rate limit (default 60) and 1-hour caching of deterministic responses |
| Localisation | Automatic "respond in {store language}" instruction from the store view locale |
| Embeddings | Gemini / OpenAI embeddings, with a deterministic hash fallback |
| Headless | GraphQL agenticEcomHealthCheck and agenticEcomConfig — public-safe only |
| Master switch | Suite-wide enable/disable and debug logging |
| Delivery & licence | Composer install; included automatically with every AgenticEcom module |
Works with
Core underpins the entire AgenticEcom suite. Other foundations in Core & System:
Included in the Starter, AgenticEcom Suite — and with every individual module.
See it in action
Frequently asked questions
Do I need to buy Core separately?
No. Core installs automatically as a Composer dependency of every AgenticEcom module, so you always have it. It's listed here so the catalogue is complete and so you can see what underpins the suite.
Which AI providers does the hub support?
Google Gemini, OpenAI and Anthropic. Each AI module sets its own provider and key; the suite standardises on Gemini by default but the hub can dispatch to any of the three.
Is there one shared AI key for everything?
No. Each AI module stores its own encrypted key and passes it per request. There is no shared Core credential, which means there's no single key to leak and you can use different providers per module.
How does Core stop AI calls running up a big bill?
It enforces a configurable per-minute rate limit across all modules and caches deterministic (low-temperature) responses for an hour, so repeated identical requests don't re-hit the provider.
Which Magento and PHP versions are supported?
Magento Open Source 2.4.9 and later 2.4.x, verified on PHP 8.4 and 8.5.
