AI Providers (Sent Only When You Trigger AI)​

Summary: Antimanual Builder Pro supports multiple AI providers with optional activation through the companion plugin. This guide explains supported services, what data is sent, and when provider requests occur, helping administrators configure AI features confidently while preserving manual workflows and minimizing unnecessary external transmission.

Antimanual Builder Pro supports multiple AI providers, and provider data is sent only when you explicitly trigger an AI action. This includes AI-assisted page generation, conversational refinement, migration planning, or other AI-driven workflows enabled through the optional Antimanual plugin.

This guide explains which providers are supported, when data is transmitted, and how the provider selection fits into the broader Antimanual workflow. Use it to understand the privacy model before enabling AI features in your site.

How AI Providers Work in Antimanual

AI support is optional. If you build manually, import HTML, migrate content, or manage layouts without AI assistance, no API key is required and no provider connection is used. When AI is enabled, the Builder reads the active provider settings from the optional Antimanual Companion Plugin.

The Builder itself does not manage your API key directly. Instead, the companion plugin stores the selected provider, model, and key details, then exposes them only when an AI action is initiated.

• AI features remain off until you trigger them.
• Provider settings are managed in the companion plugin.
• Manual editing continues to work without AI.
• Provider choice can be changed without altering your core Builder workflow.

Supported AI Providers

Antimanual Builder Pro supports a flexible set of providers so teams can choose a service based on budget, policy, or preferred model quality. Availability depends on your installation and plan configuration.

• OpenAI
• Google Gemini
• Anthropic
• xAI Grok
• DeepSeek
• OpenCode Zen

For setup instructions, see . For provider selection guidance, also review .

What Data Is Sent to the Provider

Data transmission is limited to the specific AI operation you start. Antimanual does not continuously send site content to external services. Instead, it sends only the information needed for the requested task.

Depending on the feature and provider, this may include WordPress post content for knowledge base indexing, visitor chat messages, and prompts you provide during an AI workflow. For editor-based generation or refinement, the content used in that session is sent only at the moment the AI request is made.

• Content used for a page generation prompt
• Sections selected for conversational refinement
• Post content used for knowledge base indexing, where supported
• Visitor chat messages or AI search inputs, if those features are enabled

If your workflow is strictly manual, you can leave AI disabled and avoid external API usage entirely.

When Provider Data Is Sent

Provider data is sent only when an AI action is triggered. This is an important part of the plugin’s privacy model and a key distinction from always-on background processing.

• When you generate a page from a prompt
• When you refine imported content conversationally
• When you run AI-assisted migration or restructuring
• When a visitor uses AI chat or AI search, if enabled

For large or structured imports, the system can still perform deterministic analysis where AI is not required. That means some workflows can proceed without sending data to a provider at all.

Recommended Setup Workflow

To use an AI provider safely and efficiently, configure the companion plugin first, then choose the provider you want to use in the settings panel. After that, verify your API key and test a small AI action before relying on it in production.

• Install and activate the optional Antimanual Companion Plugin.
• Select your preferred AI provider.
• Enter and save the API key.
• Confirm the provider is active before starting an AI workflow.
• Use AI features only where they add value to your process.

If you need help with installation, review . If you are still deciding between manual and AI workflows, see .

Best Practices for Business Sites

For business and enterprise environments, keep provider choice aligned with internal policy and data-handling requirements. Review the provider’s terms and privacy policy before enabling production workflows, especially if you plan to use chat, indexing, or page generation at scale.

• Use only the provider approved by your organization.
• Limit AI use to the workflows that benefit most from automation.
• Test prompts and page plans on non-production content first.
• Keep API keys restricted to authorized administrators.
• Document which AI actions are enabled on the site.

Where possible, combine AI features with manual review. This helps maintain content quality while still benefiting from faster drafting, migration, and restructuring.

Troubleshooting Provider Selection

If AI features are not available, confirm that the optional companion plugin is installed and active, the provider is configured correctly, and the API key is valid. Also verify that the selected provider is supported by your current plan or integration.

• Check that the companion plugin is active.
• Confirm the provider name matches your settings.
• Verify the API key has not expired or been revoked.
• Ensure the feature you are using actually requires AI.
• Review any provider-specific usage limits or account restrictions.

If the workflow is manual-only, no provider setup is necessary. This keeps the core Builder experience available even when AI is disabled.

Summary

Antimanual Builder Pro gives you control over when and how AI providers are used. The system sends data only when you trigger an AI action, and the provider is configured centrally through the companion plugin. This design supports flexible workflows while keeping manual editing fully available.