Identity binding
Connect a runtime to an OAS identity and carry that identity through the interfaces your application exposes.
Interfaces for agent builders
Build the agent. Connect the essentials.
Forge brings identity, capabilities, lifecycle, communication, and collaboration into a shared set of agent interfaces.
ForgeIllustrated study
A composition, not a black box.
Compose the primitives. Keep their boundaries explicit.
01 / Built for a purpose
A common contract for different runtimes.
An agent needs more than a model call. It needs to identify itself, ask for capabilities, report its health, use tools, and coordinate with other participants. Forge organizes those responsibilities around the ANVIL interface contracts.
Capability and tool boundaries
Describe the tools an agent can use and the permissions it needs. The SDK interface does not replace the service or chain policy that enforces access.
A visible lifecycle
Health, telemetry, and lifecycle interfaces help a host understand whether an agent is starting, operating, or needs attention.
Communication and collaboration
Shared contracts organize messages and work between agents. Choose a documented binding and verify the modules supported by its current release.
The details matterGood questions.
Good questions.
Clear answers.
Is every Forge method an on-chain operation?
No. Forge is an agent SDK. Many operations belong to a runtime or external service. Use Sigil’s transaction and RPC documentation for the subset that interacts with the chain.
Keep exploringOne capability.