> ## 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 --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. # Provider and Phaseo Statuses > How upstream provider availability, Phaseo integration readiness, and routing health differ. A provider/model offer has separate upstream and Phaseo statuses. This matters when a provider has released a model but Phaseo has not yet implemented or enabled the corresponding endpoint. You will see these fields on model pages, provider pricing cards, and related availability UI. ## Provider availability Provider availability describes the upstream offer. | Status | Meaning | | - | - | | `Available` | The provider currently accepts requests for the offer. | | `Preview` | The provider exposes the offer as a preview. | | `Limited Access` | The offer exists, but access is restricted by account, region, allowlist, or capacity. | | `Coming Soon` | The provider has announced or listed the offer, but it cannot be used yet. | | `Deprecated` | The offer remains available while the provider recommends migration. | | `Removed` | The provider no longer exposes the offer. | | `Unknown` | Phaseo has not verified the upstream availability. | Provider availability never means that Phaseo can route the request. ## Phaseo integration status Phaseo status describes our implementation and rollout. | Status | Meaning | Phaseo routing | | - | - | - | | `Unsupported` | Phaseo has no compatible integration for the offer. | Not routable. | | `Planned` | Integration work is accepted but has not started. | Not routable. | | `Implementing` | Integration work is in progress. | Not routable. | | `Testing` | Implemented and under contract, staging, or canary testing. | Not publicly routable. | | `Enabled` | Supported and enabled for production use. | Eligible, subject to routing switches and health. | | `Disabled` | Phaseo has intentionally switched the integration off. | Not routable. | | `Blocked` | An external or unresolved dependency prevents rollout. | Not routable. | Only `Enabled` integrations can have public routing enabled. ## Internal access Access scope is separate from Phaseo integration status: | Scope | Meaning | | - | - | | `Public` | Ordinary customer requests may use the route when every routing gate passes. | | `Internal` | Only authenticated Phaseo testing traffic may use the route. | An internal route requires the high-entropy internal token and an explicit testing-mode request. A customer cannot enable it with the testing header alone. Ordinary requests do not perform an internal-route database lookup; they use the existing default context cache. Internal testing uses a separate cache segment and only considers explicitly internal routes whose upstream offer is usable and whose Phaseo status is `Testing` or `Enabled`. ## Routing health Routing health is a third, operational signal. It answers how an enabled route should be selected right now. | Status | Meaning | Routing behaviour | | - | - | - | | `Active` | The route is healthy enough to select normally. | Routable now. | | `Deranked L1` | Mildly deprioritised by recent health. | Routable now. | | `Deranked L2` | Clearly deprioritised by recent health. | Routable now, behind healthier routes. | | `Deranked L3` | Heavily deprioritised by recent health. | Routable now, strongly deprioritised. | | `Disabled` | The routing switch is off. | Not routed. | Deranking does not change the provider's availability or Phaseo's integration lifecycle. Live health observations also do not rewrite either lifecycle field. ## Examples A newly released provider offer can be: * provider availability: `Available` * Phaseo status: `Implementing` * routing health: not applicable because routing is off A mature but temporarily degraded route can be: * provider availability: `Available` * Phaseo status: `Enabled` * routing health: `Deranked L2` A provider announcement can be: * provider availability: `Coming Soon` * Phaseo status: `Planned` * routing health: not applicable ## Compatibility Existing API fields such as `availability_status`, `routing_status`, `is_active_gateway`, and `routable` remain available during the additive rollout. New integrations should use the explicit provider and Phaseo fields. ## Related pages * [Routing and Fallbacks](https://phaseo.app/docs/v1/guides/routing-and-fallbacks.md) * [Service Tiers](https://phaseo.app/docs/v1/guides/service-tiers.md) * [Models API reference](https://phaseo.app/docs/v1/api-reference/endpoint/models.md) This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.