Grumpy AI Gate

Plugins can trigger AI calls in the background—for content, assistants, SEO tools, and more. Logging gives you a clear picture of which plugin is active, how often requests run, and where traffic is going, so you can manage budgets and content thoughtfully.

It helps you see usage and trends. Optional blocking reduces some WordPress AI Client traffic for plugins you choose. Outbound HTTP calls to provider APIs that other code makes are logged for visibility in the current release but are not blocked here—use provider dashboards, API keys, and quotas for hard spend limits.

No. Logs and settings stay on your server in the WordPress database. This plugin does not add off-site tracking or analytics.

Blocking applies to WordPress AI Client flows that respect the wp_ai_client_prevent_prompt filter. You choose plugins under Grumpy AI Gate → Settings and save. It is not a full firewall for every outbound request.

No. Only AI Client traffic for plugins you select under Grumpy AI Gate → Settings is blocked (after you save). HTTP calls to provider APIs that other plugins or themes initiate are observed and logged in the current release but not blocked .

Yes. The plugin loads safely. Without the AI Client stack, HTTP fallback can still record calls to recognized provider endpoints when that option is enabled in Settings , as long as other code on the site is making those outbound requests.

When the WordPress AI Client stack is available, a full generation is one log row from its lifecycle hooks; the matching raw provider HTTP for that same call is skipped so usage is not double-counted. Calls that do not fire those hooks (for example listing models) are still logged and may appear with capability provider_http . When another plugin talks to a known AI API without going through core AiClient, or when AI Client monitoring is off in settings, those requests are recorded via HTTP fallback instead.

Only built-in provider host/path rules (OpenAI, Anthropic, Google AI / Gemini, xAI, DeepSeek, Mistral, OpenRouter, and local Ollama). See Grumpy AI Gate → Settings for the current hostname list. Those patterns exist only to filter and classify outbound traffic initiated by other code —they are not endpoints this plugin contacts for its own operation.

Blocking uses WordPress’s wp_ai_client_prevent_prompt filter: it stops prompt builder flows (support checks and generations) that go through that path. Separate calls such as listing models ( /v1/models ) may still run as provider HTTP on the AI Client channel and appear as a successful row—that traffic does not go through the same prevent hook.

Yes. Under Grumpy AI Gate → Settings , use the options to clear the request log only, or clear the log and aggregated statistics, as needed.