Requirements and compatibility
Check these requirements before installing. Most POM AI failures reported as "the tool does nothing" are an unmet dependency rather than a fault in the tool.
Platform
| Requirement | Value |
|---|---|
| WordPress | 6.8 or newer |
| PHP | 8.2 to 8.4 |
| PHP extension | json |
| Multisite | Supported, with a distinct license model per scope |
| Outbound HTTPS | Required, to the POM account service |
POM AI ships with the POM Framework runtime inside its release package. If WordPress reports that the framework is unavailable, the package is incomplete: install the official ZIP again rather than assembling a partial copy.
Network access
Every credit-consuming operation is a request from your server to account.pom.es, so the origin must be able to make outbound HTTPS calls. A server that blocks outbound traffic, or that sits behind a proxy which strips request headers, will show service errors even though the license itself is valid.
Two request families are involved:
- license validation and domain activation;
- POM AI service requests that estimate and then perform the work.
Both must reach the same account host. If neither can, the License panel cannot validate and the credit balance cannot load.
Per-tool dependencies
Most tools need nothing beyond WordPress. Three have real dependencies.
| Tool | Requires |
|---|---|
| AI translations | Polylang or Polylang Pro active |
| AI in visual editor | A visual editor screen that loads the TinyMCE editor |
| POM AI MCP | An MCP-compatible client; WooCommerce or POM Theme only for their respective tool groups |
The translation tool registers nothing at all when neither Polylang nor Polylang Pro is active. Its menu entry will not appear and its screen cannot be reached, even if the tool checkbox is ticked. This is intentional: the translation workflow writes into Polylang's language relationships.
The MCP server exposes WooCommerce and POM Theme tool groups only when those products are present. A missing product removes its tools from the list rather than causing errors.
User capabilities
POM AI does not invent its own roles. Each screen uses a standard WordPress capability:
| Area | Capability |
|---|---|
| The POM AI settings page | read to open it; individual tabs are restricted to administrators or editors |
| License tab | manage_options |
| Prompt templates tab | edit_posts |
| MCP server tab | Administrator |
| Writing tools (posts, pages, texts generator) | edit_posts |
| Image tools and metadata | upload_files |
| Translation tool | edit_posts |
A user who cannot see a tool usually lacks the capability, not the license.
Browser requirements
The administration screens are ordinary WordPress screens and need no special browser features, with one exception: prompt dictation records audio in the browser. It needs three things — a browser that supports audio recording, a granted microphone permission, and a secure origin, since browsers only allow microphone access over HTTPS. localhost counts as secure; a staging site on plain HTTP does not.
When any of the three is missing, the dictation control reports that recording is unsupported or that microphone access was blocked, and the surrounding tool continues to work with typed prompts.
Recordings are limited to three minutes and 4 MB. See Dictation and transcription.
Local and staging environments
Local and staging domains are treated differently by the account service. A staging host is detected from its name and counts against the plan's domain capacity in the same way a production host does. Local and development hosts — .local, .test, localhost, plain hostnames without a dot, and IP addresses — are only accepted when the license plan explicitly allows them.
If a development site cannot be authorized, that is a plan policy result, not a configuration error. See Domain limits and plan capacity.
Compatibility notes
- Caching layers. POM AI works entirely in
wp-admin, which is not cached by a public page cache. No cache configuration is required for the tools themselves. - Media handling. Image tools write into the standard media library, so any plugin that hooks attachment creation also applies to generated images.
- Page builders. Generated page and landing content is written as ordinary post content. Builder-specific shortcodes are preserved by the translation workflow when the builder registers translatable parameters.
- Security plugins. A plugin that blocks
admin-ajax.phprequests or strips custom request headers will break the estimate-and-confirm flow. Allowlist the POM AI actions rather than disabling the security rule wholesale.
Verify before continuing
Confirm all of the following, then continue with Install and activate POM AI:
- WordPress and PHP are inside the supported ranges;
- the site can make outbound HTTPS requests;
- Polylang is active if translation is planned;
- the accounts that will use POM AI hold the capabilities listed above;
- the intended domain is one the license plan can authorize.