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

# Workspaces

> Organise API keys, settings, and administrative access without changing your Phaseo pricing plan.

Workspaces keep API keys, routing settings, presets, guardrails, and administrative access organised around a team, product, or environment.

Workspaces are included with Phaseo's standard pay-as-you-go service. You do not need a separate plan to create or use them.

## When to create a workspace

Use separate workspaces when you want to:

* isolate development, staging, and production credentials
* keep different products or customer projects separate
* give administrative integrations access to only the resources they need
* apply different routing, preset, or guardrail policies

For a small integration, the default workspace may be all you need.

## Manage workspaces

You can manage workspaces from the Phaseo dashboard or through the management API.

The workspace API uses [management API keys](https://phaseo.app/docs/v1/developers/management-api-keys.md). Standard Gateway API keys are for inference requests and cannot call workspace administration endpoints.

| Task | Endpoint |
| - | - |
| List workspaces | [`GET /workspaces`](../api-reference/endpoint/workspaces-list) |
| Create a workspace | [`POST /workspaces`](../api-reference/endpoint/workspaces-create) |
| Read a workspace | [`GET /workspaces/{id}`](../api-reference/endpoint/workspaces-get) |
| Update a workspace | [`PATCH /workspaces/{id}`](../api-reference/endpoint/workspaces-update) |
| Delete a workspace | [`DELETE /workspaces/{id}`](../api-reference/endpoint/workspaces-delete) |

> [!NOTE]
>
> Workspace management endpoints are currently marked Beta. Keep administrative automation easy to retry and review API responses before applying follow-up changes.

## Choose the right access

Create a management key with only the workspace capabilities your integration needs:

* `workspaces:read` to list and inspect workspaces
* `workspaces:write` to create or update workspaces
* `workspaces:delete` to remove workspaces

Phaseo also checks workspace membership and roles. A capability does not grant access to another workspace by itself.

Keep management keys in server-side secret storage. Do not expose them in browser code, desktop logs, source control, or chat.

## Deleting a workspace

The default workspace cannot be deleted. Before deleting another workspace, remove or move its active API keys so requests are not left pointing at a workspace that no longer exists.

## Billing

Workspaces do not create separate pricing tiers. Usage continues under the standard pay-as-you-go billing described in [Pricing & Billing](https://phaseo.app/docs/v1/pricing/tiers.md).

## Next steps

> [card] [Management API Keys](https://phaseo.app/docs/v1/developers/management-api-keys.md)
>
> Create a scoped server-side credential for workspace administration.

> [card] [Authentication](https://phaseo.app/docs/v1/developers/authentication.md)
>
> Use Gateway API keys for model and generation requests.


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