How to Cap AI Spending for Your WordPress Site
AI providers charge by usage. Every alt text suggestion, summary, translation, or agent action on your WordPress site is a metered request to a provider like Anthropic, Google, or OpenAI.
Day-to-day use is predictable. The risk is unpredictable: a bulk job run twice, a feature stuck retrying, or an agent caught in a loop, each runs up charges while nobody’s watching.
Alerts help, but an alert only tells you. A cap stops it.
Set Two Ceilings
Prepaid credits with auto top-up off. With Anthropic and OpenAI, API requests stop when prepaid credits run out (Anthropic, OpenAI). Leave auto top-up off and your balance becomes the limit. Check the default: OpenAI turns auto recharge on during setup.
A hard monthly cap. All three featured providers let you set a monthly spending limit yourself. It’s your backstop if auto top-up stays on, and a cleaner budget line if it’s off.
When you reach the cap, AI features stop until the next month or until someone raises it. Make sure you decide in advance who gets notified and how the site should behave when AI calls fail.
Where Each Provider Puts the Controls
| Provider | Billing | Hard monthly cap | Worth knowing |
|---|---|---|---|
| Anthropic (Claude Console) | Prepaid credits; auto-reload is a Billing page setting; credits expire one year after purchase | Settings → Billing → Spend limits for the organization; lower limits per workspace under Settings → Workspaces | A spend limit can’t exceed your usage tier’s cap |
| OpenAI (API platform) | Prepaid credits; auto recharge is on by default at setup, with an optional monthly recharge limit | Organization or project settings: turn on “Enforce a hard limit” | Requests over the limit fail with a 429 error; spend alerts can warn you first |
| Google (Gemini API in AI Studio) | Prepay or postpay, depending on your billing plan | Per project: Spend page → Monthly spend cap → Edit spend cap | Billing data can lag up to about 10 minutes; your usage tier also sets an account-wide cap |
This reflects each provider’s documentation as of October 15, 2026. Billing settings change, so confirm them in each console.
One Project or Workspace Per Site
Put each WordPress site in its own Anthropic workspace, OpenAI project, or Google AI Studio project, and create that site’s key there. Each site then gets its own cap, its own usage report, and a key you can revoke without touching any other site.
Give staging its own project with a low cap, too. A staging copy of a live site carries the live key if it’s stored in the database, so replace it right after each clone. Where and how WordPress stores keys is covered in Where WordPress Stores AI API Keys, and Where They Should Live.
Watch the Meter from WordPress
- Turn on AI Request Logging. The official AI plugin’s logging experiment records AI requests, which you can view under Tools. Use version 1.4.0 or later, which logs provider errors as errors instead of successes.
- Compare it with the provider’s dashboard. If the provider shows more traffic than the log, a plugin may be calling it with its own key, or another site may be sharing the key.
- Limit who can use the connection. The AI plugin’s Connector Approvals experiment requires admin approval before a plugin or theme can use your site’s connectors.
- Start bulk actions small. Bulk alt text and bulk summary generation can send many requests at once, so try them on a few items first.
DOWNLOAD THE WORDPRESS RESPONSIBLE AI CHECKLIST
Spending caps are one of 26 checks in our Responsible AI for WordPress checklist, which also covers ownership, key storage, backups and revisions, testing, and AI agents.
Sources
- Anthropic: How do I pay for my API usage?
- Anthropic: Rate limits and spend limits
- Anthropic: Workspaces
- OpenAI: How can I set up prepaid billing?
- OpenAI: Spend limits
- Google: Gemini API billing
- AI plugin, WordPress.org (Request Logging, Connector Approvals, bulk actions)
(Last Updated: October 30, 2026)
This post was developed in collaboration with Claude Opus 5.5. Image generated using ChatGPT and Adobe Firefly via Photoshop. The final content was edited, tested, formatted, and fact-checked by Erik Lutenegger.
Read Other Technical Snippets
[email protected]
Need help with a with setting up AI on your website?