內容簡介
WLN Multi-Provider AI Chat 是一款為 WordPress 網站添加浮動聊天小工具的外掛，允許管理員選擇 AI 端點和模型，並配置小工具以生成回覆，提升網站互動性。
【主要功能】
• 支援多種 AI 端點如 OpenAI、Google Gemini 等
• 本地數據庫知識索引可用於公開文章
• 可配置的對話歷史與頁面上下文
• 自訂小工具顏色、尺寸與字型
• 訪客會話簽名與濫用防範限制
• 翻譯友好的介面，支援 Polylang 整合
外掛標籤
開發者團隊
原文外掛簡介
WLN Multi-Provider AI Chat adds a floating chat widget to a WordPress site. Site administrators choose an AI endpoint and model, supply credentials, and configure the widget. Replies are generated by the configured service.
Features include:
OpenAI, Anthropic Claude, Google Gemini, YandexGPT, OpenRouter, local Ollama, and custom OpenAI-compatible endpoints.
A local database knowledge index for published, publicly viewable posts and pages without passwords, and administrator-supplied Markdown documents.
Optional page context and configurable conversation history sent with a question.
Widget colors, dimensions, position, fonts, and welcome messages.
Signed visitor sessions, abuse-prevention rate limits, encrypted API-key storage, and administrator permission checks.
Local conversation statistics, configurable retention, and visitor-controlled history deletion.
Translation-ready interface and integration with Polylang for saved widget strings. Translations are distributed through translate.wordpress.org.
All included plugin features are available without a plugin license or subscription. External AI providers may require accounts and charge for their processing. Request limits protect the site from abuse; they do not unlock paid plugin features.
This is an independent plugin and is not affiliated with the listed AI providers.
External services
No provider request is made merely by activating the plugin or opening the widget. After the administrator configures the service, requests are made when a visitor sends a message or an administrator clicks Test Connection. The connection test sends a fixed test message through the same prompt-building process, so configured system instructions and any relevant knowledge excerpts may also be included.
Requests contain the API credential, selected model and generation parameters, system instructions, the current message and a limited conversation history. Relevant knowledge excerpts may be included. If page context is enabled, the current page URL, title, content excerpt and selected text may also be included. Yandex requests additionally include the configured project/folder identifier. The provider sees the server’s network address and HTTP request metadata. Visitor IP addresses and browser user agents are not deliberately included in AI prompt payloads.
Only the configured endpoint receives these requests. Asynchronous Yandex generation may require follow-up status requests. There is no developer telemetry, advertising tracker or license-verification service. Provider documentation links are ordinary links and open only when clicked.
OpenAI
Used to generate chat replies at https://api.openai.com/v1. Receives the request data described above when selected and a chat or test request is submitted.
Terms: https://openai.com/policies/services-agreement/
Privacy: https://openai.com/policies/privacy-policy/
Anthropic
Used to generate Claude replies at https://api.anthropic.com/v1. Receives the request data described above when selected and a chat or test request is submitted.
Terms: https://www.anthropic.com/legal/commercial-terms
Privacy: https://www.anthropic.com/legal/privacy
Google Gemini
Used to generate replies at https://generativelanguage.googleapis.com/v1beta. Receives the request data described above when selected and a chat or test request is submitted.
Terms: https://ai.google.dev/gemini-api/terms
Privacy: https://policies.google.com/privacy
Yandex Cloud
Used to generate YandexGPT replies at https://ai.api.cloud.yandex.net/v1 or another administrator-configured Yandex Foundation Models endpoint. Receives the request data described above, including the project/folder identifier, on chat and test requests; operation identifiers are sent when polling asynchronous results.
Terms: https://yandex.com/legal/cloud_termsofuse/en/
Privacy: https://yandex.com/legal/confidential/en/
OpenRouter
Used to route generation requests through https://openrouter.ai/api/v1 to the selected model provider. Receives the request data described above on chat and test requests and forwards content to the upstream provider. Review that model provider’s policies as well.
Terms: https://openrouter.ai/terms
Privacy: https://openrouter.ai/privacy
Ollama and custom endpoints
The Ollama preset uses http://localhost:11434/v1 on the WordPress server. The same request data is sent to that local service on chat and test requests. The plugin does not contact ollama.com automatically. Whether an Ollama model or a custom gateway forwards data elsewhere depends on how the administrator configures that service.
Ollama service terms: https://ollama.com/terms
Ollama privacy: https://ollama.com/privacy
Local Ollama software license: https://github.com/ollama/ollama/blob/main/LICENSE
For a custom endpoint, the destination and applicable terms/privacy policy are determined by the administrator. Review those documents before configuration and disclose that service in the site’s privacy notice. The plugin cannot identify the operator or terms of an arbitrary URL.
Poolside (optional custom endpoint)
When an administrator configures https://inference.poolside.ai/v1 and a supported model, Poolside generates replies using the same request data and triggers described above. The plugin allows a longer request timeout for Poolside endpoints. No Poolside request is made unless that endpoint is explicitly configured.
Terms: https://poolside.ai/legal/eula
Privacy: https://poolside.ai/legal/privacy
License
GPL version 2 or later. See LICENSE.
