> ## Documentation Index
> Fetch the complete documentation index at: https://docs.ubik-agent.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Core Concepts

> Understand the fundamental building blocks of the UBIK API.

To make the most of the UBIK API, it's helpful to understand the key concepts that you'll be working with. This guide introduces the core components of our platform.

<CardGroup cols={2}>
  <Card title="Workspaces" icon="layout-dashboard" href="#workspaces">
    High-level containers for organizing your projects and data.
  </Card>

  <Card title="Documents" icon="files" href="#documents">
    The raw information you provide, like PDFs, text files, or web pages.
  </Card>

  <Card title="Tools" icon="wrench" href="#tools">
    Powerful, pre-built functions that perform complex tasks on your documents.
  </Card>

  <Card title="Skills" icon="lightbulb" href="#skills">
    Custom capabilities, instructions, and logic bundled into reusable modules.
  </Card>

  <Card title="Agent Sessions" icon="message-square" href="#agent-sessions">
    Stateful conversations with AI agents that maintain context and history.
  </Card>
</CardGroup>

## Workspaces

Think of a **Workspace** as a high-level container for your projects. It's the primary way to organize and segregate your data. Each workspace can contain its own set of documents, tools, and assistants.

* **Organization**: Group related documents for a specific project, team, or customer.
* **Isolation**: Data within one workspace is kept separate from others, ensuring privacy and control.
* **Default Workspace**: Every user has a default workspace where new documents are added if no other workspace is specified.

<Info>You can manage your workspaces through the [`/workspaces`](/en/api-reference/public-api/list-workspaces) endpoints.</Info>

## Documents

A **Document** represents any piece of content you ingest into the UBIK platform. This could be a file you upload (like a PDF or `.txt` file) or a web page you scrape. Once ingested, documents are processed and stored, making them ready to be used by Tools.

<Info>You can manage your documents through the [`/documents`](/en/api-reference/public-api/list-documents) endpoints.</Info>

## Tools

A **Tool** is a specialized function that performs a specific, complex task. Tools are designed to be powerful and asynchronous, allowing you to execute long-running jobs without blocking your application.

Examples include:

* Extracting financial data from a report.
* Summarizing a long legal document.
* Answering questions based on the content of multiple documents.

<Info>You can discover and execute tools using the [`/tools`](/en/api-reference/public-api/list-available-tools) endpoints.</Info>

## Skills

A **Skill** is a packaged set of instructions, files, and logic that define a custom capability for your AI agents. Instead of constantly rewriting complex prompts or attaching files, you can bundle them into a reusable Skill.

* **Reusability**: Build a capability once and share it across multiple agents.
* **Customization**: Provide specific files (`SKILL.md`, scripts, data) to guide the agent's behavior.
* **Access Control**: Share skills across your company or keep them private to your user account.

<Info>You can manage your skills using the [`/skills`](/en/api-reference/public-api/list-skills) endpoints.</Info>

## Agent Sessions

An **Agent Session** is a persistent, stateful conversation with an AI agent. Unlike simple chat completions, sessions maintain:

* **Conversation History**: The full context of the interaction, including branching paths.
* **Document Context**: Files and knowledge specifically linked to the conversation.
* **Tool Access**: The set of tools the agent can use to answer questions or perform tasks.

Sessions are designed for building interactive applications like customer support bots, research assistants, or data analysis tools.

<Info>You can create and manage sessions through the [`/agent-sessions`](/en/api-reference/public-api/create-agent-session) endpoints.</Info>