> For the complete documentation index, see [llms.txt](https://replai-1.gitbook.io/replai-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://replai-1.gitbook.io/replai-docs/getting-started/key-concepts-and-glossary.md).

# Key concepts & glossary

## Key concepts & glossary

These are the terms you will see most often in Replai.

### What do the key terms mean?

| Term                   | Meaning                                                                                                          |
| ---------------------- | ---------------------------------------------------------------------------------------------------------------- |
| **Assistant**          | The chat experience your visitors use. An assistant has its own tier, settings, sources, and saved provider key. |
| **Source / connector** | A connected body of content that Replai can search and cite. Sources are shared at the workspace level.          |
| **Tier**               | The assistant plan. Replai offers **Answer**, **Agent**, and **Live**.                                           |
| **Conversation**       | One chat thread between a visitor and an assistant. Only new conversations count toward the monthly limit.       |
| **Managed wallet**     | A prepaid balance for AI usage. Availability depends on workspace rollout.                                       |
| **BYOK**               | Bring your own key. You save your own model provider key on each assistant.                                      |
| **Handoff**            | Moving a conversation from the assistant to a human. Handoff is available on **Live**.                           |
| **Widget**             | The embedded chat surface that visitors open on your site or app.                                                |

{% hint style="info" %}
One source can feed multiple assistants.

One assistant can use multiple sources.
{% endhint %}

### Which terms matter most during setup?

Start with these:

* **Source / connector**
* **Assistant**
* **Tier**
* **BYOK**

### Which terms matter most after launch?

Watch these:

* **Conversation**
* **Handoff**
* **Widget**

### Related links

* [What is Replai?](/replai-docs/getting-started/what-is-replai.md)
* [How it works](/replai-docs/getting-started/how-it-works.md)
* [Sources overview](/replai-docs/connectors-sources/sources-overview.md)
* [Plans overview](/replai-docs/pricing-and-billing/pricing-overview.md)


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://replai-1.gitbook.io/replai-docs/getting-started/key-concepts-and-glossary.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.