Creator Assistant Hub

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.

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.

By default, posts and pages are vectorized. Add-ons can register additional post types via the available hooks.

In two places:

1. 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.
2. 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.

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.

Yes. In the Cache tab of the Hub settings page, set the cache expiration to Disabled.

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.

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.

No. The Hub only reads your content to generate vector embeddings. It never writes back to the post body, title, status, slug, or any other standard post field. Your content stays exactly as you wrote it. The only things the Hub writes to your WordPress database are:

1. A post meta entry on each vectorized post that records when it was indexed (keys: _creator_assistant_hub_post_vectorizer_post_chunk and _creator_assistant_hub_post_vectorizer_post_summary). This metadata is invisible to visitors, does not appear in SEO tools, and has no effect on how WordPress renders the post.
2. The plugin settings you enter (API keys, cache TTL, Terms of Service acceptance), stored in the WordPress options table.

No. The hourly background cron reads post content to generate embeddings but never writes to the post itself. The only write operation it performs is updating the post meta timestamp once vectorization is complete.

Deactivating the plugin stops all vectorization and background processing; your post meta timestamps and settings are preserved so they are ready if you reactivate. Deleting the plugin removes all plugin-created data from your WordPress database (post meta entries and options). Your Qdrant collections are not deleted automatically. You can remove them manually from your Qdrant Cloud dashboard if you no longer need them. Your posts, pages, and all their original content are completely unaffected either way.

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.

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.

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.