SDK migration
15M input + 4M output tokens / month
Existing OpenAI app with moderate traffic
- Official (GPT-5.6 Terra)
- $97.50/mo
- LumeAPI
- $48.75/mo
- Monthly savings
- $48.7550% off
OpenAI-compatible gateway
LumeAPI exposes GPT, Claude, Gemini, image, and video models through a single OpenAI-compatible base URL — change your API key, base URL, and model id without rewriting application code.
Works with the OpenAI Python/Node SDKs, curl, Cursor, LangChain, and most agents that already call /v1/chat/completions.
Official reference vs LumeAPI catalog rates. Pricing unit: per 1M input / output tokens. Last updated: July 2026. Source: provider list price.
Illustrative totals for gpt-5.6-terra using catalog list prices — your actual bill depends on retries, tool loops, and output length.
15M input + 4M output tokens / month
Existing OpenAI app with moderate traffic
60M input + 18M output tokens / month
GPT for chat, Claude for analysis, Gemini for RAG
Three values change: API key, base URL, model id. Everything else stays the same.
from openai import OpenAI
client = OpenAI(api_key="YOUR_OPENAI_API_KEY")
response = client.chat.completions.create(
model="gpt-5.6-terra",
messages=[{"role": "user", "content": "Hello"}],
)from openai import OpenAI
client = OpenAI(
api_key="YOUR_LUMEAPI_KEY",
base_url="https://api.lumeapi.site/v1",
)
response = client.chat.completions.create(
model="gpt-5.6-terra",
messages=[{"role": "user", "content": "Hello"}],
)Full step-by-step rollout, streaming checks, and FAQ: OpenAI API Too Expensive? migration guide →
Chat Completions, image generations, and async video follow OpenAI-compatible paths documented in /docs. Provider-specific features may differ — test your payload.
Every text model in our catalog uses POST /v1/chat/completions. Image and video models use their documented endpoints — see per-model docs.
Authorization: Bearer YOUR_LUMEAPI_KEY on every request. Keys are created in Console after registration.
See Privacy Policy for retention and subprocessors. You are responsible for what you send through the gateway.
Keep Chat Completions request bodies. Set base_url to https://api.lumeapi.site/v1 and swap model id to a catalog entry — no new SDK required.
Configure custom OpenAI endpoint in Cursor settings. Use LumeAPI key and catalog model ids for lower-cost daily coding traffic.
Any framework that accepts openai_api_base works out of the box. Route different chains to GPT, Claude, or Gemini by model id only.
Mirror production traffic on LumeAPI in a staging environment. Compare latency, streaming, and tool-call behavior per model.
No for standard chat. Use the OpenAI SDK with LumeAPI base URL and catalog Claude or Gemini ids. Test tool calling for your agent use case.
LumeAPI focuses on Chat Completions and multimodal generation documented in /docs. Check catalog for supported endpoints before migrating niche APIs.
Yes on supported models with stream: true. Validate reconnect and partial JSON handling in your client before production.
Yes. One wallet debits all modalities. See model pages for image and video parameter differences.
Most teams change three env vars and redeploy. Allow time to regression-test streaming, tools, and error handling on top models.
Start at /docs for gateway overview, then /docs/models/{id} for per-model parameters and curl examples.
Register, create a key, and set base_url to https://api.lumeapi.site/v1. Need help choosing a model? Browse the developer docs or contact support.