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

# Errors and troubleshooting

> Handle model, tool, validation, cancellation, and continuation failures in Go agents.

Agent failures normally come from the model request, a local tool, schema validation, cancellation, or an incomplete human decision. Keep these paths visible in logs and return safe errors to callers.

## Recover from tool errors

Set `OnError: "return-to-model"` on a tool when the model can reasonably recover from the failure. The SDK converts the error into a tool result and allows the next turn to choose another action. Leave the default fail-run behavior for unsafe or unrecoverable failures.

## Respect cancellation

Pass the request context to `Run`, `Continue`, or `Stream`. Cancelling it stops model streaming and prevents new tool work from starting.

```go theme={null}
ctx, cancel := context.WithTimeout(context.Background(), 30*time.Second)
defer cancel()

result, err := agent.Run(ctx, options)
if errors.Is(err, context.DeadlineExceeded) {
  // Persist enough application state to retry or report the timeout.
}
```

## Diagnose continuation errors

When a run is waiting for a person, every pending call needs an approval, rejection, or externally supplied result keyed by its tool-call ID. Persist the entire returned run record; a human message alone is not a substitute for those decisions.

## Capture useful context

Record the run ID, step index, request ID, provider, model, finish reason, tool-call ID, and stop reason. Lifecycle hooks and DevTools expose these fields without requiring transport-level logging.


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