LumeAPIAI SaaS backend
35M input + 12M output tokens / month
Multiple features, one gateway
- Official (GPT-5.6 Terra)
- $267.50/mo
- LumeAPI
- $133.75/mo
- Monthly savings
- $133.7550% off
LLM API gateway
LLM API Gateway — Unified GPT, Claude & Gemini Entry
One OpenAI-compatible gateway for GPT, Claude, and Gemini — switch models, one API key, wallet billing, and Usage logs without maintaining three vendor SDKs.
Simple unified access at lower catalog rates — not complex auto-routing or user-configurable failover.
- OpenAI-compatible
- Pay as you go
- One API key
- GPT, Claude & Gemini
Gateway flagship models
Official reference vs LumeAPI catalog rates. Pricing unit: per 1M input / output tokens. Last updated: July 2026. Source: provider list price.
| Model | Official (in / out) | LumeAPI (in / out) | Savings | |
|---|---|---|---|---|
| GPT-5.6 Terragpt-5.6-terra | $2.50 / $15.00 | $1.25 / $7.50 | 50% off | Details → |
| Claude Sonnet 4.6claude-sonnet-4-6 | $3.00 / $15.00 | $1.80 / $9.00 | 40% off | Details → |
| Gemini 3.1 Progemini-3.1-pro-preview | $2.00 / $12.00 | $1.20 / $7.20 | 40% off | Details → |
| Gemini 3.5 Flashgemini-3.5-flash | $1.50 / $9.00 | $0.90 / $5.40 | 40% off | Details → |
Monthly cost examples
Illustrative totals for gpt-5.6-terra using catalog list prices — your actual bill depends on retries, tool loops, and output length.
Agent platform
100M input + 30M output tokens / month
Per-step model selection
- Official (GPT-5.6 Terra)
- $700.00/mo
- LumeAPI
- $350.00/mo
- Monthly savings
- $350.0050% off
Simple gateway, honest limits
LumeAPI is a unified LLM API gateway for teams that want lower mainstream model costs without operating their own router fleet. You choose the model id on each request; we do not expose user-configurable auto-failover or opaque provider remapping.
That honesty matters for production: your Usage row matches the model you requested. Implement retries, timeouts, and fallback routes in your application when you need resilience.
AI SaaS, agent platforms, and internal automation tools benefit from one gateway credential rotated through environment secrets per environment.
Self-serve path: register to first API call
LumeAPI is designed for developers who want to integrate without scheduling demos. Create an account, confirm your email, and open Console to generate an API key. Fund your USD wallet with USDT on supported chains when you are ready for billable traffic—there is no mandatory minimum beyond what your tests require.
Point your OpenAI-compatible client at https://api.lumeapi.site/v1, set Authorization to Bearer your key, and pass a catalog model id in the model field. Run a short curl or SDK script from /docs to verify latency, streaming, and error handling before you attach the key to production services.
Use Usage logs to reconcile per-call cost with finance forecasts. When a model tier is too expensive or quality is insufficient, change model id—not your entire integration. For cross-provider price tables and Research deep dives, follow internal links on this page rather than duplicating migration math here.
Documentation, catalog, and support
Every catalog model has a detail page under /models with official reference pricing, LumeAPI pricing, and links to /docs/models/{id} for parameters and curl examples. Start there when this commercial page points you to a model id you have not called before.
The /docs index lists gateway authentication, Chat Completions, image endpoints, and async video patterns. llms.txt bundles the same information for agent tooling—useful when you want a single URL to paste into Cursor or an internal bot.
Research articles explain why bills grow and how to compare providers; commercial pages like this one explain what LumeAPI offers and how to start. Follow internal links instead of searching for duplicate migration content across pages.
If billing, chain deposits, or integration behavior is unclear, use /contact for support channels. Include your model id, approximate request time, and whether the issue is authentication, balance, or model parameters—that speeds up resolution.
Why LumeAPI
Mainstream models only
GPT, Claude, and Gemini catalog ids with published per-token or per-media rates — not obscure small models marketed as discounts.
Transparent pricing
Official reference vs LumeAPI columns on every commercial page. Your request model id matches Usage logs and billing.
OpenAI-compatible gateway
One base URL for Chat Completions, image generations, and async video. Swap key, base URL, and model id — keep your SDK.
Self-serve wallet
Top up with USDT, create keys in Console, and track per-call cost in Usage — no sales calls required.
Get started in three steps
- Create an API key — register and open Console.
- Set the LumeAPI base URL — https://api.lumeapi.site/v1
- Choose a supported model id — from the table above or model catalog.
Migrate in minutes
Three values change: API key, base URL, model id. Everything else stays the same.
Before (multiple provider endpoints)
# Separate SDKs per provider — three keys and billing relationships
After (LumeAPI)
from openai import OpenAI
client = OpenAI(api_key="YOUR_LUMEAPI_KEY", base_url="https://api.lumeapi.site/v1")
for model in ("gpt-5.6-terra", "claude-sonnet-4-6", "gemini-3.5-flash"):
r = client.chat.completions.create(
model=model,
messages=[{"role": "user", "content": "Reply with your model name only."}],
)
print(model, r.choices[0].message.content)Full step-by-step rollout, streaming checks, and FAQ: Model routing guide — quality, speed and reliability →
Migration & compatibility
What changes
API key, base URL (https://api.lumeapi.site/v1), and model id to a LumeAPI catalog entry. Message shape stays OpenAI-compatible for most apps.
What to test
Streaming, tool calling, JSON mode, and error handling on your heaviest models. Shadow 5–10% of traffic before full cutover.
What may differ
Provider-native features (Anthropic Batch, Google Grounding, OpenAI Assistants) may require the official API. Test your exact payload.
Rollback
Keep environment variables for base URL and model id. Switch back instantly if staging tests fail.
Trust & billing
Auto-routing between providers?
You choose model id per request. No silent provider routing.
Usage records?
Per-call logs in Console with model id and cost.
Wallet billing?
One USD balance debited per successful call.
Failover?
Implement in your app with env vars — LumeAPI does not auto-failover.
Built for these workloads
AI SaaS
One integration for all model tiers behind your product.
Agents
Swap model id per agent without new vendor contracts.
Automation
Cron jobs and workflows on one key and wallet.
Error handling
Standard OpenAI-compatible errors — test retry logic in staging.
Related guides
FAQ
vs OpenRouter gateway?
LumeAPI: mainstream models, lower rates, simpler stack. OpenRouter: broader catalog and routing.
vs /multi-model-api?
Gateway emphasizes unified entry for products. Multi-model emphasizes account simplicity.
Custom routing rules?
Your application logic chooses model id — not platform-side routing.
Observability?
Usage logs and wallet balance in Console.
Production?
See /production-llm-api.
Pricing?
See /ai-api-pricing.
Deploy your unified LLM gateway
Point all services at https://api.lumeapi.site/v1. Need help choosing a model? Browse the developer docs or contact support.