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

# Contributing to Phaseo

> Choose the right workflow for a catalog report, documentation edit, or code contribution.

For catalog corrections and additions, open an issue with the affected record and supporting sources. For code or documentation changes, submit a pull request to the [Phaseo repository](https://github.com/phaseoteam/Phaseo).

## Choose your contribution

| Change | Start here |
| - | - |
| Model metadata, capabilities, availability, or pricing | [Report a model update](https://phaseo.app/docs/v1/contributing/editing-a-model.md) |
| Company or research organisation details | [Report an organisation update](https://phaseo.app/docs/v1/contributing/editing-an-organisation.md) |
| Benchmark results | [Submit scores](https://phaseo.app/docs/v1/research/submitting-scores.md) |
| Other catalog corrections | [Report incorrect information](https://github.com/phaseoteam/Phaseo/issues/new?template=incorrect-info.yml) |
| Missing providers or other catalog data | [Request new data](https://github.com/phaseoteam/Phaseo/issues/new?template=data-request.yml) |
| Documentation or code | [Contribution workflow](https://phaseo.app/docs/v1/contributing/how-to-contribute.md) and [repository structure](https://phaseo.app/docs/v1/contributing/repo-structure.md) |

## How catalog reports are published

Maintainers review the evidence in the issue and apply approved changes through the admin-only [internal editor](https://phaseo.app/internal/data). Provider price updates require explicit review before publication.

The database is the catalog source of truth. Daily public JSON snapshots remain available, but neither snapshot edits nor archived JSON pull requests update the live catalog. The legacy JSON importer is retired.

## Before submitting

* Include the affected page or record ID and describe the proposed correction.
* Cite official sources and distinguish reported benchmark results from independent measurements.
* Keep each report or pull request focused.
* Never include credentials or private customer data.
* Follow the [Code of Conduct](https://phaseo.app/docs/v1/community/code-of-conduct.md).

Discuss larger schema or feature changes with maintainers before implementing them. Ask for help in [Discord](https://discord.gg/aQyywCvgZ5) if you are unsure where a change belongs.


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