AIPCF - AI Provider for Cloudflare
| 开发者 |
deshabhishek007
fitehal |
|---|---|
| 更新时间 | 2026年9月14日 23:12 |
| PHP版本: | 7.4 及以上 |
| WordPress版本: | 7.1 |
| 版权: | GPL-2.0-or-later |
| 版权网址: | 版权信息 |
详情介绍:
- a meta description, excerpt or title: about 2 neurons (about 5,000 a day inside the allowance)
- a generated 1024x1024 image: about 170 neurons (about 55 a day)
- describing an image for alt text: about 17 neurons
- translating a sentence: under 1 neuron
- In the editor, with the WordPress AI plugin: excerpts, titles, meta descriptions, summaries, alt text on upload, image generation.
- Across your archive: an hourly backfill fills missing meta descriptions (Yoast, Rank Math, AIOSEO, SEOPress) and image alt text, a batch at a time, within its own daily budget. It works with or without the AI plugin. A 140-post backlog cost about 175 neurons on a real site.
- A receipt after every action: feature, model, neurons and time, shown in the editor. Today's total sits in the admin bar. A monthly e-mail sums up requests, tokens and neurons.
- Translation for any theme or plugin:
aipcf_translate( $text, 'mr' ), 100 languages via M2M100 and 22 Indian languages via IndicTrans2.
- A Cloudflare account. No credit card is needed for the Workers AI daily allowance.
- An API token created from the "Workers AI" template at dash.cloudflare.com/profile/api-tokens.
- Your Account ID, the 32-character code on the right of the Workers & Pages page in the Cloudflare dashboard.
- Recommended defaults: Gemma 4 26B for writing, Granite 4 Micro for short tasks, the 10,000-neuron daily guard, no paid fallbacks, caching on.
- Daily budget guard: e-mail at 80%; at 100% either pause until midnight UTC or switch to the cheapest model instead of failing.
- Short tasks on a small model: titles, excerpts, meta descriptions, moderation and alt text go to a model that costs a fraction of the neurons; long-form keeps your default.
- Caching: repeated identical prompts are answered from cache for zero neurons, at Cloudflare's edge through AI Gateway or locally. A "Regenerate" click within ten minutes bypasses it so you get a new answer.
- Never fall back to paid providers: one switch keeps Anthropic, Google and OpenAI out of the AI plugin's fallback list.
- Site Health: one test that goes amber only for things that need you: not connected, connector unapproved, a licence gate, the gateway bypassed, the budget reached.
- Chat models: Llama, Gemma, GPT-OSS, Qwen, Mistral, DeepSeek, GLM, Granite, Kimi, Nemotron and whatever Cloudflare adds next. Requests use Cloudflare's OpenAI-compatible endpoint, so new families work without a plugin update.
- Tool calling, JSON output with schema, system instructions, stop sequences and penalties through the standard AI Client API. Reasoning models keep their thinking on the AI Client's thought channel, out of the answer.
- Vision: Llama 3.2 11B Vision reads inline and remote images.
- Image generation: FLUX.1 schnell, SDXL Lightning, SDXL, DreamShaper, Leonardo Lucid Origin and Phoenix.
aipcf_prompt filter.
The AI plugin (recommended)
AIPCF is the engine. The WordPress AI plugin adds the block-editor features that use it: excerpts, titles, meta descriptions, alt text on upload, summaries, image generation. It is recommended, not required; AIPCF's own features (backfill, translation, usage tracking, budget guard) work without it.
安装:
- Install and activate the plugin. You land on Cloudflare AI, a new item in the admin menu.
- Add your Cloudflare API token on Settings > Connectors (WordPress 7.0+ manages provider keys there) and your Account ID on the Overview tab. The setup panel has the exact clicks for creating the token.
- Click Apply recommended defaults. That picks the models, turns on the budget guard and caching, and approves the connector.
- Optional: install the WordPress AI plugin for AI in the block editor, and enter an AI Gateway name on the AI Gateway tab for edge caching and logs.
屏幕截图:
常见问题:
Is it really free?
Cloudflare Workers AI includes 10,000 neurons a day on every account, with no card on file. Measured on a live site, a meta description costs about 2 neurons and an alt text about 17, so a normal site never gets near the limit. Above the allowance Cloudflare bills per neuron at its published rate; the plugin's budget guard is there so that does not happen by accident.
What happens when the daily budget is reached?
You choose: pause AI requests until midnight UTC, or switch every request to the cheapest model on your account. Either way you get an e-mail at 80% and at 100%. The count resets with Cloudflare's day.
Which model should I use?
Start with the recommended defaults: Gemma 4 26B for writing and Granite 4 Micro for short tasks. They were picked by measuring output quality against neurons on real posts. Llama 3.3 70B writes a little better and costs several times more per token. The Models tab shows the neurons per 1,000 tokens for every model on your account, read from Cloudflare's price list.
Do I need the WordPress AI plugin?
Not for AIPCF's own features (backfill, translation, usage tracking, budget guard). You need it for AI inside the block editor: excerpts, titles, meta descriptions, summaries, alt text on upload and image generation. Install it from wordpress.org; AIPCF registers itself as the provider.
Does it work with the Classic editor?
The backfill, translation and budget features do. The in-editor buttons come from the WordPress AI plugin and need the block editor.
Where does my content go?
To Cloudflare, and nowhere else. When a feature runs, the post title and content (or the image) go to Cloudflare Workers AI on your own account. Nothing is sent until you enter your credentials, and the External Services section below lists every endpoint. With an AI Gateway you decide in the Cloudflare dashboard whether prompts are logged.
Where is my API token stored?
On WordPress 7.0+ it lives in the core Connectors screen (Settings > Connectors), like every other AI provider key. You can also define it as a constant in wp-config.php. The plugin never sends it anywhere except Cloudflare.
Will the backfill overwrite descriptions or alt text I wrote?
No. It only fills empty fields. Posts that already have a meta description and images that already have alt text are never touched. It writes to the meta key of your SEO plugin (Yoast, Rank Math, AIOSEO or SEOPress), so you can edit the result where you always do.
Can I stop the backfill, or undo it?
Turn off "Hourly backfill" on the Backfill tab and it stops after the current batch. Descriptions it wrote are ordinary post meta; edit or clear them like any other. Items it skipped are listed on the tab with a retry link.
Does it slow my site down?
No. Requests only happen when a feature runs, and the backfill runs in the background through WP-Cron, one batch an hour. Visitors never wait on Cloudflare.
Can I use one Cloudflare account for several sites?
Yes, and many people do. Keep in mind the 10,000-neuron allowance is per Cloudflare account, not per site, so set each site's daily budget to a share of it. An AI Gateway shows the usage of all sites in one place.
Can I change what the plugin asks the model?
Yes. The Prompts tab holds every prompt the plugin sends on its own behalf, with placeholders and a test button. Developers can also use the aipcf_prompt filter.
A model says "Model Agreement: Prior to using this model, you must submit the prompt 'agree'"
Some Meta models (Llama 3.2 Vision) need a one-time licence acceptance per Cloudflare account. The plugin shows a notice with the steps and a re-check button. The Playground's chat box cannot send it; the notice includes the one-line request that does.
I get "connector has not been approved"
WordPress asks administrators to allow each AI connector once. "Apply recommended defaults" does it for you; otherwise go to Settings > Connectors and click Allow next to Cloudflare Workers AI.
Requests time out
The plugin waits up to 60 seconds. 70B-class and reasoning models can take longer on a cold start. Raise the limit with the aipcf_request_timeout filter or pick a smaller model.
Reasoning models return an empty answer
Qwen3, GLM and GPT-OSS spend tokens thinking before they answer. The plugin turns thinking off by default where the model allows it and applies a 2,048-token output limit when the caller sets none. If you still see empty answers, raise max_tokens or pick a non-reasoning model.
How do I start over, or remove everything?
"Reset plugin" at the foot of the About card clears the plugin's settings, usage history, caches and backfill progress, and keeps everything it generated. Deleting the plugin from the Plugins screen does the same cleanup.
Does this work without WordPress 7.0?
No. The AI Client arrives in WordPress 7.0; the plugin does nothing on older versions.
更新日志:
- Fixed: "Run one batch now" did nothing while the hourly backfill switch was off, and said nothing either. It now runs regardless and reports what it filled, skipped and what is left.
- Removed a leftover check that made the backfill depend on the Abilities API; it has used its own prompts since 1.7.
- Your credentials and model choice are kept. The settings page has moved from Settings to its own "Cloudflare AI" menu; old links redirect. A setup panel offers the recommended defaults (Gemma 4 26B for writing, Granite 4 Micro for short tasks, a daily budget guard, caching); nothing is applied until you click.
- Requests use Cloudflare's OpenAI-compatible endpoint, so newer model families (Gemma 4, GPT-OSS, Qwen3, GLM, Granite) work, and the "Missing result.response" failures of 1.0.x are gone.
- The model list is read from your account with context, cost in neurons and capability labels, refreshed every 12 hours.
- New since 1.0.3: neuron usage tracking with a daily budget guard and e-mails; a receipt in the editor after every AI action and today's total in the admin bar; Cloudflare AI Gateway support with edge caching and analytics; light-model routing for short tasks; response caching; image generation; translation; hourly backfill for missing meta descriptions and image alt text; editable prompts; a monthly usage e-mail; a Site Health test; "Reset plugin".
- The settings screen was redesigned: sidebar navigation, section cards, switches, one line of help per field with a "Why?" link, advanced fields hidden until asked for.
- Fixed along the way: the configured default model was not first in the provider's list; text sent as content parts broke Llama; a 5-second request timeout; Meta licence gates were opaque; vision requests failed on the OpenAI-compatible endpoint; "Regenerate" returned the cached answer; edge cache hits were counted at full cost.
- New: Prompts tab. Every prompt the plugin sends on its own behalf is editable, with placeholders, reset and a test button.
- New: meta-description backfill no longer needs the WordPress AI plugin. The AI plugin is recommended with an install link, not required.
- New: Models tab shows how many models were read from the account and when, with a "Refresh now" link.
- Fixed: "Regenerate" in the editor returned the cached answer. A repeat of the same request within ten minutes now bypasses the local and gateway caches.
- Fixed: editor receipts were fetched after every abilities request instead of only after a run.
- Changed: the "Try it" hint names a feature that is actually on; usage labels read "Other (direct API calls)" and "Backfill: meta description".
- Code passes the WordPress security and i18n sniffs; 78 integration tests on the WordPress test framework.
- New: two-step setup after activation with one-click recommended defaults and a token walkthrough.
- New: neuron receipts in the block editor after every AI action, and today's total in the admin bar.
- New: monthly usage e-mail on the 1st.
- New: Site Health test.
- New: tabbed settings with an Overview (status cards, today's neurons, quick actions).
- New: image generation (FLUX.1 schnell, SDXL, DreamShaper, Leonardo) registered with the AI plugin's image features.
- New: translation via M2M100 and IndicTrans2,
aipcf_translate(). - New: hourly backfill for missing meta descriptions and image alt text, with its own daily budget, failed and decorative markers, and support for offloaded media read by URL.
- New: vision requests go through Cloudflare's native endpoint with a system message, which the OpenAI-compatible endpoint rejects for images.
- New: Meta licence gates are detected and explained with a re-check button.
- Fixed: responses served from the AI Gateway edge cache were counted at full cost; a model-level 403 no longer triggers the gateway bypass.
- New: light-model routing for short tasks (titles, excerpts, meta descriptions, moderation, alt text).
- New: local response cache for deterministic requests.
- New: "Never fall back to paid providers".
- New: Cloudflare AI Gateway support with edge cache TTL, request metadata, prompt-logging toggle, authenticated gateways, dynamic routes and automatic direct fallback.
- New: neuron usage tracking per day, feature and model, with a daily budget guard and 80%/100% e-mails.
- Changed: requests use Cloudflare's OpenAI-compatible endpoint, so new model families work without a plugin update.
- New: the model list is read live from the account, grouped by vendor, with context, cost and capability labels.
- Fixed: the configured default model was not the first in the provider's list; text content sent as parts broke Llama; a 5-second request timeout; model caches not cleared after upgrades.
- Cloudflare Workers AI registered as a provider for the WordPress AI Client.