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

# Feature maturity

> What the Alpha and Beta labels mean, who can use each feature, and the current stage of every feature that isn't generally available.

Some Phaseo features carry an **Alpha** or **Beta** label in the docs, the API reference and the dashboard. The label tells you how settled a feature is. A feature with no label is generally available.

## Stages

| Stage | What it means | What to do |
| - | - | - |
| Alpha | An early version. Its API, behavior or pricing may change a lot, and it may be removed. | Try it and tell us what you think. Don't build anything you can't change quickly on top of it. |
| Beta | Works for its main use. Some details may still change based on feedback, and changes are announced in the [changelog](https://phaseo.app/docs/v1/changelog.md). | Fine for pilots and real workloads you watch closely. Check the changelog when you upgrade. |
| Generally available | Fully supported and documented. No label is shown. | Use it in production. |
| Deprecated | Still works, but is no longer recommended and will be removed. A removal date is shown when one is set. | Don't start using it, and move off it before the removal date. |

Models and providers have their own lifecycle labels, which are separate from these stages. See [Model retirement](https://phaseo.app/docs/v1/guides/model-retirement.md) and [Provider statuses](https://phaseo.app/docs/v1/guides/provider-statuses.md).

## Who can use a feature

Stage and access are separate. A Beta feature can be open to everyone, and an Alpha feature can be limited to some workspaces.

* **Everyone**: any workspace can use it, subject to the usual roles. For example, some settings are for owners and admins only.
* **On request**: the feature is turned on per workspace. Until it's on, its settings page doesn't appear and its API returns an error. **Settings → Feature Preview** shows whether the Video and Batch APIs are on for your workspace. To ask for access to any of these features, [contact us](https://phaseo.app/contact).

## Features that aren't generally available

| Feature | Stage | Access |
| - | - | - |
| [Auto Routing](https://phaseo.app/docs/v1/guides/auto-routing.md) (`phaseo/auto`) | Alpha | On request |
| [Video API](https://phaseo.app/docs/v1/guides/async-video-and-batch.md) | Alpha | On request |
| [Preset Feedback](https://phaseo.app/docs/v1/guides/preset-feedback.md) | Alpha | Everyone |
| [Slack agent](https://phaseo.app/docs/v1/guides/slack-agent.md) | Alpha | On request |
| [Batch API](https://phaseo.app/docs/v1/guides/async-video-and-batch.md), with the Files API and webhook endpoints | Beta | On request |
| [Decisions API](https://phaseo.app/docs/v1/api-reference/endpoint/decisions.md) | Beta | Everyone |
| [Realtime voice](https://phaseo.app/docs/v1/guides/realtime-voice.md) | Beta | On request |
| [Server tools](https://phaseo.app/docs/v1/guides/server-tools.md) | Beta | Everyone |
| [Request classifiers](https://phaseo.app/docs/v1/guides/request-classifiers.md) | Beta | On request |
| [Trusted workloads](https://phaseo.app/docs/v1/developers/trusted-workloads.md) | Beta | On request |
| [Private models](https://phaseo.app/docs/v1/guides/private-models.md) | Beta | Everyone (owners and admins) |
| Enterprise: single sign-on, SCIM, directory and departments | Beta | On request, with the identity add-on |

Everything else, including the chat completions, responses and messages endpoints, presets, guardrails, budgets, BYOK, Broadcast and the management API, is generally available.

## How features change stage

* A feature moves from Alpha to Beta, or from Beta to generally available, when its main use works and its API is settled. We note the change in the [changelog](https://phaseo.app/docs/v1/changelog.md).
* Breaking changes to Alpha and Beta features are announced in the changelog.
* When a feature is deprecated, its docs page says so and gives the removal date when one is set.


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