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

# Report an Organisation Update

> Request corrections or additions to companies and research organisations in the catalog.

Report missing or outdated organisation details through a GitHub issue. Maintainers review the evidence and apply approved changes in the database editor.

## Report a correction

1. Copy the organisation's Phaseo page URL or ID.
2. [Report incorrect information](https://github.com/phaseoteam/Phaseo/issues/new?template=incorrect-info.yml) with the affected field and proposed value.
3. Link to an official website, announcement, or another verifiable source.

Common corrections include the name, description, website, location, and relationships to models or API providers.

## Request a missing organisation

[Open a data request](https://github.com/phaseoteam/Phaseo/issues/new?template=data-request.yml) with the organisation's name, official website, and relevant model or provider links.

## After submitting

Track review and publication in the issue. No JSON edit or pull request is needed for a catalog record change. Daily JSON files are exports; they are not imported into the live database.

Admins manage organisations through the [internal catalog editor](https://phaseo.app/internal/data), which requires admin access.


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