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

# Contribute Code or Documentation

> Set up Phaseo locally, validate a focused change, and open a pull request.

Use this workflow for code and documentation changes. For model, provider, pricing, organisation, or benchmark records, [submit a catalog issue](https://phaseo.app/docs/v1/contributing/overview.md) instead; no local setup is needed.

## Set up your fork

Install Git, Node.js 22.12 or newer, and pnpm. Fork the [Phaseo repository](https://github.com/phaseoteam/Phaseo), then clone your fork and create a new branch:

```bash theme={null}
git clone https://github.com/yourusername/Phaseo.git
cd Phaseo
git switch -c docs/improve-quickstart
pnpm install
```

## Make and preview the change

See [Repository structure](https://phaseo.app/docs/v1/contributing/repo-structure.md) for the relevant application or package. For Markdown-only edits, you can also use GitHub's file editor and open a pull request there.

```bash theme={null}
# Web app at http://localhost:3100
pnpm --filter @phaseo/web dev

# Documentation at http://localhost:3101
pnpm --filter @phaseo/docs dev
```

Follow the relevant `AGENTS.md` instructions. Keep secrets in local environment files and out of commits. Local app previews may require configured backend services and normal sign-in.

## Validate your changes

Run the checks relevant to the files you changed. For documentation:

```bash theme={null}
pnpm docs:links
pnpm docs:build
```

For web changes:

```bash theme={null}
pnpm --filter @phaseo/web lint
pnpm --filter @phaseo/web typecheck
pnpm --filter @phaseo/web test
```

Run a production build for rendering or routing changes. API, SDK, and schema changes need their corresponding tests and generation steps. See the root [contribution guide](https://github.com/phaseoteam/Phaseo/blob/main/CONTRIBUTING.md).

## Open a pull request

Stage only the files you changed, use a descriptive commit message, and push your branch:

```bash theme={null}
git add apps/docs/v1/quickstart.mdx
git commit -m "docs: clarify the quickstart"
git push -u origin docs/improve-quickstart
```

Open a pull request from your fork. Explain the problem, what changed, and which checks passed. Link related issues and include screenshots for visible UI changes. Address review feedback before merge; changes become live after the relevant deployment completes.

Follow the [Code of Conduct](https://phaseo.app/docs/v1/community/code-of-conduct.md). For large or uncertain changes, discuss the proposal before writing code.


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