Skip to content

chore: update vercel ai gateway guide #1501

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
smakosh merged 1 commit into from
Jan 25, 2026
Merged

chore: update vercel ai gateway guide #1501

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
23 changes: 0 additions & 23 deletions apps/ui/src/content/migrations/vercel-ai-gateway.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -7,8 +7,6 @@ date: 2026-01-20
fromProvider: Vercel AI Gateway
---

Using Vercel AI SDK with multiple providers means managing separate API keys and imports for each one. LLM Gateway gives you one provider that works with all models—plus response caching, per-request analytics, and automatic failover that Vercel's native providers don't offer.

## Quick Migration

Swap your provider imports—your AI SDK code stays the same:
Expand All @@ -30,18 +28,6 @@ const { text } = await generateText({
});
```

## Why Teams Switch to LLM Gateway

| Feature | Vercel AI Gateway | LLM Gateway |
| -------------------- | --------------------- | -------------------------- |
| AI SDK integration | Native (per-provider) | **One provider for all** |
| Response caching | No | **Yes, automatic** |
| Cost analytics | Limited | **Per-request detail** |
| API key management | Separate env var each | **One key, all providers** |
| Smart routing | No | **Auto failover** |
| Self-hosting | No | **Yes (AGPLv3)** |
| Anthropic-compatible | No | **Yes (/v1/messages)** |

The key difference: one provider, one API key, all models—with caching and analytics built in.

## Migration Steps
Expand Down Expand Up @@ -234,15 +220,6 @@ const { text, toolResults } = await generateText({
});
```

## What Changes After Migration

- **One import, all models** — No more separate `@ai-sdk/openai`, `@ai-sdk/anthropic` packages
- **One API key** — Stop managing OPENAI_API_KEY, ANTHROPIC_API_KEY separately
- **Response caching** — Identical requests hit cache automatically, cutting costs
- **Per-request analytics** — See what each `generateText()` call costs in your dashboard
- **Automatic failover** — If OpenAI goes down, we route to a backup provider
- **Self-hosting option** — Run on your own infrastructure if you need full control

## Self-Hosting LLM Gateway

If you prefer self-hosting, LLM Gateway is available under AGPLv3:
Expand Down