Make a first call
Create an External App, call API v3, dispatch a workflow, and inspect the
run.
Understand the Knowledge system
Learn how artifacts, sources, scoped retrieval, and human review support agents and operators.
Choose an interface
Choose Console for people, HTTP for software, or MCP for AI hosts.
Understand access
Match people, Personal keys, External Apps, roles, grants, and token scopes.
Learn the key concepts
Learn how workers, workflows, capabilities, governance, knowledge, and
operations fit together, and the principles behind them.
Operate Knowledge in Console
Find artifacts, maintain sources, review evidence, and investigate retrieval quality.
How Forge fits together
Requests enter through the Console, HTTP API, or MCP. Some invoke direct operations; others start or continue durable workflows that coordinate agents, people, and procedures. At Forge-owned boundaries, Trust Fabric evaluates the authority and policy that apply to the work. Work uses typed platform capabilities, including Knowledge, and supplies the credentials required by the selected provider. External systems remain outside Forge’s authority. A production run normally crosses several of these parts:A typical run
- A person, schedule, webhook, or API client requests a published workflow.
- Forge identifies the actor, checks access and governance, and creates durable run state.
- Each node resolves its worker, tools, model, inputs, and bindings.
- A node may call a capability, produce files, or pause for a human task.
- The run reaches a terminal state and records its outcome and available evidence.
- Operators use that evidence to change definitions, policy, or operations.
Choose your goal
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.

