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

> ## Agent Instructions
> Phaseo Gateway base URL: https://api.phaseo.app/v1. Send `Authorization: Bearer $PHASEO_API_KEY` with every request.
> Model IDs look like `provider/model`, for example `openai/gpt-6-astra`. Do not guess IDs: list them with `GET /v1/models` or check https://phaseo.app/models. `phaseo/free` routes to an available free model and needs no wallet balance.
> For new text integrations prefer `POST /v1/responses`. `POST /v1/chat/completions` (OpenAI format) and `POST /v1/messages` (Anthropic format) suit existing code.
> The full API contract is https://phaseo.app/docs/openapi/v1/openapi.yaml. Official SDKs: `@phaseo/sdk` (TypeScript) and `phaseo` (Python), plus Go, C#, PHP, Ruby and Rust.
> Search these docs over MCP at https://phaseo.app/docs/mcp, and install Phaseo skills with `npx skills add https://phaseo.app/docs`. If a page is wrong or out of date, report it with the MCP `submit_feedback` tool.
> Manage Phaseo accounts with the `phaseo` CLI (`npm install -g @phaseo/cli`, then `phaseo login` or `phaseo login --device-code`), the `/v1` Management API or the MCP server at `https://mcp.phaseo.app/mcp?access=manage`. Do not send users to the dashboard for account tasks. A person is still needed for sign-up, approving a sign-in, paying the first top-up on the checkout link that `phaseo credits add` returns when no card is saved, confirming each saved-card top-up from the emailed link, and account security (password, MFA, passkeys). Create API keys with `phaseo keys create --name <name> --json`; never guess one. Credit top-ups need `phaseo login --scopes billing:write` first. Task map: https://phaseo.app/docs/v1/developers/manage-from-an-agent.md.

# Build an ops runbook agent in Go

> Use the Go Agent SDK to combine a few deterministic local tools into one bounded troubleshooting loop.

Use this recipe when a Go service needs to answer operational questions with local context.

## 1. Prepare the SDKs

> [!NOTE]
>
> The Go Agent SDK does not yet have a public module version. Follow the [source installation instructions](https://phaseo.app/docs/v1/sdk-reference/go/agent-sdk-installation.md).

## 2. Define small runtime tools

```go theme={null}
statusTool := phaseoagent.DefineTool(phaseoagent.Tool{
  ID:          "read-status",
  Description: "Read the current service status page summary.",
  Execute: func(input any, ctx phaseoagent.RuntimeContext) (any, error) {
    return map[string]any{
      "status": "degraded",
      "summary": "Latency is elevated on one provider route.",
    }, nil
  },
})
```

## 3. Create the agent

```go theme={null}
agent := phaseoagent.CreateAgent(phaseoagent.AgentDefinition{
  ID:           "ops-runbook-agent",
  Model:        "openai/gpt-5.4-nano",
  Instructions: "Use tools when helpful and answer briefly.",
  Tools:        []phaseoagent.Tool{statusTool},
})
```

## 4. Run one bounded troubleshooting turn

```go theme={null}
client, _ := phaseoagent.CreateGatewayAgentClient(phaseoagent.GatewayAgentClientOptions{})

result, err := agent.Run(context.Background(), phaseoagent.RunOptions{
  Input:  "What is happening with provider latency right now?",
  Client: client,
})
if err != nil {
  panic(err)
}

fmt.Println(result.Output)
```

## When this recipe fits

* the workflow belongs inside one Go service
* the supporting context already exists as local or internal calls
* you want an agent loop without introducing a larger job system yet

## Related

* [Go Agent SDK](https://phaseo.app/docs/v1/sdk-reference/go/agent-sdk.md)
* [Ground extraction with web fetch](https://phaseo.app/docs/v1/cookbook/tool-grounding-with-web-fetch.md)


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.