> For the complete documentation index, see [llms.txt](https://docs.interactive.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.interactive.ai/cli/iai_collections.md).

# iai collections

Knowledge bases (searchable tables of chunks) inside a pgvector database

## Synopsis

Manage collections within a database.

A collection is a table of chunks (rows) — each chunk is text plus its vector embedding(s) — that you search by meaning or keyword; it's what backs a knowledge base. It lives inside an existing pgvector database, so every command requires --database. Use 'iai databases create' first to provision the database.

Run 'iai collections schema' to see the body format for every --file command.

## Options

```
  -h, --help   help for collections
```

## Options inherited from parent commands

```
      --api-key string               API key for authentication
      --cfg-file string              Path to YAML config file with organization, project, and optional service definitions
      --deployment-hostname string   Hostname for the deployment API (default "https://deployment.interactive.ai")
      --hostname string              Hostname for the API (default "https://app.interactive.ai")
```

## SEE ALSO

* [iai](https://docs.interactive.ai/cli/iai.md) - InteractiveAI's CLI
* [iai collections chunks](https://docs.interactive.ai/cli/iai_collections_chunks.md) - Manage the chunks (rows) in a collection
* [iai collections create](https://docs.interactive.ai/cli/iai_collections_create.md) - Create a collection from a config file
* [iai collections delete](https://docs.interactive.ai/cli/iai_collections_delete.md) - Delete a collection and all its data
* [iai collections describe](https://docs.interactive.ai/cli/iai_collections_describe.md) - Describe a collection's configuration
* [iai collections documents](https://docs.interactive.ai/cli/iai_collections_documents.md) - Inspect documents (chunks grouped by documentId)
* [iai collections list](https://docs.interactive.ai/cli/iai_collections_list.md) - List collections in a database
* [iai collections patch](https://docs.interactive.ai/cli/iai_collections_patch.md) - Update a collection's mutable config from a file
* [iai collections schema](https://docs.interactive.ai/cli/iai_collections_schema.md) - Show the file schemas for the --file-based collection commands
* [iai collections search](https://docs.interactive.ai/cli/iai_collections_search.md) - Search a collection (single-lane vector search)
* [iai collections slots](https://docs.interactive.ai/cli/iai_collections_slots.md) - Manage a collection's vector slots and their indexes
* [iai collections stats](https://docs.interactive.ai/cli/iai_collections_stats.md) - Show a collection's chunk count, size, and index status


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.interactive.ai/cli/iai_collections.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.
