Net-Base AI Operations is the operations and configuration layer behind the AI modules. It makes visible which key source is actually active, how queue and Cron are running, and the current state of multilingual, Magazine or other AI functions.
Manage keys centrally and transparently
Global or module-specific AI access credentials remain visible in one place, rather than sitting quietly side-by-side across multiple plugins.
Queues and Cron not treated as a black box
Translations, text jobs or image jobs can be traced technically before issues become visible only indirectly in the frontend.
Operate multiple AI modules together
The module links operational state and configuration across multiple plugins, reducing support effort and improving traceability.
What this module specifically provides
Shared operations and configuration layer for the AI plugins with central backend keys, queue overview and monitoring.
Purpose of this module
- Net-Base AI Operations is the central operations page for the AI-powered plugins.
- It shows which API key source is actually active in Multilingual, SEO and Magazine.
- It consolidates the queue, Cron and monitoring state of several modules in one place.
Backend keys and priorities
- Keys from wp-config.php or the environment take precedence.
- Next are the central backend keys configured on this page.
- Plugin-local fallback keys come afterwards and can be cleaned up here.
Monitoring
- Can detect stale translation or Magazine processes.
- Can trigger warning emails to a central address.
- Helps spot hangs in Cron or queue operation early, before content stalls.
What this page is not intended for
- Not for detailed editing of texts, images or SEO metadata.
- Not for direct topic or form management.
- For such detailed tasks the respective plugin dashboards remain the correct place.
Context
This page is the operations dashboard for AI keys, queue state and monitoring. Detailed editing remains in the respective plugin dashboards.
Why this foundation is crucial for AI functions
Once multiple AI-powered modules are active, it is no longer sufficient to enter keys and queue settings somewhere. You need a central operations page that makes visible what is actually active, what is stalled, and which source is currently in effect.
AI functions require a stable foundation
Especially in language and editorial automation, the real difference is not only the feature itself, but the steady, reliable technical operation behind it.