AI Spend Governance guide

First budget cap and enforcement

The first useful budget-protection win is not just seeing logs. It is knowing which compatible source is allowed to spend, where the limit is, and what should happen when the limit is reached.

Last updated: April 2026

Before you try this

Start with the getting started guide if you have not yet confirmed that AI Spend Governance can see compatible AI activity from at least one supported plugin or workflow on your site.

Logging is not enforcement

Logs help you explain what happened after an AI request runs. Enforcement is different: it is the policy layer that decides whether a plugin should be allowed to send the next request when its budget is already used up.

That distinction is the core reason to use AI Spend Governance. Visibility is useful, but supported budget control is what prevents compatible activity from continuing to create provider costs unchecked.

Choose one plugin to govern first

Do not start by trying to govern every AI workflow at once. Pick one compatible plugin or connector workflow where usage is easy to reproduce and the risk is easy to understand. A narrow first test is easier to trust than a broad rollout.

Plan the first budget cap

Your first cap should be intentionally small and easy to reason about. The goal is not to design a perfect policy on day one. The goal is to prove that one known compatible source of AI usage can be measured, given a limit, and stopped when the limit is reached.

What a hard stop does

It does

  • Stops the compatible source’s next supported AI request before it is sent once the configured limit has been reached
  • Leaves other activity alone unless it flows through a supported path with its own limit too
  • Gives you a control point before new provider spend is created

It does not

  • It does not disable the whole plugin
  • It does not block your entire site from using AI
  • It does not undo requests that already happened before the limit was hit
  • It does not cover plugins, SaaS tools, or custom code that bypass supported WordPress/Axtolab paths

What success should look like

A good first success is specific: you can identify the compatible source being governed, see the usage that counts against its budget, and confirm that an over-budget supported request would be stopped instead of going out silently.

If enforcement does not trigger

If you expected a block but the request still went through, check these first:

  • AI Spend Governance enforcement is licensed and active for the site
  • Cost rate configuration is set
  • The plugin you tested has a per-plugin budget cap configured
  • The usage really crossed the limit you set
  • The source is using a compatible WordPress/Axtolab path on this site

If you are still unsure, contact support and include your site URL, the plugin you tested, the settings you used, and what happened instead.

Back to setup

Need to confirm visibility first?

Use the getting started guide if you still need to confirm that compatible activity is visible before planning enforcement.

Back to getting started Visit support
Need help?

Still stuck after the guide?

For billing, license, activation, or account help, start with our support page. If you reach out, include your product name, order email, site URL, and the exact error or screenshot so we can help faster.

Visit support Email support

AI Spend Governance setup guides live here. Billing and license recovery still live in Support.