Site Assistant

Create an AI assistant for site visitors. It uses the AI integration of this project, so the key of the chosen provider must be in the vault (openai: openai_api_key, anthropic: aapi_anthropic_key, groq: groq_api_key, openrouter, mistral, cloudflare-workers-ai: see their integration). Visitors can never change the model, instructions or limits. scope sets how broadly it may answer: "strict" (default) only about topic, "related" also briefly about closely related questions, "open" anything. Do NOT put secrets, internal prices or private data in system_prompt: a determined visitor may get the model to reveal it. After creating, call test-assistant once to check it works.

Change an assistant. Only send what changes. Send an empty string for topic or off_topic_reply to clear it. Set is_active false to pause (visitors then see fallback_message).

Delete an assistant permanently. To pause it instead, use update-assistant with is_active false.

All assistants of this project with their settings, today's number of answers against daily_cap, whether the provider key is in the vault, and the platform limits.

No input parameters required.

Send one test message with exactly the visitor settings (instructions, scope, limits) and see the answer, or the error from the AI provider. Counts towards daily_cap. Use this after create or update.

The current visitor asks the assistant a question. Returns {reply, limited}. When limited is true, reply holds the fallback message and reason says why ("daily_limit", "visitor_limit", "network_limit", "inactive", "unavailable"). For a conversation, the page keeps the earlier messages itself and sends them as history; nothing is stored on the server.