> ## 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 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.

# Developers

> Everything you need to call Guild from code: create an API key, read the API reference and OpenAPI spec, and build agents with the CLI and SDK.

Guild's public API, CLI, and Agent SDK let you run, build, and manage agents from your own code. Try them on a free trial account at [app.guild.ai](https://app.guild.ai); no credit card required. See [Pricing](/pricing) for plans.

## Call the API

<Steps>
  <Step title="Create an API key">
    In [app.guild.ai](https://app.guild.ai), open **Settings** for the account the key should act as and create a key with the scopes it needs. Or run `guild api-key create`. See [Create a key](/api-reference/introduction#create-a-key).
  </Step>

  <Step title="Make a request">
    Send the key's `<api_key_id>:<api_key_secret>` string as HTTP Basic credentials or a Bearer token.

    ```bash theme={null}
    curl -u "<api_key_id>:<api_key_secret>" https://api.guild.ai/v1/agents
    ```
  </Step>

  <Step title="Hold a conversation">
    Start a session with an agent, read its replies, and send follow-ups. See [Conversations](/api-reference/conversations).
  </Step>
</Steps>

The OpenAPI spec is unauthenticated: [`openapi.yaml`](https://docs.guild.ai/openapi.yaml) or [`openapi.json`](https://docs.guild.ai/openapi.json). Import it into an API client or code generator.

## Resources

<CardGroup cols={2}>
  <Card title="API reference" icon="book" href="/api-reference/introduction">
    Base URL, authentication, scopes, errors, and every endpoint.
  </Card>

  <Card title="Quickstart" icon="rocket" href="/quickstart">
    Run your first agent, then build your own with the CLI.
  </Card>

  <Card title="Guild CLI" icon="terminal" href="/cli/getting-started">
    Install the CLI, scaffold an agent, and test it locally before publishing.
  </Card>

  <Card title="Agent SDK" icon="code" href="/guide/sdk-introduction">
    Build agents with tools, typed inputs, and platform services.
  </Card>

  <Card title="API triggers" icon="key" href="/platform/api-triggers">
    Run one agent on demand with a key scoped to a single trigger.
  </Card>

  <Card title="MCP server" icon="plug" href="/cli/mcp-server">
    Call Guild operations as MCP tools from Claude Code, Cursor, or any MCP client.
  </Card>
</CardGroup>

## For AI agents

* [`llms.txt`](https://docs.guild.ai/llms.txt) indexes every page; add `.md` to any page URL for its Markdown.
* Search these docs from an MCP client at `https://docs.guild.ai/mcp`.
* In a browser that supports [WebMCP](https://github.com/webmachinelearning/webmcp), every page registers tools that search and read these docs and look up integrations and their tools.