Npcink

The npcink-governance-core plugin is the Npcink AI governance layer for WordPress operations. It discovers ability metadata, records proposals, supports approval and rejection, performs commit preflight, and writes audit evidence.
Core does not generate content, route models, run MCP or workflow runtimes, store provider credentials, proxy ability execution, or perform final WordPress mutations.

npcink-governance-core

Npcink AI governance layer for WordPress operations.

Per Søderlind

AI Valve gives site administrators visibility and control over how plugins use the built-in WordPress AI connector.
<h4>Features</h4>
<ul>
<li>Per-plugin access control — Allow or deny individual plugins from making AI requests.</li>
<li>Token budgets — Set daily and monthly token limits per plugin and globally.</li>
<li>Context restrictions — Control which execution contexts (admin, frontend, cron, REST, AJAX, CLI) may trigger AI calls.</li>
<li>Usage dashboard — See token consumption at a glance with summary cards, progress bars, and per-plugin breakdowns.</li>
<li>Request logging — Every AI request is logged with provider, model, capability, tokens, and caller attribution.</li>
<li>Budget alerts — Admin notices and optional email when usage approaches or exceeds limits.</li>
</ul>
<h4>Requirements</h4>
<ul>
<li>WordPress 7.0 or later</li>
<li>PHP 8.3 or later</li>
<li>A configured AI provider in Settings → Connectors</li>
</ul>

AI Valve

Control, meter, and permission-gate AI usage from plugins that connect through the WordPress 7 AI connector.

npcink-governance-core vs AI Valve