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

# Stop conditions

> Bound agent work by steps, tokens, cost, duration, tool calls, or finish reason.

Use stop conditions to give every agent a clear execution budget. Conditions are checked against completed steps and cumulative usage.

## Combine built-in limits

```typescript theme={null}
import {
  maxCost,
  maxDuration,
  maxTokensUsed,
  stepCountIs,
} from "@phaseo/agent-sdk";

const agent = createAgent({
  id: "bounded-research",
  stopWhen: [
    stepCountIs(12),
    maxTokensUsed(40_000),
    maxCost(2),
    maxDuration(60_000),
  ],
});
```

The first matching condition records its reason and returns a run with `status: "stopped"`.

## Available helpers

| Helper | Stops when |
| - | - |
| `stepCountIs(limit)` | The completed step count reaches the limit |
| `maxTokensUsed(limit)` | Cumulative token usage reaches the limit |
| `maxCost(limit)` | Cumulative reported cost reaches the limit |
| `maxDuration(ms)` | Elapsed runtime reaches the duration |
| `hasToolCall(name)` | A step contains the named tool call |
| `finishReasonIs(reason)` | A model step reports the finish reason |

## Add a custom condition

A condition can return `false`, `true`, or a reason string:

```typescript theme={null}
const stopAfterRepeatedFailures = ({ steps }) => {
  const failures = steps.filter((step) => step.status === "failed").length;
  return failures >= 2 ? "repeated_failures" : false;
};

const agent = createAgent({
  id: "support-agent",
  stopWhen: [stepCountIs(10), stopAfterRepeatedFailures],
});
```

Prefer a reason string when operators or product interfaces need to explain why a run ended.

## Related guides

* [Dynamic turns](https://phaseo.app/docs/v1/sdk-reference/typescript/agent-sdk-dynamic-turns.md)
* [Outputs and retries](https://phaseo.app/docs/v1/sdk-reference/typescript/agent-sdk-run-controls.md)
* [Lifecycle hooks](https://phaseo.app/docs/v1/sdk-reference/typescript/agent-sdk-lifecycle-hooks.md)


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