by
Abhishek Deshpande
0 (0 reviews)
AIPCF – AI Provider for Cloudflare
AI on Cloudflare Workers AI: meta descriptions, alt text, search by meaning, a site assistant and answers for AI agents, inside the free allowance.
AIPCF ranks #71,984 among WordPress.org plugins with 0+ active installations, and was last updated Oct 27, 2026. Data from WordPress.org, refreshed twice daily — see methodology.
Compatible with WP 7.1.4
v2.0.0
Current Version v2.0.0
Updated 1 week ago
Last Update on 27 Oct, 2026
Refreshed 1 week ago
Last Refreshed on
Downloads -52.7% this week
Actively maintained
Rank
#71,984
—
No change
Active Installs
0+
-100%
KW Avg Position
N/A
—
No change
Downloads
1.1K
+14 today
Support Resolved
0%
—
No change
Rating
0%
Review 0 out of 5
0
(0 reviews)
Next Milestone 10
0+
10+
44,416
Ranks to Climb
-
Growth Needed
8,000,000
Active Installs
Pro
Unlock Exact Install Count
See the precise estimated active installs for this plugin, calculated from real-time ranking data.
- Exact install estimates within tiers
- Track install growth over time
- Milestone progress predictions
Need 10 more installs to reach 10+
Rank Changes
Current
#71,984
Change
Best
#
Downloads Growth
Downloads
Growth
Peak
Upgrade to Pro
Unlock 30-day, 90-day, and yearly download history charts with a Pro subscription.
Upgrade NowReviews & Ratings
0.0
0 reviews
Overall
0%
5
0
(0%)
4
0
(0%)
3
0
(0%)
2
0
(0%)
1
0
(0%)
Support Threads Overview
Resolved
Unresolved
1
Total Threads
0
Resolved
1
Unresolved
0%
Resolution Rate
Track This Plugin
Get detailed analytics, keyword tracking, and position alerts delivered to your inbox.
Start Tracking FreePlugin Details
- Version
- 2.0.0
- Last Updated
- Oct 27, 2026
- Requires WP
- 7.0+
- Tested Up To
- 7.1.4
- PHP Version
- 8.2 or higher
- Author
- Abhishek Deshpande
Support & Rating
- Rating
- ☆ ☆ ☆ ☆ ☆ 0
- Reviews
- 0
- Support Threads
- 1
- Resolved
- 0%
Keywords
Upgrade to Pro
Unlock keyword rankings, search positions, and detailed analytics with a Pro subscription.
Upgrade Now
Frequently Asked Questions
Common questions about AIPCF – AI Provider for Cloudflare
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 daily budget is there so that does not happen by accident.
You choose: pause AI requests until midnight UTC, or switch text requests to the cheapest model on your account. Only text requests have a cheaper model: Everything else pauses either way: Backfill, the content index, Link assistant chat, the Site assistant, Search, Search insights, AI agents, image generation, image reading (alt text) and translation. Generated images count about 170 neurons each when Cloudflare does not report the figure. Either way you get an email at 80% and at 100%. The count resets at midnight UTC.
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. Settings > Models shows the neurons per 1,000 tokens for every model on your account, read from Cloudflare's price list. I picked a model, but the logs show a different one (often Llama) That is expected for some requests, and Home and Settings > Models list the model for each one under "Current model setup". Writing uses your default model. Short tasks (titles, excerpts, meta descriptions, alt text wording) use the light model if you set one; a model you pick for a feature in the AI plugin is used as picked. Anything that reads an image, such as alt text, uses the vision model, because text models cannot see images; on most accounts that is Llama 3.2 11B Vision, and you can pick another vision model on Settings > Models. Generated images use the image model, translation uses M2M100 or IndicTrans2, and once the daily budget is used up text requests can switch to the cheapest model. The AI Gateway logs show which feature sent each request in the metadata field.
The model list is read from your account and cached for 12 hours. Each entry shows context window, neurons per 1,000 tokens from your account's current price list, and whether it supports tool calling or image input. 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: a vision model (Llama 3.2 11B Vision on most accounts, selectable on Settings > Models) reads inline and remote images. Your default text model is not used for images. Image generation: FLUX.1 schnell, SDXL Lightning, SDXL, DreamShaper, Leonardo Lucid Origin and Phoenix.
Not for AIPCF's own features (Backfill, the content index and the features on it, usage tracking, daily budget, and aipcf_translate() for developers). 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.
Backfill, the content index and the features on it, and the budget do, and so does aipcf_translate(). The in-editor buttons come from the WordPress AI plugin and need the block editor.
To Cloudflare. 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. If you switch the content index on, the content you selected is also stored, with its embeddings, in the vector store you chose: Cloudflare Vectorize on your account, your Qdrant server or Qdrant Cloud cluster, or your PostgreSQL database. Nothing else receives it. Embedding requests go through your AI Gateway (when you use one) with payload logging off, so the gateway's logs never hold a copy of your content. Author names are embedded only if you tick "Author name", and change in the vector store when a name changes or a user's posts are reassigned.
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.
You choose what goes in: post types (products and other custom types too), images, published and/or private content, which fields (title, content, excerpt, categories and tags, author, SEO description, custom fields), a date cut-off, and categories or tags to include or leave out. Any post can be left out from its editor, and password-protected content never goes in. You choose where it is stored: Cloudflare Vectorize on the same account (included in the Workers Free plan), a Qdrant server or Qdrant Cloud, or PostgreSQL with pgvector. Switching store later moves the index, at no neuron cost. It stays in sync: saving, trashing or deleting a post updates the index within about a minute; an unchanged save costs nothing. You see the cost first: an estimate of parts of posts, neurons and storage before anything is sent. Indexing whoisabhi.com (166 posts and pages) took about 60 neurons, well inside one day's allowance, with a daily limit of its own on top of the daily budget. Test search on the settings screen, and wp aipcf embed commands for large sites. The default model is BGE-M3 (multilingual, 1,024 dimensions). Search, the Site assistant and AI agents order results by your words and their meaning together. The best 20 can be checked again with BGE Reranker, so the parts that really answer the question come first.
An embedding is a list of numbers that captures what a piece of text is about, so text with a similar meaning gets similar numbers. Kept in a vector store, they let a site find posts by meaning instead of by keyword ("how much does it cost" finds the pricing page) and suggest truly related posts. AIPCF keeps them as the content index, for the Site assistant, Related posts, Search, the Link assistant, Search insights and AI agents.