Toweringmedia AI Core for Magento 2 — User Guide

This is the user guide for Toweringmedia AI Core (toweringmedia/module-ai-core): the shared AI infrastructure layer required by all AI-capable Toweringmedia Magento 2 extensions. Configure your OpenAI-compatible provider, Google Gemini, speech-to-text, text-to-speech, call budgets, and safety gates once — Nora AI, Search Intelligence LLM, Product Builder, and other modules draw from the same runtime without re-implementing HTTP clients or budget logic.

• Toweringmedia AI Core for Magento 2 — $399/month

• Magento 2 extension index
• Magento 2 docs home
• Nora AI Extension (depends on AI Core)
• Search Intelligence LLM (depends on AI Core)

AI Core is the mechanics layer for AI on Magento 2. It does not ship storefront chat, SEO workflows, or product actions on its own. Domain modules register their tools via dependency injection and inherit all provider config, memory, budgeting, and audit infrastructure from AI Core.

• One OpenAI-compatible API key and model configured in admin for all dependent extensions
• Task Routing assigns different providers to chat, summarization, image generation, STT, and TTS
• Dry Run = Yes by default — zero API spend until you explicitly opt in to live calls
• Daily call budgets and per-run caps prevent runaway API spending
• Agent runtime with bounded tool execution loop, policy gates, and layered memory
• License validated remotely every few hours — monthly subscription must stay active

Install and validate in staging before production rollout.

composer require toweringmedia/module-ai-core
php bin/magento setup:upgrade
php bin/magento setup:di:compile
php bin/magento setup:static-content:deploy -f
php bin/magento cache:flush

Requires toweringmedia/module-base ^1.1.25 (installed automatically via Composer).

Stores → Configuration → Towering Media → AI Core Settings

Paste the AI Core license key from toweringmedia.com → My Extensions. The license is validated remotely every few hours. Live AI calls are blocked when the monthly subscription is unpaid, even if you supply your own OpenAI API key.

Master switches for the provider runtime.

Best practice: leave Dry Run = Yes in staging and CI. Only flip to live in production with a saved license key and API key.

Primary provider for chat completions, summarization, and embeddings.

Assigns the right provider to each AI task type. Chat and summarization share the OpenAI-compatible provider; image generation uses Google Gemini.

Cloud STT for Nora voice input. Uses the shared OpenAI-compatible API key and base URL above.

OpenAI neural TTS for Nora AI voice responses.

CallBudgetGuard enforces daily budget and post-error cooldown.

Subject-consistent image generation/editing via the Gemini Developer API. Powers “show my product on the customer's photo” features in Product Builder.

AI Core ships with Dry Run = Yes and Enable Live API Calls = No as safe defaults. In dry-run mode:

• Packets are built and shrunk locally
• Context memory reads and writes work normally
• Summarization caches are populated from prior runs if available
• Zero HTTP calls are made to any provider
• No API cost

To promote to production:

1. Enter a valid license key in the License section
2. Enter a valid API key in the Chat Provider section
3. Set Dry Run = No
4. Set Enable Live API Calls = Yes
5. Set a realistic Daily Call Budget
6. Save config and flush cache

AI Core provides a bounded agent runtime that consumer modules (Nora AI, Search Intelligence) use for multi-step, tool-calling workflows:

• Route → Tool Execution → Compose loop with structured error handling
• Tools register via Magento DI; AI Core owns orchestration and policy gates
• No tool side effect proceeds without a policy approval from PolicyInterface
• Layered memory: raw recent → short summary → rolled-up summary → durable tiers
• Context selection within token budget before prompt assembly
• Audit events for every routing decision, tool execution, and compose step

Consumers must not fork the agent loop, provider gates, or memory store. See docs/SCOPE.md in the module repo.

• License key saved; admin shows no license error
• Dry run test passes: enable and trigger any AI feature — no HTTP calls made to provider
• Live call test (staging with test API key): confirm chat completion returns successfully
• Daily budget enforced: set budget to 1, trigger two calls — second call should be blocked
• Cache cleared after every config change: php bin/magento cache:clean config full_page

• Live calls blocked despite Enabled = Yes: check that Dry Run = No, Enable Live API Calls = Yes, license is active, and daily budget > 0
• “License invalid” error: paste the key fresh from toweringmedia.com; whitespace or trailing newline causes validation failure
• Packet budget exceeded: increase Max Input Tokens or reduce the number of context sources sent by the domain module
• Cooldown blocking calls: wait for the cooldown window, or set Cooldown After Error = 0 (not recommended for production)
• Embeddings failing: confirm the Embeddings Model matches a model your API key has access to

• Magento Version: Magento 2.4.6+ (Open Source & Adobe Commerce)
• PHP Version: 8.1, 8.2, 8.3, 8.4
• Composer package: toweringmedia/module-ai-core
• Composer repository: composer.toweringmedia.com
• Module name: Toweringmedia_AiCore
• Requires: toweringmedia/module-base ^1.1.25
• Pricing: $399/month platform subscription
• License: Proprietary; remote entitlement validation

• Magento 2 extension index
• Magento 2 docs home
• Global docs home