AI Valve vs Npcink AI Client Adapter

AI Valve gives site administrators visibility and control over how plugins use the built-in WordPress AI connector. Features Per-plugin access control — Allow or deny individual plugins from making AI requests. Abilities API guard — Optionally apply the same policy to WordPress Abilities API calls (WordPress 7.1+), keyed by ability namespace. Token budgets — Set daily and monthly token limits per plugin and globally. Context restrictions — Control which execution contexts (admin, frontend, cron, REST, AJAX, CLI) may trigger AI calls. Usage dashboard — See token consumption at a glance with summary cards, progress bars, and per-plugin breakdowns. Request logging — Every AI request is logged with provider, model, capability, tokens, and caller attribution. Budget alerts — Admin notices and optional email when usage approaches or exceeds limits. Requirements WordPress 7.0 or later PHP 8.3 or later A configured AI provider in Settings → Connectors Developer Hooks AI Valve exposes filters and actions so you can extend its behaviour without editing the plugin. Full signatures, parameters, and examples are in the developer hooks documentation. aivalve_plugin_policy (filter) — Override the allow/deny decision for any plugin. aivalve_request_denied (action) — React when an AI request is blocked. aivalve_request_completed (action) — React when an AI request succeeds (token counts available). aivalve_ability_invoked (action) — React when an Abilities API call is invoked (WP 7.1+). aivalve_ability_denied (action) — React when an Abilities API call is blocked (WP 7.1+). Renamed in 1.3.0 from the soderlind_aivalve_ prefix; the old names still fire as deprecated aliases and will be removed in a future major version.

Npcink AI Client Adapter connects local AI clients, such as OpenClaw-compatible tools, to a WordPress site through a focused REST adapter. It is designed for sites that use Npcink Governance Core for reviewable AI operations and WordPress Abilities API providers, such as Npcink Abilities Toolkit, for concrete WordPress capabilities. The Adapter gives clients one stable WordPress REST surface for checking readiness, reading governance guidance, running approved read abilities, creating governed proposals, and executing supported writes only after Core approval and commit-preflight. The default connection path uses signed key-pair pairing so the AI client does not need to receive a WordPress Application Password. A WordPress Application Password fallback is available for clients that already have a dedicated secret field or credential vault. Adapter is intentionally thin. It does not define abilities, store approval truth, run workflow queues, act as an MCP server, manage model providers, store prompts, or execute arbitrary final write mutations. Governance remains in Npcink Governance Core. Ability definitions and callbacks remain in Npcink Abilities Toolkit or another WordPress Abilities API provider. Adapter exposes a machine-readable client_policy on health, help, and the connection manifest so compatible 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 explicit Adapter profiles after Core approval, including npcink-abilities-toolkit/trash-post, npcink-abilities-toolkit/create-draft, npcink-abilities-toolkit/update-post, npcink-abilities-toolkit/update-post-blocks, npcink-abilities-toolkit/set-post-terms, npcink-abilities-toolkit/reply-comment, and npcink-abilities-toolkit/approve-comment. Key features: Connect OpenClaw-compatible and similar local AI clients to WordPress through one Adapter REST namespace. Check Adapter readiness and dependency status before a client starts work. Expose a machine-readable client_policy so clients can understand route, read, write, and sensitive-data boundaries. Route approved direct-read requests through the WordPress Abilities API. Forward governed write requests to Npcink Governance Core proposal and commit-preflight endpoints. Support a user-triggered approve-and-execute path for explicit, allowlisted execution profiles after Core approval. Prefer signed key-pair pairing for local clients, with an Application Password fallback when appropriate. Keep channel, governance, ability, cloud, and model-provider responsibilities separate.