axtolab

WordPress 7.0 introduced the AI Client and the Connectors screen: you configure an AI provider API key once, and every plugin on your site can use it. What WordPress does not show you is which plugin is spending your money.
AI Spend Monitor records every call made through the WordPress AI Client and gives you a clear dashboard under Axtolab → AI Spend Monitor:
<ul>
<li>Per-plugin AI usage — see exactly which plugins and themes make AI calls, with calls, prompt tokens, and completion tokens for each.</li>
<li>Estimated cost per plugin — token counts are converted to an estimated USD cost using bundled list prices for popular OpenAI, Anthropic, and Google models.</li>
<li>Editable cost rates — a “Cost rates” tab lets you adjust the per-model input/output prices to match your provider plan or a price change. Saving re-estimates previously recorded calls too, so the whole dashboard reflects your rates. No code required.</li>
<li>Daily cost chart — a 30-day view of your estimated AI spend, so a sudden spike is visible the day it happens, not when the invoice arrives.</li>
<li>Recent call log — the latest AI calls with source, provider, model, and token counts.</li>
<li>CSV export — download the recorded calls for any period for accounting or review: source plugin, provider, model, tokens, and estimated cost per call.</li>
<li>Spend notification — optionally get one email per month when estimated sitewide AI spend passes a dollar amount you choose.</li>
<li>Zero configuration — activate it and it starts recording. No API keys, no account, no setup.</li>
</ul>
<h4>How it works</h4>
The plugin listens to the WordPress AI Client’s lifecycle hooks. When any plugin calls the AI Client, the call’s token usage and model metadata are recorded in a local database table, and the calling plugin is identified automatically. Old records are pruned after 90 days (filterable).
<h4>Privacy</h4>
All data stays on your site. The plugin records token counts and metadata only — it does not store prompt or response content, and it does not send anything to any external service. There are no remote calls, no tracking, and no account requirement.
<h4>For developers</h4>
<ul>
<li><code>aismon_usage_recorded</code> — action fired after each recorded call.</li>
<li><code>aismon_cost_rates</code> — filter the model price table used for estimates.</li>
<li><code>aismon_retention_days</code> — filter the data retention window (default 90 days).</li>
<li><code>aismon_dashboard_after_summary</code> — action to render additional dashboard panels.</li>
</ul>
<h3>External Services</h3>
AI Spend Monitor does not contact any external services. All data is recorded and stored locally in your WordPress database — no remote calls, no telemetry, no analytics.
The token-to-USD cost estimates use a pricing table that ships with the plugin (no remote lookup). The table can be overridden via the <code>aismon_cost_rates</code> filter; see the developer notes in the description.
The plugin does not send any data outside your WordPress site.
<h3>Privacy</h3>
AI Spend Monitor records the following data locally, in a custom database table with the standard WordPress table prefix:
<ul>
<li>The source plugin or theme that made each AI call.</li>
<li>The AI provider (e.g. OpenAI, Anthropic, Google) and model identifier (e.g. <code>gpt-4o-mini</code>).</li>
<li>Token counts per call: prompt tokens, completion tokens, total tokens.</li>
<li>A timestamp for each recorded call.</li>
</ul>
The plugin does not store any of the following:
<ul>
<li>Prompt or response content.</li>
<li>User identifiers, user emails, or user IP addresses.</li>
<li>Any other personally-identifying information.</li>
<li>Any visitor-facing data — the plugin only sees server-side AI calls made by other plugins or themes.</li>
</ul>
Recorded data is pruned automatically after 90 days. The retention window is filterable via <code>aismon_retention_days</code>. All recorded data, plugin options, and transients are removed when the plugin is uninstalled (see <code>uninstall.php</code>).
No recorded data is sent to any external service. All processing happens on your own WordPress site.

Axtolab AI Spend Monitor

AI usage and cost tracking for the WordPress AI Client. See which plugins make AI calls, how many tokens they use, and what it costs.

berkux

WP-Memory-Usage is a lightweight but powerful WordPress plugin that monitors and displays memory usage directly in your WordPress admin area. 
It is essential for site administrators and developers who need to keep an eye on memory consumption, identify bottlenecks, and act before users are affected.
What the plugin shows:
In the admin footer (every admin page): 
* Current memory usage vs. WordPress limit (with percentage) 
* Current memory usage vs. PHP limit (with percentage) 
* Server IP address and server name 
* PHP version
In the Dashboard widget (“Memory Overview”): 
* PHP version, architecture (32/64 bit), max execution time 
* WordPress memory limit (WP_MEMORY_LIMIT), WordPress admin limit (WP_MAX_MEMORY_LIMIT), PHP memory limit 
* Current peak memory usage with a visual progress bar (colour-coded: green / orange / red) 
* Latest digest status summary (warn / danger / critical badges) 
* Link to the Threshold Alerts settings page
Settings & Monitor — Tabs (since 2.0.0):
<ul>
<li>Settings — thresholds, logging options, email alerts, log rotation</li>
<li>History — latest logged requests with full context (URL, type, user, memory)</li>
<li>Digest — aggregated summaries of past log intervals; browse, merge, and delete digest files</li>
<li>️Actions — practical guidance on what to do when you receive a memory alert</li>
<li>Diagnose (new in 2.1.0) — full PHP/WordPress configuration snapshot with a ready-to-paste AI prompt for analysis</li>
<li>Memory Thresholds — current limits, threshold assessment, and recommendations</li>
<li>Check Installation — verifies that the plugin can run correctly on your server</li>
</ul>
<h3>Why Use WP-Memory-Usage?</h3>
Excessive memory usage leads to slower sites, HTTP 500 errors, and failed background jobs (cron, imports, backups). WP-Memory-Usage gives you the information you need to act before users are affected — without overwhelming you with notifications.
<h3>Features</h3>
<ul>
<li>Real-time memory display in the dashboard widget and every admin page footer</li>
<li>Colour-coded progress bar (green / orange / red) for instant status recognition</li>
<li>Three alert levels: Warning, Danger, Critical — each configurable as a percentage of the effective memory limit</li>
<li>Flexible logging: Ajax, REST, Admin, Cron, favicon requests — log only what matters</li>
<li>Email alerts with configurable recipient</li>
<li>History tab: recent requests with full context (URL, type, admin screen, REST route, AJAX action, user)</li>
<li>Digest tab: aggregated interval reports — browse, merge, and delete digest files</li>
<li>Actions tab: plain-language guidance on resolving memory alerts, no developer skills required</li>
<li>Diagnose tab (new in 2.1.0): full configuration snapshot + one-click AI prompt (English, copy & paste ready)</li>
<li>Memory Thresholds tab: shows effective limits, threshold gaps, and concrete recommendations</li>
<li>Check Installation tab: verifies log directory, WP-Cron, PHP functions, disk space, and email setup</li>
<li>Admin bar indicator: quick status badge visible on every admin page</li>
<li>Multisite compatible</li>
<li>Clean uninstall: removes all options, cron jobs, database-tables and log files on deletion</li>
</ul>
<h3>PluginCheck-Plugin Status</h3>
Plugin is compatible with PluginCheck-Plugin. Note regarding “trademarked_term”: “WP-Memory-Usage” and “wp-memory-usage” are today considered restricted terms. This plugin entered the WordPress repository in 2009, when those terms were permitted.
<h3>Credits</h3>
Copyright 2009–2013 by Alex Rabe, 2022– Bernhard Kux

WP-Memory-Usage

Monitor PHP memory usage, set alert thresholds, and diagnose your server configuration — directly inside WordPress admin.

Axtolab AI Spend Monitor vs WP-Memory-Usage