TWP Technologies, LLC

Sentient Forms adds AI actions to Gravity Forms submissions: lead scoring (A/B/C/Reject), spam review, entry summaries, content checks, and WordPress logs. Other form builders are not supported in this release.
A TWP Technologies, LLC product. Product site: https://sentientforms.com. Public development: https://github.com/TWP-Technologies/sentient-forms-wp-plugin.
Local settings, action definitions, form mappings, execution logs, provider settings, and saved results are stored in WordPress.
Use your OpenRouter key for direct execution, or connect Sentient Forms Managed Execution for managed paid features. AI-generated Site Context needs Managed Execution or a paid, web-capable OpenRouter model; you can also write it manually.
<h3>Source</h3>
JavaScript and CSS in <code>assets/dist</code> are generated from <code>admin-app</code> in the public release source: https://github.com/TWP-Technologies/sentient-forms-wp-plugin/tree/v0.3.14. Build with <code>cd admin-app</code>, <code>bun install --frozen-lockfile</code>, and <code>bun run build:wp</code>.
<h3>External services</h3>
This plugin sends data to external services only for provider paths and features an administrator enables.
OpenRouter direct execution:
<ul>
<li>Service: OpenRouter</li>
<li>Endpoint: https://openrouter.ai/</li>
<li>When used: after an administrator connects OpenRouter and runs direct provider validation, a form action, or AI-generated Site Context. Site Context needs a paid, web-capable OpenRouter model.</li>
<li>Data sent: selected form fields, prompt/action instructions, model identifier, and request metadata for form actions. Site Context sends the site URL, public-site research prompt, selected model, and request metadata; web-capable models may search or fetch public pages.</li>
<li>Account required: an OpenRouter account/API key. Site Context requires a paid, non-free, web-capable model.</li>
<li>Terms: https://openrouter.ai/terms</li>
<li>Privacy policy: https://openrouter.ai/privacy</li>
</ul>
Sentient Forms Managed Execution:
<ul>
<li>Service: Sentient Forms</li>
<li>Endpoint: https://api.sentientforms.com/</li>
<li>When used: optional managed account, billing, metering, managed model execution, support diagnostics, or administrator-enabled managed features.</li>
<li>Data sent: account/site identifiers, billing state, and, for managed AI execution, selected form fields and prompt/action instructions. Managed Site Context sends the site URL, public-site research prompt, selected model, and request metadata; web-capable models may search or fetch public pages.</li>
<li>Account required: a Sentient Forms account may be required for managed paid features. Direct OpenRouter does not require Sentient payment.</li>
<li>Terms: https://sentientforms.com/terms</li>
<li>Privacy policy: https://sentientforms.com/privacy</li>
</ul>
Optional Sentient Forms telemetry:
<ul>
<li>Service: Sentient Forms</li>
<li>Endpoint: https://api.sentientforms.com/v1/sites/telemetry and https://api.sentientforms.com/v1/telemetry/async</li>
<li>When used: only after an administrator opts in and the site has a connected Sentient Forms site identity.</li>
<li>Data sent: telemetry consent state and metadata-only events: plugin/runtime versions, provider path, action code, execution request ID, adapter, job status, attempt counts, and sanitized error or warning codes.</li>
<li>Data not sent: form field contents, prompts, model outputs/results, raw error messages, visitor identifiers, saved provider secrets, billing secrets, or OpenRouter BYOK payloads.</li>
<li>Account required: a Sentient Forms site identity is required for telemetry sync and delivery.</li>
<li>Terms: https://sentientforms.com/terms</li>
<li>Privacy policy: https://sentientforms.com/privacy</li>
</ul>
Administrator-configured webhooks:
<ul>
<li>Service: the webhook URL entered by the site administrator.</li>
<li>Endpoint: the administrator-provided webhook URL.</li>
<li>When used: only when an administrator explicitly enables a post-execution webhook for an action.</li>
<li>Data sent: form entry identifier, local action context, action result, and configured webhook metadata needed by the receiver.</li>
<li>Account required: depends on the administrator-provided webhook receiver.</li>
<li>Terms: provided by the administrator-chosen webhook receiver.</li>
<li>Privacy policy: provided by the administrator-chosen webhook receiver.</li>
</ul>
Realtime Clarification Assistant:
<ul>
<li>Service: OpenRouter direct execution or Sentient Forms Managed Execution, depending on the selected provider path.</li>
<li>Endpoint: the same provider endpoint disclosed above for the selected execution path.</li>
<li>When used: only when an administrator maps the Realtime Clarification Assistant to a Gravity Forms form and enables realtime suggestions.</li>
<li>Data sent: visible field values collected before submission, realtime action instructions, form metadata, selected model identifier, and request metadata needed to return suggestions.</li>
<li>Account required: depends on provider path. OpenRouter requires an account/API key. Managed execution may require a Sentient Forms account.</li>
<li>Visitor disclosure: site owners should disclose realtime AI suggestions in their public privacy policy or form copy before enabling this feature, because selected in-progress field values can be sent before final submission.</li>
<li>Terms and privacy policy: the same provider terms and privacy policy disclosed above for the selected execution path.</li>
</ul>
No OpenRouter or Sentient AI execution request should be sent until an administrator has configured and accepted the relevant provider disclosure. No telemetry event should be queued or sent until an administrator opts in and a Sentient Forms site identity exists.

