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.Documentation Index
Fetch the complete documentation index at: https://docs.animam.ai/llms.txt
Use this file to discover all available pages before exploring further.
You need an API token with
settings:write, corpus:write, segments:write, and tokens: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.| Field | Description |
|---|---|
slug | Your tenant identifier (used in widget and API calls) |
plan | Current plan (free = 50 conversations/month) |
isActivated | Must be true for the widget to work on production sites |
apiKey | Your tenant API key (for chat API calls, not the Bearer token) |
2. Configure your bot
Update personality, colors, and security settings withPUT /tenants/{slug}.
All modifiable fields
| Field | Type | Description |
|---|---|---|
name | string | Tenant display name |
botName | string | Bot name shown in widget |
botTitle | string | Subtitle under bot name |
botLore | string | Background story (injected in system prompt) |
botTone | string | FORMAL, NEUTRAL, FRIENDLY, PLAYFUL, TECHNICAL |
useTutoiement | boolean | Use “tu” instead of “vous” (French) |
allowEmojis | boolean | Allow emoji in responses |
primaryColor | string | Hex color for widget |
secondaryColor | string | Secondary hex color |
showAiBadge | boolean | Show “AI” badge in widget |
allowedDomains | string[] | CORS whitelist for widget embedding (empty = allow all) |
contentPolicy | string | SFW_STRICT, SFW (default), MODERATE, UNFILTERED |
visitorAuthMode | string | jwt, otp, all, or null |
bookingCtaEnabled | boolean | Enable booking CTA in welcome screen |
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 segmentid from the response above:
Create a new segment
Segment fields
| Field | Type | Description |
|---|---|---|
name | string | Segment name |
systemPrompt | string | Full system prompt for the AI |
welcomeMessage | string | First message shown to visitors |
conversationStarters | array | Up to 4 suggested questions: [{ text, emoji }] |
isActive | boolean | Enable/disable the segment |
4. Add knowledge (corpus)
Feed your bot with content it can reference in conversations.5. Configure tools
Add interactive capabilities (forms, booking, escalation, etc.).Available tool types
| Type | Description |
|---|---|
SUBMIT_FORM | Collect structured data (contact, report, lead) |
GENERATE_QUOTE | Generate a price quote |
CHECK_AVAILABILITY | Check calendar availability (requires Google Calendar connector) |
BOOK_MEETING | Book a meeting slot |
COLLECT_PAYMENT | Generate a Stripe payment link |
ESCALATE_TO_HUMAN | Hand off to a human operator |
REMEMBER_FACT | Remember visitor preferences across sessions |
RECOMMEND_PRODUCT | Recommend products from catalog |
EXPLORE_CORPUS | Deep-search the knowledge base on demand |
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
- At chat time, Animam calls
tools/liston your MCP server - Discovered tools are injected into the AI’s available tools (prefixed
mcp_) - When the AI decides to use one, Animam calls
tools/callon your server and returns the result - Tools are cached for 5 minutes per tenant
Remove
| Field | Type | Description |
|---|---|---|
mcpToolsUrl | string | Your MCP server URL (HTTPS required) |
mcpToolsApiKey | string | Bearer token sent to your server (optional, encrypted at rest) |
mcpToolsMaxTools | number | Max tools to import, 1-20 (default: 10) |
7. Embed the widget
Add one script tag to your site:| Attribute | Description |
|---|---|
data-tenant | Your tenant slug (required) |
data-color | Override primary color |
data-segment | Target a specific segment slug |
data-position | bottom-right (default) or bottom-left |
data-visitor-id | Pre-set visitor ID for authenticated users |
Test locally
The widget works onlocalhost if your allowedDomains includes localhost:PORT or is empty.
8. Use the Chat API directly
If you prefer API integration over the widget:"stream": true and handle text/event-stream responses.
9. Dashboard access
The tenant owner can manage most settings visually at:- 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.)
-
allowedDomainsset to your production domain(s) - Widget embedded on your site
- MCP server connected (if applicable)
- Tested a full conversation end-to-end