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

# App Attribution

> Group Gateway usage by application with stable IDs, names, URLs, and categories.

Use app attribution to separate usage from different products, environments, or customer-facing experiences. Attribution appears in app analytics and request audits without changing the inference response.

## Add attribution headers

Send a stable app ID on every request. Add a name, URL, and up to three categories when you want richer dashboard grouping.

```bash theme={null}
curl https://api.phaseo.app/v1/responses \
  -H "Authorization: Bearer $PHASEO_API_KEY" \
  -H "Content-Type: application/json" \
  -H "X-App-Id: acme-support" \
  -H "X-App-Name: Acme Support" \
  -H "HTTP-Referer: https://acme.example/support" \
  -H "X-App-Categories: chat,productivity" \
  -d '{
    "model": "openai/gpt-5-nano",
    "input": "Summarize this ticket."
  }'
```

Use the same `X-App-Id` for every request from the same application. Phaseo uses it as the stable identity when a URL is unavailable.

## Use the TypeScript SDK

```typescript theme={null}
import Phaseo from "@phaseo/sdk";

const phaseo = new Phaseo({
  apiKey: process.env.PHASEO_API_KEY,
  app: {
    id: "acme-support",
    name: "Acme Support",
    url: "https://acme.example/support",
    categories: ["chat", "productivity"],
  },
});

const response = await phaseo.generateResponse({
  model: "openai/gpt-5-nano",
  input: "Summarize this ticket.",
});
```

## Supported headers

| Header | Purpose |
| - | - |
| `X-App-Id` | Stable identifier chosen by your application. |
| `X-App-Name` | Human-readable name shown in app and usage views. |
| `HTTP-Referer` | Public page or deployment URL associated with the app. |
| `X-App-Categories` | Comma-separated list of up to three supported categories. |
| `X-Title` | Compatibility alias for a human-readable app name. |

`HTTP-Referer` is attribution metadata; it does not need to match the browser's automatic `Referer` header. Set it explicitly in server-side integrations when you want one canonical app URL.

## Categories

Choose up to three values:

* `chat`
* `developer-tools`
* `research`
* `productivity`
* `education`
* `commerce`
* `media`
* `finance`
* `other`

Values are case-insensitive. Phaseo ignores unknown values, removes duplicates, and keeps the first three valid categories. Categories received on later requests are merged with categories already saved for the app; they do not remove dashboard selections.

You can also edit categories in **Gateway → Settings → Apps**. Use the dashboard when classification is managed centrally rather than by application code.

## Attribution guidelines

* Keep IDs stable across deployments so usage remains grouped.
* Use separate IDs for applications that need separate cost or usage reporting.
* Do not put customer IDs, email addresses, or other personal data in attribution headers.
* Treat the URL as public metadata when the app may appear in shared or public app views.


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