Do I Need an AI API Key?​

Summary: Antimanual Builder Pro only requires an AI API key for optional AI features such as generation, refinement, and AI-assisted migration. Manual editing, imports, templates, and component workflows work without one. Learn when to connect a provider and how the integration operates.

You only need an AI API key in Antimanual Builder Pro if you plan to use AI-powered generation, conversational refinement, or AI-assisted migration. Manual editing, page creation, component management, and HTML or ZIP import workflows do not require an API key.

When an AI API Key Is Required

An AI API key is required only when you activate a supported AI provider and begin using AI tools inside the builder. This includes tasks such as generating a full page from a prompt, refining content through chat, or helping plan a migrated page structure. If you never trigger these actions, you can continue working without connecting any AI service.

• Generate a page from a text prompt.
• Refine content conversationally inside the builder.
• Use AI-assisted migration for existing content.
• Connect a provider such as OpenAI, Gemini, Anthropic, Grok, DeepSeek, or OpenCode Zen, depending on your configuration.

When You Do Not Need One

Antimanual Builder Pro is designed to support a full manual workflow without external AI access. You can build pages, edit text inline, drag and drop sections, save reusable components, preview layouts across devices, and manage imported content without any API key at all. For many users, this is enough to create and maintain production-ready pages.

This means the AI connection is optional, not mandatory. If your team prefers a controlled manual process, you can keep AI disabled and still use the core builder features normally.

How AI Connections Work

Antimanual Builder Pro does not continuously send content to an AI provider in the background. Data is transmitted only when you explicitly start an AI action. This includes actions initiated from the builder interface or from the companion plugin settings when you configure your provider and key.

for the setup process, including where to paste the key and how to save the connection correctly. If you are still deciding which service to use, can help you compare supported providers and choose one that matches your budget and workflow.

Setup Requirements Before You Enter a Key

Before configuring AI, make sure the base plugin is installed and active. In some workflows, the optional Antimanual Companion Plugin is also used to connect the builder to your selected AI provider. Your WordPress and PHP versions should also meet the documented requirements so the integration can function reliably.

• Activate the free base plugin first.
• Install the companion plugin if your workflow requires AI features.
• Confirm your WordPress and PHP versions meet the required standards.
• Prepare a valid API key from the provider you want to use.

Best Practices for API Key Configuration

Use only a valid key from the provider account you plan to bill against. Antimanual Builder Pro does not charge for model usage directly; provider usage is billed by the AI vendor. If your organization manages multiple environments, keep keys separate for staging and production to reduce operational risk.

For security, the key is stored server-side and not exposed in front-end code. The settings are applied immediately after saving, so no cache clear or restart is usually required. If you run into issues, review the provider account status, permissions, and available credits before retrying.

Quick Decision Guide

If you are unsure whether you need an AI API key, use this simple rule: manual editing only does not require a key; any AI-assisted feature does. This approach keeps the builder flexible for both traditional page building and advanced AI workflows.

• No API key: manual page building, drag-and-drop layout, inline editing, components, templates, and import workflows.
• API key required: prompt-based generation, chat refinement, AI-assisted migration, and other provider-backed AI actions.
• Optional companion plugin: needed only when your AI workflow depends on it.

Troubleshooting AI Access

If AI features are unavailable after configuration, check whether the provider is selected, the key is valid, and the base plugin is active. Also confirm that the provider account is in good standing and that your plan supports the model you selected. In many cases, access problems are caused by an inactive license, an expired key, or insufficient provider credits.

For related setup details, see and . These sections explain the activation flow and the required foundation for using the builder correctly.