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

# Forge platform

> Build and operate durable, governed work performed by AI agents, people, and procedures.

Forge coordinates durable work across agents, people, and external systems. Its [Knowledge system](https://docs.gloo.com/forge/knowledge.md) gives that work shared artifacts, scoped retrieval, and reviewable evidence.

> [card] [Make a first call](https://docs.gloo.com/forge/quickstart.md)
>
> Create an External App, call API v3, dispatch a workflow, and inspect the
> run.

> [card] [Understand the Knowledge system](https://docs.gloo.com/forge/knowledge.md)
>
> Learn how artifacts, sources, scoped retrieval, and human review support agents and operators.

> [card] [Choose an interface](https://docs.gloo.com/forge/get-started/choose-an-interface.md)
>
> Choose Console for people, HTTP for software, or MCP for AI hosts.

> [card] [Understand access](https://docs.gloo.com/forge/get-started/credentials-and-access.md)
>
> Match people, Personal keys, External Apps, roles, grants, and token scopes.

> [card] [Learn the key concepts](https://docs.gloo.com/forge/concepts.md)
>
> Learn how workers, workflows, capabilities, governance, knowledge, and
> operations fit together, and the principles behind them.

> [card] [Operate Knowledge in Console](https://docs.gloo.com/forge/console/knowledge.md)
>
> Find artifacts, maintain sources, review evidence, and investigate retrieval quality.

## How Forge fits together

Requests enter through the [Console, HTTP API, or MCP](https://docs.gloo.com/forge/get-started/choose-an-interface.md).
Some invoke direct operations; others start or continue [durable workflows](https://docs.gloo.com/forge/architecture/flows/workflow-execution.md)
that coordinate agents, people, and [procedures](https://docs.gloo.com/forge/concepts/procedures.md). At Forge-owned
boundaries, [Trust Fabric](https://docs.gloo.com/forge/concepts/trust-fabric.md) evaluates the authority and policy that
apply to the work. Work uses typed [platform capabilities](https://docs.gloo.com/forge/concepts/capabilities.md),
including Knowledge, and supplies the [credentials](https://docs.gloo.com/forge/get-started/credentials-and-access.md)
required by the selected provider. External systems remain outside Forge's authority.

**Forge at a glance**

### Interfaces

Forge Console · HTTP API v3 · MCP

Interfaces can also invoke direct operations.

authenticated requests enter Forge-owned boundaries

### Trust Fabric

Governance applies at Forge-owned boundaries; controls depend on the execution path.

**Governance controls:** Identity · Authority · Permissions · Spend · Autonomy · Policy · Human approval · Scope · Emergency stop · Audit · Trust evidence

#### Workflows

Agents ↔ People ↔ Procedures & scripts

Coordinates AI, human decisions, and deterministic code.

uses

#### Platform capabilities & services

Notifications · Inference · Embeddings · Sandbox · File hosting · Publishing · Knowledge · Secrets & credentials

Configured providers supply the selected capabilities.

Scoped credentials · API / MCP

### External systems

Outside Forge authority: Business applications · Content & data · Communication · Model & compute providers

A production run normally crosses several of these parts:

| Part | What it does | Read |
| - | - | - |
| Workers | A person or agent with an identity, organizational home, relationships, and bounded authority. Agent definitions add instructions, model selection, skills, and tools; people remain the source of human decisions. | [Workforce](https://docs.gloo.com/forge/concepts/workforce.md) |
| Workflows | A versioned graph of steps. Publishing fixes an executable version, and each run records the version it used. | [Workflows and runs](https://docs.gloo.com/forge/concepts/workflows-and-runs.md) |
| Tools, procedures, and capabilities | Tools are operations assigned to agents; procedures are versioned programs run in isolated sandboxes. Capabilities separate an operation from its provider, so vendor secrets stay behind the platform boundary. | [Tools and skills](https://docs.gloo.com/forge/concepts/tool-registry.md), [Procedures](https://docs.gloo.com/forge/concepts/procedures.md), [Capabilities](https://docs.gloo.com/forge/concepts/capabilities.md) |
| Trust Fabric | Decides whether an action may proceed: allow, refuse, or hold it for a person. An approval does not grant authority the original actor lacked. | [Trust Fabric](https://docs.gloo.com/forge/concepts/trust-fabric.md) |
| Knowledge | Governed context, authored in Forge or synchronized from external sources. Reads stay subject to source and scope restrictions. | [Knowledge](https://docs.gloo.com/forge/knowledge.md) |
| Operations | Console brings together runs, approvals, cost, alerts, audit evidence, workforce, and configuration. | [Observability](https://docs.gloo.com/forge/run/observability.md), [Console documentation](https://docs.gloo.com/forge/console.md) |

### A typical run

1. A person, schedule, webhook, or API client requests a published workflow.
2. Forge identifies the actor, checks access and governance, and creates durable run state.
3. Each node resolves its worker, tools, model, inputs, and bindings.
4. A node may call a capability, produce files, or pause for a human task.
5. The run reaches a terminal state and records its outcome and available evidence.
6. Operators use that evidence to change definitions, policy, or operations.

The platform persists state, but it cannot guarantee that a prompt is correct, an external provider
is available, or a human decision is wise. Design recovery for those conditions. For the
implementation-level boundaries and evidence path, continue to the
[system architecture](https://docs.gloo.com/forge/architecture/system-overview.md).

## Choose your goal

| Goal | Start here | You will use |
| - | - | - |
| Build and maintain shared knowledge | [Knowledge system](https://docs.gloo.com/forge/knowledge.md) | Artifacts, synchronized sources, retrieval, review, scope, and evidence |
| Evaluate the platform | [Key concepts](https://docs.gloo.com/forge/concepts.md) | Concepts, design principles, and current limitations |
| Build an agent or workflow | [Define an agent](https://docs.gloo.com/forge/build/define-an-agent.md) and [Compose a workflow](https://docs.gloo.com/forge/build/compose-a-workflow.md) | Console, skills, tools, procedures, capabilities |
| Operate production work | [Observability](https://docs.gloo.com/forge/run/observability.md) | Runs, approvals, observability, cost, audit, emergency controls |
| Integrate software | [Integration reference](https://docs.gloo.com/forge/reference.md) | API v3, OAuth client credentials, OpenAPI, webhooks |
| Connect an AI host | [MCP quickstart](https://docs.gloo.com/forge/quickstart/mcp-host.md) | Hosted MCP or the local stdio server |
| Use the operator UI | [Forge Console documentation](https://docs.gloo.com/forge/console.md) | Task guides for the current Console |

## Why Forge

A model API can produce an answer. It does not, by itself, provide a durable process,
organizational authority, a safe boundary around business systems, human decision handling, cost
control, or an audit trail. Forge exists for work where those concerns are part of the product.

### Problems Forge addresses

* **Work outlives a request.** A workflow run has persisted state and a terminal outcome. Versions,
  runs, node state, files, and outcomes survive waits, retries, and deployments.
* **Authority depends on context.** People, agents, and External Apps act through explicit
  identities. Roles, scoped grants, credential scopes, resource reach, and runtime governance all
  affect whether an action may proceed.
* **External access needs a boundary.** Tools and procedures call capabilities through platform
  boundaries instead of carrying vendor credentials into prompts or sandboxes.
* **People remain part of the process.** Approval and requested input are durable work states with
  eligible decision makers and recorded responses; work resumes from the recorded decision.
* **Operators need evidence and controls.** Run state, decisions, files, usage, cost, audit events,
  cancellation, and emergency controls are available to operators with the corresponding access.

### What Forge does not do

Forge does not make an unsafe tool safe, infer the right permission model, guarantee output
quality, or eliminate provider failures. It does not replace security review, data governance,
incident response, or business ownership. A durable run can durably execute a bad design.

Teams still own prompts, tool risk, minimal access, approval policy, testing, budgets, alerts,
recovery, data retention, and the decision to deploy or resume work.

Use Forge when work is multi-step, crosses systems, needs a person, requires scoped authority, or
must be operated and audited. A direct model call may be a better fit for a short-lived, low-risk
interaction with no durable state.

Forge has three interfaces: Console for people, HTTP API v3 for software, and MCP for AI hosts. [Choose an interface](https://docs.gloo.com/forge/get-started/choose-an-interface.md).


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.