Switching from Requesty

Requesty alternative.
Requesty's routing, plus everything else a gateway should ship.

Requesty routes text LLM requests. AIgateway adds image, video, voice, audio, music, and embedding routing — plus primitives (evals, replay, sub-accounts, cost tags) single-purpose routers don't ship.

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 — Requesty
from openai import OpenAI

client = OpenAI(
    base_url="https://router.requesty.ai/v1",
    api_key="rq-...",
)

r = client.chat.completions.create(
    model="openai/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 Requesty doesn't.

WINS
  • Not just text — every modality under one schema.
  • Evals + replay + shadow A/B — not just cost-aware routing.
  • Sub-account API with per-user spend caps.
  • BYOK on every provider — Requesty is managed-only on most.
  • Flat 5% top-up fee; no per-request platform surcharge.
HONEST
What Requesty does better, per their public docs.
  • Requesty's cost-lookup UI is slick; we match on dashboard v2.
Credit match

Send your last Requesty invoice.
We match it.

Forward last month's Requesty 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 OpenRouter →Switch from Portkey →Switch from Helicone →Switch from LiteLLM →Switch from Together AI →Switch from Fireworks AI →Switch from Braintrust →