Yes. Linguise stores its settings in linguise_options in wp_options, plus connection state and URL rules. SleekAI can be configured to read those entries as data sources and expose them as named variables in the system message, so the bot answers with the real config rather than a guess at how Linguise is wired.

By default, no. SleekAI is read-only against Linguise. The bot can tell an editor that a page is missing a French translation, but it does not call the Linguise API to force one. If you want write actions, you can wire a SleekAI tool with a tight capability check, but most teams keep re-translation inside the Linguise dashboard.

No. The token is stored in linguise_options and SleekAI can be configured to expose only the connection status (valid or invalid) rather than the raw value. Display conditions also keep the editorial bot scoped to logged-in editors, so even the connection status does not appear to public visitors.

Yes. Linguise handles neural translation itself; SleekAI does not translate page content. The chatbot only reads which languages are configured and whether the connection is healthy, so the choice of model (DeepL-class neural, NMT, etc.) is whatever Linguise's dashboard sets. The bot just talks about it.

Yes. Multibot lets several chatbots run on the same WordPress install with separate system messages and data sources. The public bot can know which languages are exposed in the switcher. The editorial bot can additionally see word usage and URL exclusion rules, scoped to editors only.

No. Linguise emits hreflang and serves translated HTML on its translated URLs independently of the chatbot. SleekAI only reads option values and surfaces them in answers; it does not alter the page markup, the hreflang tags, or the canonical URLs that Linguise outputs for SEO.

It can describe the rules in play, such as which engine is configured, whether the page is in the exclusion list, and whether the latest sync happened. The actual content-level fix happens in Linguise's editor or via the rules screen, but the bot saves time narrowing down which knob to turn before opening the dashboard.

Yes. Each WordPress install has its own Linguise options and its own SleekAI configuration, so the staging bot can run against a smaller language set or a sandbox API token. Conversation logs stay per environment, so test traffic does not pollute the production metrics for editorial questions.