Paste your OpenAI code or config
What the checker looks for
The scanner performs six checks on your code:
| Check | What it looks for | Why it matters |
|---|---|---|
| SDK detection | openai Python SDK, openai Node SDK, or direct HTTP | Determines if you can just swap base_url |
| Base URL | Hardcoded api.openai.com or configurable | Plugsky needs a different base URL |
| API key format | sk-proj-, sk-, sk-live- patterns | Different providers use different key prefixes |
| Model names | gpt-*, claude-*, gemini-* vs provider models | Model names differ across providers |
| Streaming format | stream=True, stream:true, SSE handling | Streaming works the same across providers |
| Function calling | tools, functions, tool_choice params | Format is consistent across providers |
OpenAI compatibility explained
The OpenAI API format has become the industry standard. Most AI providers — including Plugsky, Together AI, Groq, Fireworks AI, DeepSeek, xAI, Mistral, and Cerebras — implement the same /v1/chat/completions endpoint with identical JSON schemas.
This means code written for OpenAI often needs only three changes to work with another provider:
- Base URL — Change from
https://api.openai.com/v1to the provider's endpoint (e.g.https://api.plugsky.com/v1) - API key — Replace your OpenAI key with the provider's key
- Model name — Use a model the provider supports (e.g.
plugsky-proinstead ofgpt-4o)
Common migration issues
- Hardcoded model names — If you check for
gpt-4in your code to decide behavior, you need to also check for the new provider's models - OpenAI-only features —
response_format: json_object,seed, and parallel tool calls might not be supported everywhere - Rate limit assumptions — OpenAI uses tier-based RPM/TPM limits; other providers have different ceilings
- Streaming chunk format — Every provider uses the same SSE
data: {...}format, but some include extra fields
Migration example: Python SDK
# Before (OpenAI)
from openai import OpenAI
client = OpenAI(api_key="sk-proj-...")
resp = client.chat.completions.create(
model="gpt-4o-mini",
messages=[{"role": "user", "content": "Hello!"}],
)
# After (Plugsky)
from openai import OpenAI
client = OpenAI(
api_key="sk-live-PLUGSKY-...",
base_url="https://api.plugsky.com/v1",
)
resp = client.chat.completions.create(
model="plugsky-pro",
messages=[{"role": "user", "content": "Hello!"}],
)Migration example: cURL
# Before (OpenAI)
curl https://api.openai.com/v1/chat/completions \
-H "Authorization: Bearer $OPENAI_KEY" \
-H "Content-Type: application/json" \
-d '{"model": "gpt-4o-mini", "messages": [{"role": "user", "content": "Hello!"}]}'
# After (Plugsky)
curl https://api.plugsky.com/v1/chat/completions \
-H "Authorization: Bearer $PLUGSKY_KEY" \
-H "Content-Type: application/json" \
-d '{"model": "plugsky-pro", "messages": [{"role": "user", "content": "Hello!"}]}'Frequently asked questions
What does the OpenAI compatibility checker do?
It analyzes your existing OpenAI API code to detect SDK version, base URL usage, API key format, model names, streaming format, and function calling patterns. It then gives you a compatibility score (0-100%) and a list of specific changes needed to switch to Plugsky or other OpenAI-compatible providers.
Is my code sent to a server?
No. All analysis happens in your browser. Your code never leaves your machine. The checker uses pattern matching on the text you paste.
Is the compatibility checker free?
Yes. This tool is free to use with no signup required. Sign up for unlimited API access on Plugsky once you are ready to migrate.
Which providers are OpenAI-compatible?
Plugsky, Together AI, Groq, Fireworks AI, DeepSeek, xAI, Mistral, Cerebras, and many more use the OpenAI-compatible API format. Most only require changing the base URL, API key, and model name.
Can I migrate without changing my code?
If you use the openai Python or Node SDK with a configurable base URL, yes — you only need to change the base URL, API key, and model name. Plugsky uses the exact same SDKs. If you use LangChain, LlamaIndex, or Vercel AI SDK, you only need to change the model configuration.
Last updated Jul 2026. Prices and availability verified at time of writing — check provider pages for current rates.
Ready to migrate?
Get a Plugsky API key and switch in 5 minutes. No credit card required.
Start Free → API reference