Skip to main content
Use this guide to keep your Anthropic SDK workflow while moving requests through Phaseo. Change the client configuration first, then verify model IDs and the Anthropic-specific behavior your application depends on.

What changes

1

Create a Phaseo API key

Create a key 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 base URL and use your Phaseo 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/v1.
  • 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.

Next steps

Last modified on July 26, 2026