Sentient Forms

AI actions for Gravity Forms: lead scoring, spam review, entry summaries, and WordPress logs.

micromax

HyperMew AI Translator is a high-performance, developer-friendly translation plugin that integrates modern language model routing directly inside your WordPress post edit screens. Powered by the OpenRouter API, it translates your content fields to a variety of target languages within seconds.
Key features include: 
* Gutenberg & Classic Editors: Complete sidebar integration in Gutenberg and a custom metabox inside the Classic Editor. 
* Granular Field Selection: Translate the Title, Content, Excerpt, or any arbitrary custom fields simultaneously. 
* Custom Field Mapping: Define translatable fields dynamically using custom CSS selectors to target specific page elements. 
* Performance Caching: Local caching via the WordPress Transients API preserves translations for 24 hours to speed up repeated edits and minimize API usage. 
* System Prompt Customization: Customize the core instructions sent to translation models, with full support for HTML tag preservation and specific typography rules. 
* Dynamic Model Selection: Connect to any model on OpenRouter, with visual badges highlighting free tiers, fast options, and auto-routing models. 
* Tabbed Settings Dashboard: A fully responsive settings page with slide-in tab transitions and persisted navigation states.
<h4>External Service Integration</h4>
This plugin relies on the external service OpenRouter (https://openrouter.ai) to perform translation requests. 
* Service URL: https://openrouter.ai 
* Terms of Service: https://openrouter.ai/terms 
* Privacy Policy: https://openrouter.ai/privacy 
* Data Transmission: When you perform a translation, the selected text, chosen target language, system prompt guidelines, and your configured API key are securely transmitted via HTTPS requests to OpenRouter’s API endpoint (https://openrouter.ai/api/v1/chat/completions). No other personal or site details are shared.
<h3>Help & Guide</h3>
<h4>Step-by-Step Translation Guide</h4>
<ol>
<li>Open any supported Post or Page.</li>
<li>Write or paste your content in the Title, Content, Excerpt, or Custom text area.</li>
<li>Observe that the translation panel automatically detects which fields contain text and lights them up.</li>
<li>Select the field(s) you wish to translate.</li>
<li>Select your target language from the buttons group.</li>
<li>Click Translate Now.</li>
<li>The fields will temporarily disable during execution and then update automatically.</li>
</ol>
<h4>System Prompt Best Practices</h4>
Use the system prompt to guide your translation model. Always keep the <code>{target-lang}</code> placeholder, which is replaced dynamically. To prevent models from breaking layouts, instruct them to preserve: 
* WordPress blocks and shortcodes (e.g., <code>[gallery]</code>) 
* HTML tags and attribute values (e.g., class names, URLs) 
* Typography preferences (e.g., prohibiting em dashes)

HyperMew AI Translator

Translate WordPress titles, content, excerpts, and custom fields via AI services. Works with both Gutenberg and Classic Editors.

Sentient Forms vs HyperMew AI Translator