Forge documentation

Start building

Choose your language and verify a small, real Forge operation.

Forge is a family of libraries. Start with the implementation your application uses, verify a no-network message example, then supply a model and an explicit tool policy.

Choose your language

LanguageImport boundaryFirst success
Rustforge_core, aggregate forge_sdkRust quickstart
TypeScript@forge-sdk/core, aggregate @forge-sdk/sdkTypeScript quickstart
Pythonforge.core inside distribution forge-sdkPython quickstart
Gogithub.com/l1fe-labs/forge-go/coreGo quickstart
SwiftForgeCore, aggregate ForgeSDKSwift quickstart
Kotlincom.l1fe.forge.coreKotlin quickstart

Build up in layers

  1. Construct a message and verify its text without contacting a provider.
  2. Supply a concrete model for your language. Configure the provider's endpoint and a model available to your account.
  3. Add a bounded tool loop. Keep approval explicit; several implementations default to automatic approval.
  4. Add an OAS identity and scoped authorization when the application needs accountable actions.
  5. Verify the selected deployment target and conformance scenarios before release.

A root identity is not an agent identity: create the human root, then derive an agent child. A signing identity does not automatically grant a capability. Package source versions do not establish public registry availability or six-language parity.

Browse every library or read the ANVIL specification.

On this page