Lars Koudal

cleverplugins

Grumpy AI Gate helps you stay in control as AI features spread across WordPress. It observes and intercepts outbound HTTP that other code on your site already initiates (plugins, themes, or core)—so you can see which plugin was involved, how much activity you are seeing (including helpful estimates), and optionally stop unwanted WordPress AI Client traffic for specific plugins. This plugin does not call external AI APIs for its own dashboard, analytics, or licensing. Nothing is sent to us or to a third-party analytics service.
Why use it
<ul>
<li>Visibility — Dashboard summaries, a per-plugin usage table, and a request log so surprises become visible early.</li>
<li>Spend awareness — When other software calls paid APIs, usage adds up. Logging helps you notice patterns before invoices or quotas become a problem.</li>
<li>Safer sharing — Knowing what leaves your server makes it easier to decide what belongs in prompts and what does not.</li>
<li>Optional blocking — For paths that use WordPress’s AI Client, you can block generations from selected plugins under Grumpy AI Gate → Settings (save to apply).</li>
</ul>
How it works
<ul>
<li>When the WordPress AI Client is available, the plugin records those requests from core lifecycle hooks (other code still drives the actual generation).</li>
<li>For HTTP fallback, Grumpy AI Gate hooks WordPress’s HTTP API (for example <code>pre_http_request</code>) to inspect requests that are already in flight. If a URL matches built-in recognition rules for major AI providers, a log row can be stored. Grumpy AI Gate does not open those connections for its own purposes—it only filters and classifies traffic initiated elsewhere on the site.</li>
<li>HTTP fallback does not block outbound API calls in the current release—it is there so you still get visibility when plugins talk to providers directly over HTTP instead of (or in addition to) AI Client flows.</li>
</ul>
Compatibility
The plugin requires WordPress 7.0+ (matches Requires at least in the plugin header). On WordPress 7.x, it works with core AI Client functionality where available. Release testing included WordPress 7.0 Beta 5. HTTP fallback remains important on every supported version—it records calls to recognized provider endpoints that other plugins make directly over HTTP, which is still common alongside (or instead of) AI Client–based flows.
Privacy
Everything is stored locally in your WordPress database. There is no cloud account, no telemetry, and no third-party analytics from this plugin.
For technical details on logging, double-counting avoidance, and blocking limits, see the FAQ below.
<h3>External services</h3>
This plugin does not rely on third-party AI APIs, remote analytics, or any external service for its own features. All logging and settings stay on your site.
Provider names and URL patterns included with the plugin are local matching rules only. They let Grumpy AI Gate filter and classify outbound HTTP requests that plugins, themes, or WordPress core may already be sending. They are not a list of servers this plugin calls to power the admin UI or to “phone home.”
Your site may still contact third-party AI providers when you or other software use AI features—that traffic is separate from this plugin’s own network use (which does not include calling those providers for monitoring).

Grumpy AI Gate

Intercept and log AI-related HTTP from plugins/themes; optional AI Client blocking. All data stays on your server.

netopsae

AudioEye’s patented technology tests for over 400 accessibility and compliance issues, and fixes many of them automatically, reducing the time to make content accessible.
You will get your first AudioEye Accessibility Score the moment you install AudioEye on your site. From then on, AudioEye monitors your site for new issues with every site visitor, detecting and fixing hundreds of errors, while also providing you with a reporting dashboard that identifies what we cannot fix and needs your attention.
Technology can’t do it alone. With advanced plans, AudioEye has a team of certified accessibility experts who can help you throughout your accessibility journey. For those issues that we cannot fix automatically, we show you what the issue is, and how to address it on your site. If a lawsuit occurs, AudioEye is here to support you every step of the way.
Note: Use of the AudioEye plugin requires an active subscription to an AudioEye Plan. See pricing <a href="https://www.audioeye.com/plans-and-pricing" rel="nofollow ugc">here</a>. A link to sign up for a new account is presented during the plugin activation process. To log into an existing AudioEye account, you will need to provide your AudioEye Site ID.
Script delivery (CDN): AudioEye loads the storefront script (<code>aem.js</code>) from <code>wsmcdn.audioeye.com</code> by default today. We are migrating to <code>wsv3cdn.audioeye-services.com</code>. New setups without a saved Site ID use the new host by default; sites that already had a Site ID saved before the CDN preference existed keep the legacy host until an administrator enables the new host under AudioEye → Script CDN (Advanced) after allowlisting the new URL in any Content Security Policy (<code>script-src</code>, etc.). On first run, the plugin includes an optional onboarding step that explains how to allowlist the new host in your CSP.
Features included in all AudioEye base plans:
<ul>
<li>Path to compliance with ADA, Sec 508, AODA & more, using WCAG 2.1 AA</li>
<li>AudioEye Trusted Certification​</li>
<li>Usability toolbar with 24/7 Helpdesk​</li>
<li>Suite of AI-Powered Tests & Fixes​</li>
<li>Access to Certified Accessibility Experts</li>
<li>Basic Legal Support & Warranty​</li>
</ul>
Features available in AudioEye custom plans:
<ul>
<li>Advanced Legal Support</li>
<li>Manual Remediations</li>
<li>Premium Support</li>
<li>Custom Training</li>
</ul>

Accessibility by AudioEye


Kind reminder that accessibility can't take shortcuts. It's like telling an online shop owner there is a widget that fixes all their UX issue. As a UX Designer, I can tell it's impossible. As an accessibility expert, I can tell this kind of solution only bring more complexity to the disable folks' experience.



In January 2025, the US Federal Trade Commission ordered [similar solution name] to pay $1 million (subject to a thirty day finalisation period) due to misrepresentation that its software could make any website compliant with WCAG.



Also, WCAG isn't necessarily what's needed in your country. (France is RGAA, Luxembourg is RAWeb, Europe is EN 301 549)Best is to stay informed, and don't install a magic wand that is more of a black box.


Missleading - Risks of lawsuits (says European Council)

AudioEye automatically finds and fixes common accessibility issues on your site. This plugin provides an easy way to install AudioEye’s accessibility  …

Grumpy AI Gate vs Accessibility by AudioEye