Which AI Provider Should I Use?​

Summary: Learn which AI provider to use in Antimanual Builder Pro, how to compare supported options, and what to verify before enabling AI features on a live WordPress site.

The best AI provider for Antimanual Builder depends on your workflow, compliance requirements, and the type of content you want to generate. Antimanual Builder Pro supports several providers, including OpenAI, Google Gemini, Anthropic, xAI Grok, DeepSeek, and OpenCode Zen, and the selected provider is used only when you explicitly trigger an AI action.

If you build pages manually, migrate existing content, or manage layouts without AI assistance, no provider choice is required. If you plan to use prompt generation, conversational refinement, knowledge-base-assisted workflows, or AI page planning, choose the provider that best matches your technical, operational, and policy needs.

How to Choose the Right AI Provider

For most sites, the right provider is the one that balances quality, cost, and operational control. In Antimanual, the active provider is configured in the optional companion plugin, which stores your API key and model selection separately from the Builder interface.

• Choose OpenAI for broad compatibility and general-purpose content generation.
• Choose Google Gemini if your workflow is tied to Google services or you want flexible cost management.
• Choose another supported provider when your organization has a specific integration, pricing, or compliance requirement.

If you are still deciding between a manual workflow and AI-assisted editing, review before enabling a provider. If you are preparing your environment, review Optimizing WordPress: Disabling Forum and eCommerce Features While Retaining Helpdesk Functionality to confirm the free base plugin and optional companion plugin are installed correctly.

Recommended Provider Selection by Use Case

Provider selection should follow the primary task you intend to automate. A single provider can support prompt generation, page refinement, migration planning, or knowledge-base workflows, but the best results usually come from matching the provider to the job.

• OpenAI: A strong default option for general content generation and wide model availability.
• Google Gemini: Suitable for Google-based workflows and teams that prefer Google AI tooling.
• Anthropic: Useful when your team values structured, conversational assistance and policy-aware output.
• xAI Grok, DeepSeek, OpenCode Zen: Consider these when your environment, budget, or approved vendor list requires a different supported provider.

Best Practices for Business Sites

For business and enterprise sites, provider choice should align 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 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.

When possible, combine AI features with manual review. This approach helps preserve quality while still improving speed for drafting, restructuring, and migration tasks.

What Must Be Installed Before You Use AI

AI features depend on the optional Antimanual companion plugin. The free base plugin must also be active, and your WordPress and PHP versions must meet the required standards. If the environment is not compatible, AI features may not be available even if a provider is selected.

• Install and activate the free Antimanual Builder base plugin.
• Install and activate the optional companion plugin for AI features.
• Confirm your WordPress and PHP versions meet the required standards.
• Add your API key and verify that the provider connection is active.

The Builder reads the active provider from the companion plugin when an AI action is triggered. This keeps credentials centralized and allows manual Builder features to continue working even if the AI connection is inactive.

How to Verify Your Provider Is Working

After configuration, confirm that the selected provider responds normally before relying on it for production work. A short test is usually enough to validate the connection and reveal any model, billing, or permission issues.

• Save the provider settings in the companion plugin.
• Start a small prompt-based generation task.
• Try a conversational refinement action.
• Check for provider-specific error messages if the request fails.

If the AI tools remain unavailable, confirm that the companion plugin is active, the API key is valid, and the selected provider is supported in your current setup. For troubleshooting installation and activation, see .

Important Privacy and Data Notes

Antimanual sends provider data only when you explicitly trigger an AI action. This includes supported AI-assisted page generation, conversational refinement, migration planning, and related workflows enabled through the companion plugin.

Provider data may include the content used for generation, knowledge-base indexing data, visitor chat messages, and prompts configured in the admin area. Because these requests are sent through your own API key, you should evaluate privacy obligations before enabling AI on a live site.

In short, choose the provider that matches your workflow and governance requirements, verify the connection carefully, and use AI only where it adds measurable value.