What changes
1
Create a Phaseo API key
Create a key with
phaseo keys create in the Phaseo CLI or in Gateway Keys and make it available to your application as PHASEO_API_KEY.2
Update the Anthropic client
Point the SDK at the Phaseo root host,
https://api.phaseo.app, and pass your Phaseo key as authToken (auth_token in Python). The SDK adds /v1/messages itself and sends the key as Authorization: Bearer. Remove ANTHROPIC_API_KEY from environments that now call Phaseo, so older SDK versions don’t also send your Anthropic key.3
Verify Anthropic-specific behavior
Test system prompts, streaming, tool use, thinking or reasoning options, and structured output behavior with the exact models your application uses. Remove obsolete beta headers or request fields rather than carrying them into the new path blindly.
4
Roll out gradually
Compare a representative prompt set across both configurations. Check output shape, latency, token usage, errors, and cost before shifting production traffic.
Migration checklist
- The Phaseo key is configured in every deployment environment.
- The Anthropic client points to
https://api.phaseo.app. - Every production model ID is verified against
GET /v1/models. - Streaming and tool-use flows pass in staging.
- Anthropic-specific beta headers and parameters have been reviewed.
- Rollback remains a configuration-only key and endpoint change.