> ## 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, timeout, and continuation failures in PHP agents.

Agent failures normally come from the model request, a local tool, schema validation, a timeout, or a missing human decision.

## Recover from tool errors

Set `onError: "return-to-model"` when the model can recover from a tool failure. The error becomes a structured tool result and the run can choose another action. Keep fail-run behavior for unsafe or unrecoverable operations.

## Understand PHP execution

PHP tool callbacks execute synchronously. Tool concurrency and interruption are therefore constrained by the PHP runtime and the underlying I/O client. Use explicit timeouts in network and process tools, and avoid claiming that a timed-out callback can always be forcibly stopped.

## Diagnose continuation errors

Every pending call needs an approval, rejection, or externally supplied output keyed by its tool-call ID. Persist the complete returned run state before showing an approval UI.

## Log actionable fields

Capture run ID, step index, request ID, provider, model, finish reason, tool-call ID, and stop reason. Use lifecycle hooks or DevTools instead of logging raw prompts and credentials.


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