POM AI documentation
POM AI adds assisted writing, translation, image, metadata, website-copy and controlled WordPress automation tools to the WordPress administration area. This documentation explains the public product: what each tool is for, how to use it safely, what consumes credits and how to review the result. It intentionally does not identify the underlying AI providers or models.
Choose your starting point
| If you want to… | Start with… |
|---|---|
| Install POM AI for the first time | Install and activate POM AI |
| Understand the product before enabling tools | What POM AI is |
| Check whether this site can run it | Requirements and compatibility |
| Find a screen | Tour the POM AI interface |
| Authorize a site | License and domains |
| Understand billing and consumption | POM AI credits |
| Generate or revise copy | Writing tools |
| Translate content | Translation |
| Generate or edit media | Image tools |
| Dictate a prompt | Dictation and transcription |
| Improve a request | Prompting guides |
| Connect an MCP client | POM AI MCP |
| Integrate or extend the plugin | Developer documentation |
The five-minute first run
- Install and activate POM AI on the intended site.
- Open Settings → POM AI → License.
- Paste a valid POM AI license key and select Save and validate. Validation authorizes the current domain, subject to the plan's domain capacity.
- Confirm that the panel reports a valid license and that the credit balance loads.
- Complete the short description and relevant profile sections under Settings → POM AI → AI Setup.
- Enable one tool under Settings → POM AI → AI Tools.
- Open that tool, use a small non-confidential example, read the credit estimate and confirm once.
- Review the draft before saving or publishing it.
POM AI does not require a separate key from an AI provider. The product license identifies the account, authorizes the current domain and determines which account balance pays for credit-consuming requests.
A useful mental model
POM AI has three distinct layers:
- Local WordPress interfaces collect the request, check permissions and place the result into the editor or the media library.
- Licensed POM AI services perform the credit-consuming work on the POM account service.
- POM AI MCP exposes a controlled set of local WordPress, POM Theme, WooCommerce and POM Cache operations to compatible clients. An ordinary management operation does not become AI generation merely because POM AI exposes it.
Keeping the layers apart makes troubleshooting shorter: a license or credit error is not a WordPress capability error, and neither is an MCP scope or write-gate error.
Before publishing generated work
- Verify facts, dates, prices, names, links and any regulated claim.
- Edit the result into the site's own voice; do not publish an unreviewed draft.
- Confirm that no confidential, personal or customer data was sent unnecessarily.
- For images, verify usage rights, crop, alternative text and every page a replacement affects.
- For translations, review terminology, locale conventions, links, placeholders and formatting.
- For state-changing MCP operations, read the current state first, use a dry run where offered, and fetch the result after the write.
Review AI output responsibly covers each of these properly.
What this documentation never asks you to share
Do not place license keys, MCP API keys, OAuth access or refresh tokens, authorization codes, cookies, customer data or unredacted logs in screenshots, prompts or support messages. A safe support report needs the site URL, the time, the tool name, the shape of the input and the exact public error code — not the secret that authenticated the request.