Migrate Direct Provider SDKs to Merge Gateway

Migrate OpenAI, Anthropic, and Google SDK usage to Merge Gateway.

1|Updated Mar 17, 2026
One-click install
npx skills add https://github.com/merge-api/merge-gateway-skills --skill migrate-direct-provider-sdks-to-merge-gateway
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: Migrate Direct Provider SDKs to Merge Gateway
Source: https://github.com/merge-api/merge-gateway-skills/tree/main/.claude/skills/migrate-direct-sdk
Command: npx skills add https://github.com/merge-api/merge-gateway-skills --skill migrate-direct-provider-sdks-to-merge-gateway

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Replaces direct usage of OpenAI, Anthropic, and Google SDKs with the Merge Gateway SDK to unify API access, improve key management, and simplify migrations.

Core Features & Use Cases

  • Detects direct provider SDK usage (OpenAI, Anthropic, Google Generative AI) in Python and TypeScript projects.
  • Migrates client constructors to use the Merge Gateway SDK, prefixes models with provider tags, and consolidates keys into a single MERGE_GATEWAY_API_KEY.
  • Guides Google Generative AI migrations and handles model-name normalization, embeddings, and multi-provider routing where relevant.
  • Supports end-to-end migration workflows from detection to verification, with guidance for local development or CI/CD environments.

Quick Start

Run /migrate-direct-sdk to begin migrating all direct provider SDK usage to Merge Gateway.

Frequently Asked Questions about Migrate Direct Provider SDKs to Merge Gateway

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I migrate direct OpenAI and Anthropic SDKs to a unified API gateway?

Run the migration command to automatically detect direct provider SDK usage in Python or TypeScript, replace client constructors with the Merge Gateway SDK, and consolidate authentication into a single MERGE_GATEWAY_API_KEY.

Does the Merge Gateway migration support both Python and TypeScript projects?

Yes, the migration supports both Python and TypeScript projects, detecting direct usage of OpenAI, Anthropic, and Google Generative AI SDKs to update constructors and normalize model names.

What do I need to route my provider SDKs through Merge Gateway?

You need a valid MERGE_GATEWAY_API_KEY and an existing Python or TypeScript project currently using direct OpenAI, Anthropic, or Google Generative AI SDKs.

How does multi-provider routing handle Google Generative AI model names?

Google Generative AI migrations handle model-name normalization by prefixing models with provider tags, ensuring correct multi-provider routing through the Merge Gateway SDK.

Can I verify direct SDK migration to Merge Gateway in a CI/CD environment?

Yes, the migration workflow supports end-to-end detection, migration, and verification steps designed for both local development environments and CI/CD pipelines.