> ## 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.

# Concepts

> Key concepts of Animam

Understanding the fundamental concepts of Animam.

## Tenant

A **tenant** represents your Animam account. Each tenant has:

* A unique **slug** (e.g., `my-company`)
* A **corpus** (knowledge base)
* **Segments** (contexts)
* A configurable **personality**

## Corpus

The **corpus** is your chatbot's knowledge base. It's the content it uses to answer questions.

Each corpus entry has:

* A **title** (for organization)
* **Content** (the text the bot knows)
* An optional **segment** (for context)
* A **priority** (high-priority entries are preferred)

<Tip>
  Write your corpus as if you were talking to a customer. The bot naturally adopts this tone.
</Tip>

## Segments

**Segments** allow different contexts for different pages.

Example:

* Segment `landing`: general questions about your product
* Segment `pricing`: questions about pricing
* Segment `support`: technical questions

```html theme={null}
<!-- Home page -->
<script src="https://animam.ai/widget.js" data-tenant="my-site" data-segment="landing"></script>

<!-- Pricing page -->
<script src="https://animam.ai/widget.js" data-tenant="my-site" data-segment="pricing"></script>
```

## Personality

The **personality** defines how the bot expresses itself:

| Parameter     | Description                               |
| ------------- | ----------------------------------------- |
| **Name**      | The bot's name (e.g., "Alice", "Support") |
| **Title**     | Its role (e.g., "Sales Assistant")        |
| **Lore**      | Its background/context                    |
| **Tone**      | Professional, casual, friendly            |
| **Formality** | Formal or informal address                |
| **Emojis**    | Allowed or not                            |

## API Tokens

**API tokens** allow programmatic API access.

Each token has **scopes** (permissions):

* `corpus:read` / `corpus:write`
* `conversations:read`
* `settings:read` / `settings:write`
* `*` (full access)

<Warning>
  Tokens are only displayed once at creation. Store them securely.
</Warning>

## Bridges

**Bridges** are how the agent acts on third-party systems without building a parallel data store. Instead of capturing leads, orders or subscriptions in an Animam-owned table, the agent calls the system the tenant already runs and lets it persist the data — so existing automations (Zapier, notification emails, CRM connectors) keep firing untouched.

Today three bridges ship in the WordPress plugin:

| Bridge          | What the agent does                                                           | Where data lands                                 |
| --------------- | ----------------------------------------------------------------------------- | ------------------------------------------------ |
| **WPForms**     | Submits the form on behalf of the visitor through the native WPForms pipeline | WPForms entries (existing automations preserved) |
| **WooCommerce** | Searches products, adds to cart; checkout stays native                        | WooCommerce orders                               |
| **MailPoet**    | Subscribes the visitor to whitelisted lists, double opt-in preserved          | MailPoet subscribers                             |

Bridges live inside the destination system — Animam never owns the data and the tenant can audit what the agent did inside WPForms entries, WooCommerce orders or MailPoet subscribers like any other action.

## Connectors

**Connectors** authenticate the agent into outbound services so the chatbot can act on the tenant's behalf. Today the platform ships connectors for **Google Calendar** (BOOK\_MEETING + CHECK\_AVAILABILITY) and **Stripe** (COLLECT\_PAYMENT). Each connector auto-injects the tools it powers into the agent's toolbelt — no manual configuration needed once OAuth or API keys are linked.

## Multi-tenant (Enterprise)

In **Enterprise** mode, you can create **child tenants**:

* A parent dashboard to manage everything
* Independent child chatbots
* Complete white-label (no Animam mention)