Skip to main content

​
Migrating from Helicone AI Gateway

This guide helps migrate from Helicone’s gateway to AI Stats.

​
Overview

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

​
Prerequisites

  • AI Stats 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 (AI Stats)

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

​
2. Authentication

Use Bearer token. Remove Helicone-specific headers.

​
3. Observability

AI Stats 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 AI Stats analytics.
Last modified on February 11, 2026