CNXT AI Cost Guardrails
CNXT AI Cost Guardrails gives site administrators a local control plane for plugins that use the native WordPress AI Client. The plugin records content-minimized operational metadata around native AI Client calls, estimates token-billed cost from rates you control, and can prevent later prompts afte
About this tool.
CNXT AI Cost Guardrails gives site administrators a local control plane for plugins that use the native WordPress AI Client.
The plugin records content-minimized operational metadata around native AI Client calls, estimates token-billed cost from rates you control, and can prevent later prompts after recorded monthly usage reaches a configured threshold.
Features
- Sitewide monthly limits for estimated USD, AI call attempts, and total tokens.
- Per-source monthly limits for plugins, mu-plugins, themes, core, and unknown callers.
- Monitoring mode that marks calls which would have been prevented without blocking them.
- Enforcement mode that uses the official pre-flight AI Client prevention filter.
- Atomic request reservations to reduce concurrent overrun of request limits.
- Conservative handling of missing token or price data.
- Emergency stop that prevents new native AI Client prompts immediately.
- Content-free audit rows for prompts blocked by configured limits, fail-closed safety checks, or the emergency stop.
- Provider/model token-rate editor with historical estimate recalculation.
- Usage by source, recent activity, retention controls, and formula-safe monthly CSV export.
- No external service, account, telemetry, remote assets, license check, or paid feature lock.
All functionality included in this plugin is available without payment, registration, a license key, a quota, or a trial period.
Data minimization
CNXT AI Cost Guardrails stores only the time, inferred calling source, provider ID, model ID, capability, token counts, estimated cost, duration, coarse request context, and policy status.
It does not intentionally read or store prompt or response content, direct user identifiers, IP addresses, request URLs, API keys, or connector credentials. It briefly uses object identities, not message text, to correlate lifecycle events within one PHP request. All plugin data remains in the site’s own WordPress database. The plugin makes no outbound network requests and never starts an AI request.
