Switching from Helicone

Helicone alternative.
Observability plus the routing Helicone doesn't do.

Helicone is an observability proxy — great at logging, not a routing or aggregation layer. AIgateway bundles observability with real routing, caching, and a 100+ model multi-modal catalog.

Get your key →See pricingClaim credit match
Migration

One-line diff.

Change the base URL and the key. Every other line of your integration stays the same.

Before — Helicone (proxy)
from openai import OpenAI

client = OpenAI(
    base_url="https://oai.helicone.ai/v1",
    api_key="sk-openai-...",
    default_headers={
        "Helicone-Auth": "Bearer sk-helicone-...",
    },
)

r = client.chat.completions.create(
    model="gpt-5.4",
    messages=[{"role": "user", "content": "Hello"}],
)
After — AIgateway
from openai import OpenAI

client = OpenAI(
    base_url="https://api.aigateway.sh/v1",
    api_key="sk-aig-...",
)

r = client.chat.completions.create(
    model="openai/gpt-5.4",
    messages=[{"role": "user", "content": "Hello"}],
)
Why switch

What AIgateway ships that Helicone doesn't.

WINS
  • Not a proxy — a real aggregator with 100+ models under one schema.
  • Eval-driven routing and replay, not just logs.
  • Caching at the edge (exact + semantic), metered at 10% of uncached cost.
  • Sub-account API for scoped keys per end user.
  • First-class video, image, audio, voice endpoints — Helicone is text-only observability.
HONEST
What Helicone does better, per their public docs.
  • Helicone's prompt-versioning UI is more mature; we match on Enterprise.
Credit match

Send your last Helicone invoice.
We match it.

Forward last month's Helicone invoice to switch@aigateway.sh and we apply matching AIgateway credit (up to $1,000) within 24 hours. Same base URL change. No migration tax.

Other migrations

Switching from something else?

Switch from OpenRouterSwitch from PortkeySwitch from LiteLLMSwitch from Together AISwitch from Fireworks AISwitch from RequestySwitch from Braintrust