Skip to main content

​
Migrating from Helicone AI Gateway

This guide helps migrate from Helicone’s gateway to Phaseo.

​
Overview

Both provide AI API proxying with observability. Migration involves:
  • Changing base URL
  • Updating authentication
  • Adjusting configuration

​
Prerequisites

  • Phaseo account
  • Helicone setup

​
Migration Steps

​
1. Update Base URL

Replace Helicone’s proxy URL. 
# Before (Helicone proxy)
curl https://oai.helicone.ai/v1/chat/completions \
  -H "Authorization: Bearer sk-your-openai-key" \
  -H "Helicone-Auth: Bearer your-helicone-key" \
  -H "Content-Type: application/json" \
  -d '{
    "model": "gpt-4",
    "messages": [{"role": "user", "content": "Hello!"}]
  }'

# After (Phaseo)

curl https://api.phaseo.ai/v1/chat/completions \
 -H "Authorization: Bearer your-phaseo-key" \
 -H "Content-Type: application/json" \
 -d '{
"model": "gpt-4",
"messages": [{"role": "user", "content": "Hello!"}]
}'


import openai

client = openai.OpenAI(
    api_key="your-phaseo-key",
    base_url="https://api.phaseo.ai/v1"
)

response = client.chat.completions.create(
    model="gpt-4",
    messages=[{"role": "user", "content": "Hello!"}]
)

import OpenAI from "openai";

const client = new OpenAI({
	apiKey: "your-phaseo-key",
	baseURL: "https://api.phaseo.ai/v1",
});

const response = await client.chat.completions.create({
	model: "gpt-4",
	messages: [{ role: "user", content: "Hello!" }],
});

​
2. Authentication

Use Bearer token. Remove Helicone-specific headers.

​
3. Observability

Phaseo provides analytics. Migrate monitoring accordingly.

​
4. Test

Ensure requests work.

​
Common Issues

  • Headers: Remove Helicone-specific headers.
  • Logging: Different observability features.

​
Next Steps

  • Set up Phaseo analytics.
Last modified on July 9, 2026