About this plugin
Apeari is an AI content editor for Gutenberg. Select a block, describe a change and review a private preview. Your live page changes only when you publish.
From an idea to an edit
- Rewrite text and add supported native sections, buttons, images and galleries using existing WordPress media.
- Preview, undo, redo and publish with conflict checks.
- Generate draft pages/posts and optionally fill supported Yoast SEO, Rank Math or SEOPress fields.
- A one-time guide can be reopened with the question-mark button at the top right.
- Edit text, heading level, alignment and button links directly; duplicate, move or remove selected blocks in the private draft.
Try requests like these
- “Rewrite this introduction to sound warmer.”
- “Add a heading and a short paragraph below this section.”
These open-ended requests require an AI connection. Local demo mode accepts a small set of example commands.
Choose your AI connection
The plugin is free; AI processing costs extra. Use your own OpenAI or Anthropic API key with a compatible JSON Schema model, billed by the provider, or an Apeari account with paid service credits. Hosted requests use the verified domain’s token balance; answers without changes may also consume credits.
Local editing and preview need no paid credits or subscription.
Hosted AI needs a verified HTTPS website and a Lite installation token. See the installation steps below. AI requests require explicit consent in Settings > Apeari.
Scope and requirements
This is the Gutenberg-only edition, also called Apeari Lite. It supports an allowlist of native blocks and preserves existing unsupported blocks. It does not edit theme files, templates or plugin code, generate executable code, add custom HTML or shortcodes, upload images or download remote media.
Existing-page editing does not change publication status. Access is limited to administrators. Apeari PRO is a separate download and cannot be active alongside this edition.
Source code and development
Editable source is bundled in src/, views/, assets/js/ and assets/css/. js load directly without compilation or minification. txt for development, packaging and asset attribution.
0. Credentials and consent are configured in Settings > Apeari.
External services and privacy
Fonts and editor assets are bundled locally. No analytics, licensing requests or background installation reports. AI is disabled until an administrator configures a provider and explicitly consents.
Submitting an AI request then contacts the selected service:
- Apeari hosted AI: https://apeari.com/v1/lite/edits
OpenAI-powered, restricted Gutenberg edit proposals and draft content. Requires an account, a verified HTTPS domain, Lite installation token and paid service credits. A useful answer without changes can consume credits.
com/regulamin
com/polityka-prywatnosci
- OpenAI: https://api.openai.com/v1/responses
com/policies/services-agreement/
com/policies/privacy-policy/
- Anthropic: https://api.anthropic.com/v1/messages
com/legal/commercial-terms
com/legal/privacy
Requests contain your instruction, up to six recent messages and necessary selected-page block context, including text, attributes and supported styles. Image titles/alt text and URLs inserted into a message may be included; image files are not sent. Draft generation sends the brief, language, sequence number and previous generated titles.
Editing requests can also synchronize a structured theme index: relative file names, hashes, CSS selectors and property names, template rendering markers, design settings and supported block capabilities. Full theme files, executable source bodies, other pages’ content and provider keys are not sent to hosted Apeari AI. Apeari stores this index separately for each domain and edition so later sessions can reuse it; changes to theme content or effective settings create a new revision.
Local knowledge is stored in a non-autoloaded WordPress option and removed on uninstall. Own-key mode sends selected knowledge directly to the selected provider. The site owner must have authority to share the data and determine applicable processing terms.
Do not submit unauthorized confidential or personal information.
Hosted Apeari results are retained for up to 30 days for retries; billing records follow the service privacy policy. Both the API and WordPress validate hosted operations against an allowlist. Disabling service consent stops new calls.
Contact the service for account/data erasure. Direct providers’ retention follows their terms.
Domain verification is administrator-initiated: Apeari calls the fixed HTTPS WordPress /apeari/v1/ownership endpoint using a single-use secret valid for 15 minutes. The endpoint provides no editing access. Multisite proof generation requires a superadministrator.
Installation tokens and provider keys are encrypted in the database using WordPress salts and remain server-side. A local PRO migration may copy settings into separate Lite options, but does not enable AI consent or migrate drafts.
Each local conversation message expires seven days after saving; refresh, new messages and undo/redo do not renew old messages. Generation metadata expires seven days after the last generation step/status change, not the last view. Private editing sessions expire after two hours of inactivity.
Expired messages are excluded from AI context, restored sessions and exports. Physical removal uses scheduled WordPress cleanup, which needs site visits or system cron. sessionStorage holds a per-tab session identifier.
A per-user preference remembers dismissal of the optional PRO introduction. Restoring conversation history is optional.
Settings > Apeari can erase your local editor data on the current site. WordPress personal data export/erasure includes Apeari data across multisite sites with pagination. User removal clears that site’s private editor data; network deletion clears it across sites.
Generated drafts are ordinary posts subject to your site’s retention policy. Uninstall removes Apeari settings, secrets, history and cleanup tasks; it keeps pages, posts, media and PRO data. txt contains further implementation details.
Updates
org build receives updates exclusively through the WordPress Plugin Directory.