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

# Migration Feature Checklist

> Check the Phaseo capabilities that commonly affect a gateway migration.

# Migration Feature Checklist

Use this checklist to identify which parts of an existing gateway integration can move unchanged and which need explicit validation. It was last reviewed on August 23, 2026.

## Core request compatibility

| Capability | Phaseo support | Migration action |
| - | - | - |
| OpenAI-compatible authentication | Supported | Change the base URL and API key, then run one authenticated request. |
| Chat Completions | Supported | Test normal, streaming, tool-calling, and structured-output requests. |
| Responses | Supported | Test input formats, streaming events, tools, and response parsing. |
| Anthropic Messages | Supported | Verify Anthropic-specific headers, system prompts, and streaming events. |
| Model identifiers | Phaseo catalog IDs | Validate every production ID with `GET /v1/models`; do not assume aliases match. |
| Embeddings, image, and audio endpoints | Supported by model and provider | Verify the model supports the required operation before cutover. |

## Routing and policy controls

| Capability | Phaseo support | Migration action |
| - | - | - |
| Provider ordering | `provider.order` | Recreate only the ordering rules the workload still needs. |
| Provider allow and ignore lists | `provider.only` and `provider.ignore` | Validate provider IDs and confirm at least one route remains available. |
| Price, latency, or throughput sorting | `provider.sort` | Inspect the selected provider in Gateway usage after testing. |
| Zero data retention | `provider.require_zero_data_retention` | Confirm the model has a matching provider before enforcing the requirement. |
| Regional execution and data residency | Request fields and workspace privacy defaults | Test both successful routing and the no-matching-provider failure path. |
| Reusable prompts and defaults | Presets | Move shared configuration into a preset instead of duplicating it across callers. |

## Operations and rollout

| Capability | Phaseo support | Migration action |
| - | - | - |
| Request attribution | App ID, name, URL, and categories | Keep attribution headers during migration and verify app grouping in the dashboard. |
| Request and provider details | Gateway usage and generation records | Compare provider, latency, token usage, and pricing for representative prompts. |
| Batch and async jobs | Batch, file, video, webhook, and websocket APIs | Validate status transitions, terminal billing, cancellation, and result retrieval. |
| Replay support | Generation records expose replay metadata when available | Confirm the original endpoint and payload can be recovered for failed requests. |
| Gradual rollout | Client or infrastructure traffic splitting | Keep rollback as a base URL and credential change until the cutover is stable. |

## Features that require workload-specific validation

Do not treat API compatibility as proof that these behaviors are identical:

* automatic provider selection and fallback order
* prompt-cache affinity and cache pricing
* provider-specific request fields
* response-only metadata
* rate limits and retry timing
* data retention, residency, and training policies
* exact model availability and price

Run production-like prompts and failure cases before moving meaningful traffic.

## Related guides

* [Migration Guides](https://phaseo.app/docs/v1/migration-guides/index.md)
* [Migration Readiness Review](https://phaseo.app/docs/v1/migration-guides/gateway-parity-review.md)
* [Routing and Fallbacks](https://phaseo.app/docs/v1/guides/routing-and-fallbacks.md)
* [Presets](https://phaseo.app/docs/v1/guides/presets.md)
* [App Attribution](https://phaseo.app/docs/v1/guides/app-attribution.md)


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