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

# Anthropic Claude Opus 4.7

> What to know when adopting Claude Opus 4.7, including adaptive thinking, sampling controls, and token usage.

# Anthropic Claude Opus 4.7

Use this guide to adopt `anthropic/claude-opus-4.7` safely in production.

Claude Opus 4.7 introduces request-shape changes that can hard-fail old 4.6 patterns if left unchanged.

## What's new

* New effort level: `xhigh` (Messages API)
* Extended thinking budgets were removed for Opus 4.7 (`thinking: { type: "enabled", budget_tokens: ... }` now fails)
* Sampling params are no longer supported on this model when set to non-default values (`temperature`, `top_p`, `top_k`)
* Thinking content is omitted by default unless you explicitly opt in
* Updated tokenizer behavior can increase token usage vs Opus 4.6

## Phaseo gateway compatibility behavior

To reduce migration breakage, Phaseo accepts legacy Opus 4.6 fields for Opus 4.7 and normalizes them before sending upstream:

* `temperature`, `top_p`, and `top_k` are accepted but stripped
* legacy thinking budgets are not forwarded
* Opus 4.7 thinking is always sent as `thinking: { "type": "adaptive", "display": "summarized" }`
* `reasoning.effort` is still honored and mapped to `output_config.effort` (`xhigh` supported)

## Migration quickstart

### 1. Update model ID

Set the model ID to `anthropic/claude-opus-4.7`.

### 2. Move to adaptive thinking with summarized display

For Opus 4.7, use:

* `thinking: { "type": "adaptive", "display": "summarized" }`

Avoid legacy extended-thinking budgets on this model.

### 3. Remove sampling controls

Do not send:

* `temperature`
* `top_p`
* `top_k`

Prefer prompt and instruction tuning instead.

### 4. Rebaseline effort controls

If you use reasoning controls, retest with:

* `output_config.effort = "high"` as baseline
* `output_config.effort = "xhigh"` for hardest coding/agentic paths

If you call Phaseo through OpenAI-style payloads, `reasoning.effort` maps to this same `output_config.effort` value for Opus 4.7.

### 5. Recheck token ceilings

Because tokenization changed, audit:

* `max_tokens` / `max_output_tokens`
* timeout budgets
* cost controls and alerts

## What to test

* strict schema output pass rate with your production prompts
* long-running tool workflows (tool call count, completion rate, latency)
* response quality deltas at `high` vs `xhigh`
* token-cost deltas on your highest-volume prompt classes

## Safe rollout

1. Deploy request-shape changes before shifting traffic.
2. Shadow Opus 4.7 on your production eval suite.
3. Canary with rollback to Opus 4.6.
4. Promote once quality, latency, and cost deltas are within target.

## Sources

* [What's new in Claude Opus 4.7](https://platform.claude.com/docs/en/about-claude/models/whats-new-claude-4-7)
* [Anthropic migration guide](https://platform.claude.com/docs/en/about-claude/models/migration-guide)
* [Claude Opus 4.7 System Card (PDF)](https://cdn.sanity.io/files/4zrzovbb/website/037f06850df7fbe871e206dad004c3db5fd50340.pdf)


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