---
title: "The Guild API is now public"
canonical: "https://www.guild.ai/blog/engineering/guild-api-announcement"
---

# The Guild API is now public

- **Category:** Engineering
- **Author:** Logan Valeski
- **Published:** Sep 16, 2026
- **Reading time:** 5 min

Guild has always been good at running agents. Now it's just as good at being run by everything else you already use.

Today we're opening up the Guild API. It gives external systems a first-class way to act on a Guild account programmatically: hold a conversation with an agent, read your agents and skills, create workspaces, publish new agent versions, and read session activity.

The mechanics are deliberately boring, which is what you want from infrastructure. You create an API key in your account settings, where you get a single credential string: the key ID, a colon, then a secret that starts with glda\_, shown exactly once, so save it somewhere safe. Requests go to https://api.guild.ai/v1 with that string sent as a Bearer token. Access is governed by scopes, which are (group, access) pairs where write implies read, and a key can only ever touch entities your account can already see. No new surface area to reason about, just your existing permissions expressed as credentials.

```
curl https://api.guild.ai/v1/agents \
  -H "Authorization: Bearer $GUILD_API_KEY"
```

That's the whole story. Here's why we're excited about it.

## Wiring Guild into the systems you already run

Platform teams don't want another console to babysit. They want Guild to behave like every other service in their stack. The API lets you provision workspaces, agents, and skills from code, so Guild becomes part of your infrastructure-as-code story instead of a manual step off to the side. A deployment pipeline can call the API as a post-install step to stand up the workspace an app expects. A provisioning script can create agents to match a new tenant. The point is that Guild now fits the automation you've already built, rather than asking you to build something new around it.

![](https://images.prismic.io/guild-ai/T8gmolTCMGtyPhmf_guild-api-wiring.png?auto=format,compress)

## Agents, skills, and workspaces in your CI pipeline

Because the API can create workspaces, publish agent versions, and cut new skill versions, your agents can live in version control like everything else. Push a change to an agent definition and let CI publish it. Run tests against a fresh workspace. Promote a validated agent version on merge to main.

```
- name: Publish version
  run: |
    curl -X POST https://api.guild.ai/v1/versions/$VERSION_ID/publish \
      -H "Authorization: Bearer $GUILD_API_KEY"
```

Agents stop being things you configure once and forget. They become artifacts with a real lifecycle, reviewed and shipped the same way you ship code.

## Agents that can work on themselves

An agentic API wouldn't be complete if agents couldn't use it. With the Guild API, you can do exactly that.

This opens the door for agents that re-attach a dropped credential for a helper they installed, that spin up a helper agent for a task that needs one, or that publish a corrected version of a skill after a run goes sideways. Self-healing workflows, in other words, where the system that spots the problem is also the system that fixes it. We'll leave the more ambitious version of that sentence to the sci-fi writers.

![](https://images.prismic.io/guild-ai/des7ntJrVvCXEqik_guild-api-work-on-themselves.png?auto=format,compress)

## A note on API triggers

If you've used Guild before, you may already know API triggers. The public API is a different breed of cat. An API trigger is a single-purpose credential that runs one agent, in one workspace, on demand when an authenticated request hits its session endpoint. Each trigger key is scoped to that one trigger, and it's the right tool when you just want to fire an agent from a webhook. The public API is a broader surface: account-scoped keys that read and write across your agents, skills, workspaces, and sessions. Triggers invoke. The API operates.

The full reference lives at [docs.guild.ai](https://docs.guild.ai/api-reference/introduction), including the OpenAPI spec if you'd rather generate a client. You can get started today at [app.guild.ai](https://app.guild.ai). Now, let's go build something.

## Build with the Guild API

Account-scoped keys, one base URL, your existing permissions expressed as credentials. Create a key in your account settings and make your first call today.

[Get your API key](https://app.guild.ai)