Npcink

Npcink AI Client Adapter gives OpenClaw-compatible and similar AI clients one WordPress REST namespace for reading Npcink Governance Core capability guidance, routing approved read abilities through the WordPress Abilities API, and forwarding governed write requests to Npcink Governance Core proposal and commit-preflight endpoints.
Adapter is intentionally thin. It does not define abilities, store approval truth, run workflow queues, or execute final write mutations without Core approval and commit-preflight.
Adapter can be distributed as the Npcink AI suite entry plugin while Core and Toolkit remain separate plugins. Adapter health reports missing dependencies and dependency-sensitive routes fail closed with a structured missing dependency error.
Adapter exposes a machine-readable <code>client_policy</code> on health, help, and the connection manifest so OpenClaw-compatible clients, Qclaw-style clients, WorkBuddy-style clients, or other local AI clients can consume explicit route, output, sensitive-read, and write-flow boundaries. The local CLI also redacts profile paths, key ids, signing headers, tokens, passwords, and secrets from output.
Current governed execution support covers individually approved proposal execution for explicit Adapter profiles, including <code>npcink-abilities-toolkit/trash-post</code>, <code>npcink-abilities-toolkit/create-draft</code>, <code>npcink-abilities-toolkit/update-post</code>, <code>npcink-abilities-toolkit/update-post-blocks</code>, <code>npcink-abilities-toolkit/update-template-blocks</code>, <code>npcink-abilities-toolkit/upsert-template-blocks</code>, <code>npcink-abilities-toolkit/update-template-part-blocks</code>, <code>npcink-abilities-toolkit/set-post-terms</code>, <code>npcink-abilities-toolkit/reply-comment</code>, and <code>npcink-abilities-toolkit/approve-comment</code>.

Npcink AI Client Adapter

Thin AI client channel plugin for Npcink Governance Core and WordPress Abilities execution.

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 AI Client Adapter vs AI Valve