SDKs

Gestalt provides SDKs to allow expressing app providers programmatically instead of declaratively, or to build custom providers that do not yet exist.

Read the language-specific SDK page for examples and runtime details:

API reference layout

Each language reference starts with a sectioned index so provider authors can jump to the same SDK concepts across generators:

• Provider authoring: operations, requests, responses, routers, and catalogs.
• Provider runtimes: authentication, cache, S3, secrets, workflow, agent, and hosted-runtime providers where supported by the language.
• Workflow and agent models: native request, response, event, signal, target, session, turn, message, and tool values.
• Host-service clients: cache, storage, workflow, agent, invocation, authorization, and runtime-log clients.
• Telemetry: provider-authored GenAI spans and metrics.

Native input coverage

The SDK examples use native input helpers for host-service requests where those helpers exist. That includes agent messages and tool refs, workflow events, workflow signals, and bound workflow targets in Go, Python, and Rust. TypeScript workflow examples use root helper functions such as workflowEvent, workflowSignal, and boundWorkflowTarget when a request field would otherwise expose a transport-specific shape.

Host-service responses now return native SDK objects as well. Examples should read plain fields such as session.ID, turn.id, run.id, or event.type rather than generated protocol accessors.