channel=website.
Authentication
With an API key, workspace is inferred from the key. Optional
workspace_id in the request body must match the authenticated workspace.
Agent turns consume AI credits (
agent_turn = 2 credits, plus per-tool costs). Requires a plan with agent access (Pro for WhatsApp; website chat follows workspace AI composer limits).Send a message
POST /workspace-agent/website/chat
Run one agent turn. Provide at least one of: text, image_url, video_url, image_media_id, video_media_id.
Request body
* At least one field must be non-empty.
object
Convenience parse of
agent_response_json. Primary field is response (markdown-friendly text). Optional: tables_markdown, charts_markdown, mermaid_diagrams, image_urls, video_urls, append_footer.Agent tools
The agent has access to the same tool layer as MCP (minusweb_search_duckduckgo on some channels):
See the full MCP tool catalog for argument details.
List chat history
GET /user-agent-chats
Returns archived user/assistant turns stored in user_agent_chats. Newest first.
Query parameters
integer
Count of rows matching filters (ignores
limit/offset).Clear chat history
DELETE /user-agent-chats
Deletes all archived turns for the workspace (every channel) and clears LangGraph thread memory. Equivalent to asking the agent to run clear_workspace_chat_history.
Voice transcription (optional)
POST /workspace-agent/website/transcribe
Upload audio (e.g. audio/webm) to get a text transcript. Send the transcript as text in /chat. Requires server-side Pollinations configuration.
Errors
REST vs MCP vs agent chat
Next
MCP overview
Connect Cursor or n8n
AI content APIs
Direct generate endpoints
GPT Actions
ChatGPT Custom GPT setup