Choose Console
Use Console for human review, exploration, workflow authoring, approvals, incident response, and configuration. UI labels and routes can evolve; software should use the HTTP or MCP contracts. Start with Console documentation.Choose HTTP API v3
Use API v3 for deterministic integrations that own request construction and error handling. The generated operation reference remains organized by the underlying v2 operation identity; v3 maps those operations to resource-oriented paths without changing their authorization or business logic. Start with the Raw HTTP quickstart and the API reference.Choose MCP
Use MCP when an AI host should discover and perform Forge tasks. The default listing is deliberately bounded. Core tools cover common jobs; search and describe operations expose the wider catalog, and separate read/write callers preserve host confirmation behavior. Start with MCP host quickstart.Combine interfaces deliberately
A common pattern is Console for setup and incident response, HTTP for the production integration, and MCP for ad hoc operator assistance. These callers may use different identities and therefore see different resources. Test each credential and scope independently.Console and the HTTP API share one platform
Forge Console and HTTP API v3 reach the same platform state and the same domain services. They serve different callers, so their contracts differ.How Console connects
Console keeps run state, approvals, and other views current through live subscriptions. It submits actions with the signed-in person’s identity, and the applicable permissions and runtime governance apply.How software connects
New integrations call the documented/api/v3/* operations with the credential each operation
admits. Forge authenticates the caller, validates the request, delegates to the owning service, and
returns the published response shape. For updates, use supported webhook events
or read operation status through the API. Console’s subscriptions are not an external
subscription contract.
Sharing a backend does not make Console view models and HTTP response shapes interchangeable.
Build external integrations against the published API contract. Authorization applies on each
path, and the applicable Trust Fabric controls govern the work it invokes. See the
system overview for the wider execution model.
Related
- Quickstart: the Console and raw HTTP path.
- MCP host quickstart: connect an AI host to Forge.
- Access and credentials: which credential each interface uses.

