Arguto

Description

Arguto is an AI chat widget that goes beyond answering questions. Built-in tools let the agent search your content, navigate visitors to the right page, search and add products to the cart, list and RSVP to events, submit contact forms, and more — all without leaving the chat.

Key features

• Pre-built agent purposes: site navigator, shop assistant, support agent, event concierge, brewing/product expert, knowledge explorer, and a general sitewide helper.
• Purpose-based tool defaults — pick the agent’s role and get a sensible starting tool set.
• Three ways to embed: sitewide auto-inject, Gutenberg block, or [arguto] shortcode.
• Knowledge sets that index pages, posts, products, events, or uploaded files (PDFs supported).
• Custom HTTP tools — expose any internal REST endpoint to the agent with a few clicks.
• Per-agent customisation: system prompt, welcome message, overlay style, enabled tools.

Optional integrations

Arguto works standalone, and lights up additional capabilities when these free plugins are active:

• WooCommerce — product search, categories, featured / on-sale lists, coupons, stock availability, client-side add-to-cart.
• The Events Calendar — upcoming events, search, detail fetch, one-click .ics download.
• Contact Form 7 — list, describe, and submit forms on the visitor’s behalf.
• WPForms Lite — same, with WPForms Lite as the form provider.
• MailPoet — list newsletters and subscribe visitors directly from the chat (double opt-in).

Arguto connects to a hosted LLM-orchestration service operated by Fluid Interactive. A valid Arguto account is required for the chat to function; the PHP plugin itself is a thin client under GPL v2.

External services

This plugin is a thin WordPress client for an AI-chat orchestration backend operated by Fluid Interactive. The plugin will not function without contacting that backend, and contacts no third party other than Fluid Interactive’s own services described below — unless the site administrator explicitly enables a “Custom HTTP Tool” that targets some other API (see the final entry in this section).

All Fluid Interactive HTTP traffic from this plugin goes to the single hardcoded host https://scripts3.fluidinteractive.com — either to a fixed endpoint on that host, or to a backend URL that scripts3 returns at runtime. There is no other hardcoded Fluid Interactive hostname in the plugin’s source.

Fluid Interactive — subscription/license information lookup

This plugin connects to https://scripts3.fluidinteractive.com/subscription-order_info.php to read the administrator’s Arguto subscription status and per-plan token-usage figures shown on the plugin’s Settings page.

It sends, when the Settings page loads and roughly every 5 minutes thereafter while the admin remains on the page: the administrator’s Arguto account e-mail and password (over HTTPS), the licence ID, the plugin’s product / version / build identifiers, an anonymous machine identifier issued to this install at registration time, the site locale (e.g. en_US), and a short context label such as “settings_panel” so Fluid Interactive can log why the request was made. The response is cached in a WordPress transient for 5 minutes.

