No. The bot only needs the plugin's configuration metadata, which is stored in WordPress options and post meta. The Kit API key reference itself stays out of the system prompt. Anything that requires the API itself is delegated to webhooks or tool calls you wire up explicitly, not auto-exposed.

If the subscriber is logged in or identified by email cookie, yes. Kit's plugin records tag and form assignments in post meta, and SleekAI maps those entries into prompt variables so the bot can name the exact form and the post URL it lives on, not a generic answer.

Landing pages hosted on Kit aren't part of your WordPress site, so the bot won't introspect them. It still answers correctly about embedded forms and shortcodes, and you can pass a small mapping table of landing-page slug to form name as a SleekAI variable for completeness.

Yes. The bot can explain how the [convertkit_broadcasts] shortcode pulls past broadcasts onto the page, why a recent send may not yet show up, and how the date format and limit attributes change the output, using the exact vocabulary from the Kit documentation rather than invented terms.

Yes. Multibot mode runs several SleekAI chatbots on one site. Common setup is a sales bot on the marketing pages, a subscriber support bot on the help and account pages, and an editor-facing bot in the WP Admin that can answer questions about per-post form assignments.

Yes. The wrapper that exposes the bot to public traffic enforces rate limits per IP and runs a guideline filter that blocks attempts to extract the system prompt, jailbreak the model, or fetch credentials. You stay in control of the model key and can cap monthly spend at the provider level.

No. The variable mapping excludes sensitive subscriber data by default. For logged-in users the bot can reference their own email and form history, but it cannot enumerate other subscribers or list members, since that data is not in the WordPress scope SleekAI reads.

Yes, since the option and post meta keys haven't changed materially across versions. If you are on a release before the Kit rebrand, the bot still reads _wp_convertkit_settings and _wp_convertkit_post_meta correctly. You can update the visible name to either ConvertKit or Kit in the system prompt.