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

# Workspace audit log

> Review security-sensitive workspace administration changes.

Workspace owners and admins can review key lifecycle changes in **Settings → Workspace → Activity**. Events are scoped to the active workspace and ordered from newest to oldest.

The first release records these operations:

* API key creation, rename, pause, resume, limit changes, rotation, and deletion
* management key creation, rename, pause, resume, access-template changes, limit changes, expiry changes, and deletion

Each event includes the actor, action, target, timestamp, and a small set of safe change metadata. Audit events are append-only. Phaseo does not store plaintext keys, credential hashes, authorization headers, full scope lists, or request bodies in this log.

Audit-log access is limited to workspace owners and admins. Ordinary members cannot read audit events, and the underlying table is not exposed to authenticated database clients.

For automation, call `GET /v1/audit-events` with a management key that has `activity:read`. Use the returned `next_cursor` to retrieve older events without timestamp gaps.

> [!NOTE]
>
> Request and generation logs answer what traffic ran. The workspace audit log answers who changed an administrative control and when.


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