This service is provided by Fluid Interactive: terms of service ( https://www.fluidinteractive.com/products/wp-plugins/arguto/tos/ ), privacy policy ( https://www.fluidinteractive.com/privacy-policy/ ).

Fluid Interactive — FIServices backend (server-URL resolver and chat orchestration)

This plugin connects to https://scripts3.fluidinteractive.com/fi-services/server_url.php to look up the current production URL of Fluid Interactive’s “FIServices” backend — the service that registers each install for licensing and that runs the AI chat itself. This indirection lets Fluid Interactive move the FIServices backend without every WordPress install needing a new hardcoded URL.

The first request to that resolver URL is a plain HTTPS GET with no query parameters and no body; the response body is the actual FIServices backend URL the plugin will use from then on (cached in a WordPress transient for 10 minutes). That backend URL — whichever host Fluid Interactive currently runs FIServices on — is then contacted at the following paths for the purposes described:

• POST /fi-services-register-install, once on first activation, to register this WordPress install. Sends: the site home URL, a one-time registration nonce, the plugin product name, and the plugin product version. Returns an install token that the plugin stores locally and replays on chat requests.
• POST /fi-services-license-info, on activation and roughly every 5 minutes thereafter, to refresh the install’s subscription status. Sends the same data as the subscription-order_info.php call described above, with the same context-label parameter.
• GET /agent-config and /agent-config/hash, fetched by the chat widget from the visitor’s browser each time a page that contains the widget loads, to retrieve the agent configuration (system prompt, enabled tools, overlay style) for the rendered chat session. The widget caches the result in sessionStorage.
• POST /chat, called by the chat widget from the visitor’s browser every time a visitor sends a message; the response is streamed back as model tokens.

Data sent to the FIServices backend at chat-session start (once per chat session, in the widget’s first call): the administrator’s Arguto account e-mail and password (over HTTPS), the licence ID, the plugin product / version / build identifiers, the anonymous machine identifier and the install token (signature + issued-at + install domain) issued at registration time, a per-visitor random client identifier, a per-conversation random thread identifier, and the site locale.

Data sent to the FIServices backend per chat message: the visitor’s message text. Conversation history within the current thread is tracked server-side by thread identifier; the plugin does not re-send prior messages with each new message.

Data NOT sent: the visitor’s IP address, name, e-mail address, or any other field the visitor has not typed into the chat themselves. The page URL the visitor is on is only sent if the configured agent decides to call the optional get_current_url browser tool during the conversation; it is never sent automatically.

This service is provided by Fluid Interactive: terms of service ( https://www.fluidinteractive.com/products/wp-plugins/arguto/tos/ ), privacy policy ( https://www.fluidinteractive.com/privacy-policy/ ).

Optional, administrator-configured Custom HTTP Tools

This plugin ships a small library of template entries under Arguto → Custom Tools so a site administrator can give the AI agent the ability to call a third-party HTTP API. The plugin only contacts a third-party host when the administrator explicitly creates a tool from one of these templates, supplies their own API key for that provider, and enables the tool for an agent. Out of the box, no Custom HTTP Tool is enabled and no request is made to any of these third-party hosts.

The templates that ship with the plugin reference the following third-party hosts. The plugin’s source code only contains these URLs as template defaults — the plugin itself does not POST to them unless the administrator activates the corresponding tool with valid credentials.

• Mailchimp (https://us1.api.mailchimp.com/3.0/…) — template for “subscribe a visitor to a Mailchimp audience”. When enabled, the plugin POSTs the visitor’s e-mail (and optionally first / last name) to Mailchimp using the administrator’s Mailchimp API key. This is a Mailchimp service: terms of service ( https://mailchimp.com/legal/terms/ ), privacy policy ( https://mailchimp.com/legal/privacy/ ).

• Slack (https://hooks.slack.com/services/…) — template for “post a message to a Slack channel via an incoming webhook”. When enabled, the plugin POSTs a short text message and an optional emoji prefix to the administrator’s Slack webhook URL. This is a Slack service: terms of service ( https://slack.com/terms-of-service ), privacy policy ( https://slack.com/trust/privacy/privacy-policy ).

• HubSpot (https://api.hubapi.com/crm/v3/objects/contacts) — template for “create a contact in HubSpot CRM”. When enabled, the plugin POSTs the visitor’s contact details (e-mail, name, phone, company) to HubSpot using the administrator’s HubSpot Private App token. This is a HubSpot service: terms of service ( https://legal.hubspot.com/terms-of-service ), privacy policy ( https://legal.hubspot.com/privacy-policy ).

• OpenWeather (https://api.openweathermap.org/data/2.5/weather) — template for “fetch the current weather for a city”. When enabled, the plugin GETs weather data for a city the visitor names, sending the administrator’s OpenWeather API key in the query string. This is an OpenWeather service: terms of service ( https://openweathermap.org/terms ), privacy policy ( https://openweathermap.org/privacy-policy ).

• Zapier (https://hooks.zapier.com/hooks/catch/…) — template for “trigger a Zapier catch-hook with arbitrary JSON”. When enabled, the plugin POSTs a short event name and an arbitrary JSON payload to the administrator’s Zapier webhook URL. This is a Zapier service: terms of service ( https://zapier.com/legal ), privacy policy ( https://zapier.com/privacy ).

Because these services are chosen and credentialled by the site administrator, please refer to each provider’s own terms and privacy policy before enabling a Custom HTTP Tool. The plugin authors do not control those services.