AFRODITABOT
AfroditaBot compatibility with REEID Translate
AfroditaBot compatibility with REEID Translate is being evaluated from available plugin evidence. Adds a floating AI chat widget to WordPress and provides an admin configuration console. No specific visitor-facing translation surface is currently confirmed.
AWAITING VERIFICATION
What the available evidence establishes for AfroditaBot.
Official plugin information supports the compatibility context documented for this category.
AWAITING VERIFICATION
This integration has not yet been manually verified by REEID.
PLUGIN PROFILE
AfroditaBot is documented in the Other category with 6 concrete capabilities identified in the current evidence.
EVIDENCE COVERAGE
Plugin capabilities are documented from available official evidence. Translation support is listed only when concrete visitor-facing content is explicitly established.
COMPATIBILITY REVIEW
How AfroditaBot compatibility is evaluated
01 · Review official plugin evidence
Establish documented plugin behaviour before making any multilingual compatibility claim.
02 · Identify visitor-facing content
Determine whether the documented behaviour exposes human-readable values that visitors can see.
03 · Separate content from functionality
Keep structure, configuration, logic, integrations and runtime behaviour outside translation scope unless concrete content values are identified.
04 · Confirm translation scope
Publish supported content only when concrete visitor-facing values are explicitly established and can be validated.
PLUGIN INTELLIGENCE
What the official plugin evidence shows
Plugin capabilities
- Adds a floating AI chat widget to WordPress and provides an admin configuration console.
- Uses an external AfroditaBot Server API to verify the installation, save configuration, retrieve balance/history, and generate assistant responses.
- During installation verification, the plugin sends the admin email for server-to-server confirmation via a link; the email is not published in the widget and is not included in the browser token.
- Sends to the backend: a random installation identifier, the site URL, assistant configuration, and limited message/history needed to respond; on PayPal recharge confirmation it also sends the PayPal order identifier.
- Loads the PayPal JavaScript SDK only when recharges are enabled; payment is processed by PayPal and the plugin receives a PayPal order identifier rather than full card data.
- Relies on the OpenAI API via the AfroditaBot server to generate responses using the visitor message, configured instructions, and a limited recent history.
CONTENT BOUNDARY
AfroditaBot capabilities and translation scope are documented separately.
The available evidence documents plugin functionality, but does not currently establish a specific visitor-facing translation surface.
Functional capability alone is not treated as evidence that a value should be translated.
LIMITATIONS & QA
Verification notes
- This integration is documented for compatibility context. Visitor-facing translation scope is not listed for this category.
COMMON QUESTIONS
AfroditaBot and REEID Translate FAQ.
What does AfroditaBot do according to the available plugin evidence?
AfroditaBot has 6 concrete capabilities documented from the currently available official plugin evidence. See the Plugin Intelligence section for the individual capabilities.
Is a REEID translation surface currently confirmed for AfroditaBot?
No specific visitor-facing content values are currently confirmed as an evidence-backed translation surface for this integration.
What would establish translation scope for AfroditaBot?
The evidence must identify concrete visitor-facing values such as labels, titles, descriptions, messages or other human-readable content that can be validated through the integration workflow.
RELATED GUIDES
Continue through the compatibility library.
INTEGRATION EVIDENCE
Evaluate AfroditaBot in a multilingual WordPress workflow.
REEID documents AfroditaBot functionality separately from evidence-backed translation support so compatibility claims remain specific and testable.
Translation scope will be published when concrete visitor-facing content is established by evidence.