The AI infrastructure for your WordPress content. Vectorize posts with OpenAI embeddings and store them in Qdrant for semantic search.
Creator Assistant Hub is the core infrastructure plugin of the Creator Assistant ecosystem. It connects your WordPress site to OpenAI and Qdrant to automatically generate and store vector embeddings for your content, enabling semantic search and AI-powered features.
How it works
The Hub is the shared infrastructure layer for the Creator Assistant ecosystem. When a compatible add-on is active and activates a vectorizer, the plugin generates vector embeddings via the OpenAI API and stores them in your Qdrant vector database cluster whenever a post is published or updated. This makes your content available for semantic search and retrieval by Creator Assistant add-ons. Without an active add-on, the Hub runs in standby mode — no content is sent to external services.
Key features
- Automatic post vectorization — when an add-on activates a vectorizer, embeddings are generated and stored whenever a post is published or updated. Without an active add-on, no vectorization takes place.
- Chunk-based vectorization — splits post content into word-level segments and stores each chunk as a separate Qdrant point, enabling fine-grained retrieval (activated by add-ons via filter).
- Summary-based vectorization — generates a short AI summary of each post via OpenAI Chat Completions, then embeds and stores a single point per post for high-level semantic search (activated by add-ons via filter).
- Background batch vectorization — an hourly cron job automatically picks up any existing posts that have not yet been vectorized, so your entire content library is indexed without manual intervention.
- OpenAI integration — uses the
text-embedding-3-small model (1536 dimensions) via the OpenAI Embeddings API for all vectorizers; the Summary vectorizer additionally calls the OpenAI Chat Completions API (gpt-4.1-nano) to generate post summaries.
- Qdrant integration — stores and retrieves vector embeddings from your Qdrant Cloud cluster. Two collections are used:
post_chunk for chunk-level points and post_summary for post-level summary points.
- Block editor panel — shows the vectorization status of each post directly in the block editor sidebar (document settings panel).
- Post list column — adds a “Vector Status” column to the posts and pages admin list, showing the vectorization status of each entry at a glance.
- Settings page — configure OpenAI API key, Qdrant endpoint and API key, and cache expiration from a dedicated admin page.
- API response caching — configurable cache duration to reduce API usage and latency.
- Site Health check — reports the Hub service status in the WordPress Site Health screen.
- Qdrant keep-alive — sends a daily lightweight ping to prevent free-tier Qdrant Cloud clusters from being suspended.
- WPML compatible — detects the post language via WPML hooks (when WPML is active) and includes it in the Qdrant payload for multilingual filtering.
- Extensible — exposes actions and filters so add-ons can register additional post types, override vectorizer behaviour, customise Qdrant payloads, and add settings tabs.
Requirements
- An OpenAI account with a valid API key.
- A Qdrant Cloud account with an active cluster (free tier is supported).
- WordPress 6.6 or higher.
- PHP 7.4 or higher.
External services
This plugin connects to two third-party services. By using this plugin you agree to their respective terms and privacy policies.
-
OpenAI — used to generate vector embeddings from your post content via the Embeddings API. When the Summary vectorizer is active (enabled by an add-on), post content is also sent to the Chat Completions API to generate a short AI summary before embedding.
-
Qdrant Cloud — used to store and query vector embeddings.
Data is only transmitted to these services after you explicitly accept the Creator Assistant Terms of Service in the plugin settings and provide your own API credentials. No data is transmitted automatically upon activation.
FAQ
Do I need a paid OpenAI plan?
Yes. The OpenAI API is a pay-as-you-go service — a valid payment method and prepaid credits are required. There is no free tier for API usage. The text-embedding-3-small model used by the Hub is very affordable: generating embeddings for a typical blog post costs a fraction of a cent. Check OpenAI pricing for details.
Does the plugin work with the free tier of Qdrant Cloud?
Yes. The free tier of Qdrant Cloud provides a single cluster that may be suspended after a period of inactivity. The built-in keep-alive feature sends a daily ping to prevent this.
Which post types are vectorized?
By default, posts and pages are vectorized. Add-ons can register additional post types via the available hooks.
Where can I see the vectorization status of a post?
In two places:
- Block editor — open any post or page in the editor. A Creator Assistant panel in the document settings sidebar (top-right area) shows the vectorization status for each active vectorizer.
- Post list — a Vector Status column in the Posts and Pages admin list shows a green checkmark with the date of last vectorization, or a greyed-out label if the post has not yet been vectorized.
How do I check whether the service is properly configured?
Go to Tools → Site Health. A dedicated test named Creator Assistant Hub service reports whether the Terms of Service have been accepted and both OpenAI and Qdrant are connected and ready.
Also verify that WP-Cron is running correctly on your site. Vectorization is processed asynchronously via WP-Cron: if WP-Cron is disabled (e.g. DISABLE_WP_CRON is set to true in wp-config.php), posts will not be vectorized automatically. You can check this under Tools → Site Health → Info → WordPress constants. On some managed hosting plans, a real server-side cron job is used instead — make sure it is configured and firing regularly.
Can I disable API response caching?
Yes. In the Cache tab of the Hub settings page, set the cache expiration to Disabled.
Is my API key stored securely?
API keys are stored in the WordPress options table in the same way as other plugin settings. Make sure your WordPress database and hosting environment are secure. Keys are never exposed in the front end or in REST API responses accessible to non-administrators.
Do I need an active add-on for vectorization to work?
Yes. The Hub is a core infrastructure plugin — its vectorizers are disabled by default and must be activated by a compatible add-on (such as Creator Assistant Search). Without an active add-on, the plugin registers no vectorizers and no content is sent to OpenAI or Qdrant, even after you configure your API credentials.
What is the difference between Chunk and Summary vectorization?
The Hub provides two vectorization strategies, each stored in a separate Qdrant collection:
- Chunk — the post content is split into word-level segments. Each segment is embedded individually and stored as a separate point in the
post_chunk collection. This enables precise, paragraph-level retrieval.
- Summary — an AI-generated summary of the post is produced via OpenAI Chat Completions, then embedded and stored as a single point in the
post_summary collection. This enables high-level, concept-based semantic search.
Add-ons can enable either or both strategies independently via the creator_assistant_hub_post_vectorizer_post_chunk and creator_assistant_hub_post_vectorizer_post_summary filters.
Does the plugin support multilingual sites?
Yes. When WPML is active, the plugin detects the language of each post and includes it in the Qdrant payload. Add-ons can then filter search results by language. Sites without WPML are fully supported and unaffected.
Can other plugins or add-ons extend the Hub?
Yes. The Hub exposes WordPress actions and filters that add-ons can use to register additional settings sections, tabs, and custom behaviour. Developer documentation will be published on creator-assistant.it.
ChangeLog
1.0.0
- Initial release.
- Automatic post and page vectorization using OpenAI
text-embedding-3-small.
- Qdrant Cloud integration for vector storage and retrieval.
- Settings page with TOS acceptance, OpenAI, Qdrant, and cache configuration.
- Block editor sidebar panel showing per-post vectorization status.
- Post list column (“Vector Status”) with per-vectorizer status indicators.
- Hourly background batch cron to automatically vectorize existing content.
- Site Health integration reporting service status.
- Daily Qdrant keep-alive cron for free-tier clusters.
- Extensibility hooks for add-ons — settings:
creator_assistant_hub_loaded, creator_assistant_hub_after_register_settings, creator_assistant_hub_settings_tabs, creator_assistant_hub_sanitize_settings; OpenAI models: creator_assistant_hub_openai_embedding_model, creator_assistant_hub_openai_chat_model, creator_assistant_hub_embedding_dimension; vectorizer control: creator_assistant_hub_post_vectorizer_post_chunk, creator_assistant_hub_post_vectorizer_post_summary, creator_assistant_hub_skip_vectorizer, creator_assistant_hub_post_vectorizer_text, creator_assistant_hub_post_vectorizer_chunks; post types: creator_assistant_hub_additional_post_types, creator_assistant_hub_excluded_post_types; Qdrant payloads: creator_assistant_hub_post_vectorizer_post_chunk_payload, creator_assistant_hub_post_vectorizer_post_summary_payload, creator_assistant_hub_post_vectorizer_post_chunk_search_filter; collection lifecycle: creator_assistant_hub_post_vectorizer_post_chunk_collection_created, creator_assistant_hub_post_vectorizer_post_summary_collection_created.
