axtolab

<p>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 <strong>which plugin is spending your money</strong>.</p>
<p>AI Spend Monitor records every call made through the WordPress AI Client and gives you a clear dashboard under <strong>Axtolab <span aria-hidden="true" class="wp-exclude-emoji">→</span> AI Spend Monitor</strong>:</p>
<ul>
<li><strong>Per-plugin AI usage</strong> — see exactly which plugins and themes make AI calls, with calls, prompt tokens, and completion tokens for each.</li>
<li><strong>Estimated cost per plugin</strong> — token counts are converted to an estimated USD cost using bundled list prices for popular OpenAI, Anthropic, and Google models.</li>
<li><strong>Editable cost rates</strong> — 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><strong>Daily cost chart</strong> — 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><strong>Recent call log</strong> — the latest AI calls with source, provider, model, and token counts.</li>
<li><strong>CSV export</strong> — download the recorded calls for any period for accounting or review: source plugin, provider, model, tokens, and estimated cost per call.</li>
<li><strong>Spend notification</strong> — optionally get one email per month when estimated sitewide AI spend passes a dollar amount you choose.</li>
<li><strong>Zero configuration</strong> — activate it and it starts recording. No API keys, no account, no setup.</li>
</ul>
<h4>How it works</h4>
<p>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).</p>
<h4>Privacy</h4>
<p>All data stays on your site. The plugin records token counts and metadata only — it does <strong>not</strong> store prompt or response content, and it does <strong>not</strong> send anything to any external service. There are no remote calls, no tracking, and no account requirement.</p>
<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>
<p>AI Spend Monitor does <strong>not</strong> contact any external services. All data is recorded and stored locally in your WordPress database — no remote calls, no telemetry, no analytics.</p>
<p>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.</p>
<p>The plugin does not send any data outside your WordPress site.</p>
<h3>Privacy</h3>
<p>AI Spend Monitor records the following data locally, in a custom database table with the standard WordPress table prefix:</p>
<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>
<p>The plugin does <strong>not</strong> store any of the following:</p>
<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>
<p>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>).</p>
<p>No recorded data is sent to any external service. All processing happens on your own WordPress site.</p>


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.

Amaury Balmer

Maxime Culea

BE API

<p>If you want to see which media is used and where? This plugin is for you!</p>
<p>By installing this plugin you will index where your media are used, display further informations about how they are used and also warn you about deleting used ones.<br />
Therefore, you will easily delete unused medias.</p>
<p>A table is created for indexing where media are used. This is done when saving contents but could also by activating the plugin or be forced with the wp-cli commands.</p>
<h3>Features</h3>
<p>For now the supported contents for indexation are post types by focusing on :</p>
<ul>
<li>Post content ( gallery, image, links )</li>
<li>Post thumbnail</li>
<li><a href="https://www.advancedcustomfields.com/" rel="nofollow ugc">Advanced Custom Fields PRO</a>‘s fields :
<ul>
<li>“content fields” :
<ul>
<li>File</li>
<li>Gallery</li>
<li>Image</li>
<li>Post object</li>
<li>Page link</li>
<li>Relationship</li>
<li>Textarea</li>
<li>Wysiwyg</li>
</ul>
</li>
<li>“structuring fields” which can reuse the above “content fields”
<ul>
<li>Clone</li>
<li>Flexible</li>
<li>Group</li>
<li>Repeater</li>
<li><a href="https://acf-component-field.gummi.io/" rel="nofollow ugc">Component</a></li>
</ul>
</li>
<li>ACF Options</li>
</ul>
</li>
<li><a href="https://codecanyon.net/item/image-map-pro-for-wordpress-interactive-image-map-builder/2826664" rel="nofollow ugc">Image Map Pro</a></li>
</ul>
<h3>Third party support</h3>
<p>This plugin has third party support with following plugins :</p>
<ul>
<li><a href="https://github.com/BeAPI/bea-content-sync-fusion" rel="nofollow ugc">Content Sync Fusion</a> : the usage counter will now consider synced sites to reveal how many times a media has been used across all synchronized sites.</li>
</ul>
<h3>More features to come</h3>
<p>As you can see, some <a href="https://github.com/BeAPI/bea-media-analytics/issues?q=is%3Aissue+is%3Aopen+label%3Aquestion" rel="nofollow ugc">issues</a> are feature requests :<br />
– More fields support (excerpt, post meta, etc)<br />
– More type of support (widget, etc)<br />
– More support (elementor, visual composer, polylang, -wpml-, etc)<br />
– Media expiration<br />
– Media replacement<br />
– More file’s mime types</p>
<h3>Next Roadmap</h3>
<ul>
<li><a href="https://github.com/BeAPI/bea-media-analytics/issues/39" rel="nofollow ugc">39</a> : Improve display</li>
<li><a href="https://github.com/BeAPI/bea-media-analytics/issues/33" rel="nofollow ugc">33</a> : Ensure a lot of file’s mime types support</li>
</ul>
<h3>Who ?</h3>
<p>Created by <a href="https://beapi.fr" rel="nofollow ugc">Be API</a>, the French WordPress leader agency since 2009. Based in Paris, we are more than 30 people and always <a href="https://beapi.workable.com" rel="nofollow ugc">hiring</a> some fun and talented guys. So we will be pleased to work with you.</p>
<p>This plugin is only maintained, which means we do not guarantee some free support. Consider reporting an <a href="https://github.com/BeAPI/bea-media-analytics/issues" rel="nofollow ugc">issue</a> and be patient.</p>
<p>To facilitate the process of submitting an issue and quicker answer, we only use Github, so don’t use WP.Org support, it will not be considered.</p>


BEA – Media Analytics

Find where and how media are used across your site.

Axtolab AI Spend Monitor vs BEA – Media Analytics