Skip to main content
This guide walks you through configuring an Animam tenant entirely via API. By the end, you’ll have a working chatbot with custom knowledge, tools, and optionally your own MCP server connected.
You need an API token with settings:write, corpus:write, and segments:write scopes. Ask your Animam admin to create one, or generate it from the dashboard at /dashboard/{slug}/tokens.

1. Check your tenant

Verify your tenant exists and note its current configuration.
Key fields in the response:

2. Configure your bot

Update personality, colors, and security settings with PUT /tenants/{slug}.

All modifiable fields

Domain format: exact match (app.example.com), bare domain (example.com), or wildcard subdomain (*.example.com). If allowedDomains is empty, all origins are allowed.

3. Set the system prompt (via segments)

The system prompt lives on the segment, not the tenant. Every tenant has a default segment.

List segments

Update the default segment

Use the segment id from the response above:

Create a new segment

Segment fields

4. Add knowledge (corpus)

Feed your bot with content it can reference in conversations.
You can also sync corpus from a URL:

5. Configure tools

Add interactive capabilities (forms, booking, escalation, etc.).

Available tool types

See the Tools Guide for detailed configuration of each type.

6. Connect your MCP server (optional)

If you have your own MCP server, Animam can auto-discover and proxy its tools into the chatbot.
MCP tools require Builder plan or above. The MCP server must expose tools via Streamable HTTP transport.

Configure

Check configuration

How it works

  1. At chat time, Animam calls tools/list on your MCP server
  2. Discovered tools are injected into the AI’s available tools (prefixed mcp_)
  3. When the AI decides to use one, Animam calls tools/call on your server and returns the result
  4. Tools are cached for 5 minutes per tenant

Remove

7. Embed the widget

Add one script tag to your site:
Optional attributes:

Test locally

The widget works on localhost if your allowedDomains includes localhost:PORT or is empty.

8. Use the Chat API directly

If you prefer API integration over the widget:
Response:
For streaming (SSE), set "stream": true and handle text/event-stream responses.

9. Dashboard access

The tenant owner can manage most settings visually at:
Login via magic link (email). The dashboard provides:
  • Bot personality, tone, avatar, colors
  • Corpus management (add, edit, delete entries)
  • Tools configuration (all types)
  • Conversation history and visitor profiles
  • Analytics and usage stats
  • API token management
Not yet in dashboard: allowedDomains, mcpToolsUrl, content policy, visitor auth mode. Configure these via API.

Checklist

  • Tenant created and isActivated: true
  • Bot personality configured (name, tone, system prompt)
  • Corpus populated with key content
  • Tools added (forms, escalation, etc.)
  • allowedDomains set to your production domain(s)
  • Widget embedded on your site
  • MCP server connected (if applicable)
  • Tested a full conversation end-to-end