Open GravityOps -> AI Feed -> Controls for site-wide safety and lifecycle-alert controls. Runtime safety settings are checked before the plugin sends a generation request.
Provider Emergency Switches #
- Disable Anthropic blocks all text generation that uses Anthropic.
- Disable OpenAI blocks all image generation that uses OpenAI.
Use these switches for an incident, unexpected cost, provider outage, or planned maintenance. They affect every form, frontend button, administrator rerun, and workflow step using that provider. They do not delete feeds or credentials.
Disable AI For Entire Forms #
Select one or more named forms to block every AI feed belonging to those forms. Use Ctrl/Command while selecting to add or remove individual forms in the multi-select.
This is a form-wide emergency control. To stop only one feed, use its native Deactivate action on the Feeds tab or in Form Settings.
Model Lifecycle Alerts #
Lifecycle Alert Emails are enabled by default. Lifecycle Alert Recipient defaults to the WordPress administration email address and can be changed to an operational mailbox.
Only active feeds generate notices and email. The daily scan sends one site-wide consolidated email for each newly due event:
- when the plugin first detects an active feed using a deprecated model;
- seven days before the nearest confirmed retirement; and
- when the retirement date arrives.
The 30-day reminder appears in WordPress administration but does not send email. Multiple feeds using the same affected model are consolidated, and a sent event is recorded so routine daily scans do not repeat it. Inactive affected feeds remain visible in the Overview report without generating notices or email.
Turning email off does not disable the persistent report, Feeds count, retirement enforcement, or administrator notices. The plugin never selects a replacement automatically.
The daily scan compares feeds with the reviewed lifecycle data bundled in the installed plugin; it does not send API keys to a separate monitoring service. Keep the plugin updated so newly reviewed provider announcements and retirement dates can reach the site.
Public Frontend Limits #
- Public Requests Per Window is the number of anonymous generation requests allowed for one visitor during a window. The default is 10 and the hard maximum is 100.
- Rate-Limit Window is the window length in seconds. The default is 3,600 seconds (one hour), and the hard maximum is 86,400 seconds (one day).
These limits apply to public frontend buttons, not ordinary post-submission processing by itself. The plugin also applies a broader network ceiling so deleting a browser cookie does not create unlimited new request buckets.
Monthly Text Token Caps #
Premium and Agency administrators can enter a positive monthly token cap next to a named form or feed. Leave the field blank for no plugin-level cap. The plugin counts text input and output tokens recorded during the current month and skips generation once usage has reached the cap.
Form and feed caps are independent. The more restrictive reached cap stops the request. Image generation is not measured by text tokens and is not controlled by these fields. Provider-side budgets remain important because the plugin’s ledger is not the provider’s billing system.
Saved caps remain enforced after a plan downgrade so an existing cost guard is not silently removed.
Advanced Network Setup #
Most sites should leave Trusted Proxy IPs/CIDRs blank. It is relevant only when public frontend generation runs behind a CDN, load balancer, or reverse proxy and the server receives the visitor’s original address in X-Forwarded-For.
Enter only exact addresses or CIDR ranges officially published for the service directly in front of the site. Never enter a visitor address or a broad range you do not control. See the public access and proxy explanation before changing this field.
