Developer API

Most people should use Gwen through the chat and dashboard. But Gwen is also a platform: if you want to embed Gwen in your own product, trigger missions from your systems, or build on top of its capabilities, there is a programmatic surface for that.

This page is the conceptual orientation for technical users. It describes how to think about building with Gwen — keys, missions, the SDK, and integration paths — rather than a frozen endpoint reference.

Access is authenticated with workspace-scoped API keys. A key acts within a single workspace, so its reach is bounded by that workspace's data, connections, and budget.

Treat keys like any credential: keep them narrow, store them securely, and rotate them when access should change. The same isolation and approval rules that protect the dashboard apply to API access.

The core unit you work with programmatically is the mission. You can plan work, check mission status, and review the tasks, approvals, and artifacts a mission produces.

This mirrors how Gwen works in the product: a request becomes a scoped mission, the mission runs through its stages, and the results come back as reviewable artifacts you can pull into your own systems.

A TypeScript SDK (@gwendolyn/sdk) wraps the API so you do not have to hand-roll requests. It gives you a typed way to authenticate, start and track work, and read results from your own code.

If you are building an integration or an internal tool on top of Gwen, the SDK is the recommended starting point.

Gwen is built to connect through whatever a job needs: direct APIs, browser paths, code and runtime paths, and standard tool protocols.

That flexibility is deliberate — the goal is to reach the systems real work depends on, rather than being limited to a single integration style.

Programmatic access does not bypass the safety model. Actions that touch the outside world — sends, publishing, spend, deployments, record changes — are still governed by approvals and policy.

So you can automate Gwen into your stack while keeping the same guarantees that the consequential parts run with consent, not silently.