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

# Agent

Agents are the action layer of the GLIK platform — performing complex work invisibly, accurately, and repeatably.

The **Agent App Type** is designed for creating purpose-built, autonomous agents that perform targeted actions or complete multi-step processes — typically without a chat interface or ongoing conversation.

<figure><img src="https://3916444914-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FDBilw3zq3DIWtwBIyxN9%2Fuploads%2Fj9FweG87l7NO5unzqmS7%2Fimage.png?alt=media&amp;token=126f3098-7206-4f3d-a2ca-092b5f92dbde" alt=""><figcaption><p>GLIK Agent performs multi-step reasoning, invokes external tools, and uses variable memory to complete tasks autonomously. It shows an agent orchestrating search actions, interpreting results, and responding intelligently — without requiring ongoing user intervention.</p></figcaption></figure>

Agents can be:

* Embedded inside apps or workflows
* Triggered by API calls, events, or forms
* Assigned to handle **discrete jobs** using orchestration logic, memory, and tools

GLIK Agents are ideal when you want **AI-powered action**, not just conversation or interface logic. They act on behalf of users or systems — ingesting context, reasoning through decisions, and executing tasks across one or more services.

***

## What makes Agents different?

| Feature          | Agent App Type                                                                     |
| ---------------- | ---------------------------------------------------------------------------------- |
| **Interface**    | No frontend chat required; runs silently or behind other UIs                       |
| **Trigger**      | External input, task queue, form, system event                                     |
| **Focus**        | Task completion, decision enforcement, orchestration                               |
| **Intelligence** | Agent-specific prompt logic + memory + dynamic tools                               |
| **Examples**     | - File classification agent- Contract summarizer- Internal support ticket resolver |

## When to use Agent instead of other types

Use an **Agent** when:

* You want **autonomous execution** without relying on a user conversation
* The task is **repeatable, structured, and logic-heavy**
* You need to **embed intelligence into a backend service**, workflow step, or plugin
* A chat interface or visual logic is unnecessary for the end user

***

## Enterprise Examples

| Scenario                   | Agent Function                                   |
| -------------------------- | ------------------------------------------------ |
| Document Upload            | Automatically classify, tag, and forward file    |
| Support Intake             | Extract intent and route to correct department   |
| Procurement Review         | Enforce cost thresholds + escalate violations    |
| Legacy CRM Action Trigger  | Fill out structured forms via internal API call  |
| Onboarding Pack Generation | Generate personalized policy PDF + metadata logs |

## How Agents Fit into the GLIK Stack

* **Workflow App**: Orchestrates logic
* **Advanced Chat App**: Interfaces with users
* **Agent App**: Executes tasks or decisions autonomously
* Agents can be **spawned by other apps**, or triggered via **API/Webhook/Form** and report back silently to orchestration layers.
