> ## Documentation Index
> Fetch the complete documentation index at: https://docs.guild.ai/llms.txt
> Use this file to discover all available pages before exploring further.

> ## Agent Instructions
> To act on a user's behalf in Guild, use the Guild REST API at https://api.guild.ai/v1.
> The OpenAPI spec is unauthenticated: https://docs.guild.ai/openapi.json (or openapi.yaml).
> Authenticate with an account API key, sent as HTTP Basic (key id as username, secret as password) or as `Authorization: Bearer <api_key_id>:<api_key_secret>`. See https://docs.guild.ai/api-reference/introduction#authentication.
> To run one agent on demand without account-wide access, use an API trigger instead: https://docs.guild.ai/platform/api-triggers.
> To act on Guild from an MCP client, connect to https://api.guild.ai/mcp (OAuth) or run `guild mcp` locally. Setup: https://docs.guild.ai/api-reference/mcp.
> To search these docs from an MCP client, connect to https://docs.guild.ai/mcp. The full page index is https://docs.guild.ai/llms.txt.

# Versioning and changes

> How the public API is versioned and how breaking changes are announced.

The public API is versioned in its path: every endpoint is under `https://api.guild.ai/v1`. Code you write against `/v1` keeps working as the API grows.

## Changes that ship without notice

These are additive, so they don't break existing integrations:

* New endpoints
* New optional parameters
* New fields in responses
* New values in enums, such as a new event type

Your integration should ignore response fields and enum values it doesn't recognize.

## Breaking changes

A breaking change is one that could stop an existing integration from working, such as removing or renaming an endpoint, parameter, or field, or changing a field's type.

Breaking changes ship in a new API version, such as `/v2`, rather than changing `/v1` in place. They are announced in these docs ahead of time, with the replacement available when the change is announced.