Intent classification
200M input + 10M output tokens / month
High input, short outputs
- Official (GPT-5.4 mini)
- $195.00/mo
- LumeAPI
- $97.50/mo
- Monthly savings
- $97.5050% off
GPT-5.4 mini API
GPT-5.4 mini for classification, extraction, routing, or high-frequency agent steps at ~50% below reference.
Model id: gpt-5.4-mini. Same gateway as flagship GPT 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.4 minigpt-5.4-mini | $0.75 / $4.50 | $0.375 / $2.25 | 50% off | Details → |
Illustrative totals for gpt-5.4-mini using catalog list prices — your actual bill depends on retries, tool loops, and output length.
200M input + 10M output tokens / month
High input, short outputs
50M input + 5M output tokens / month
Cheap pre-step before flagship
gpt-5.4-mini shines when outputs are short and requests are frequent: intent labels, JSON extraction, moderation pre-screens, and agent routing before an expensive flagship call.
At 200M input tokens per month, mini-tier input savings dominate the bill. Pair mini with Sonnet or Terra only on escalations to keep margin predictable.
See /high-volume-llm-api for 100M+ token forecasting templates.
Set rate limits on public endpoints that call gpt-5.4-mini—high-volume mini traffic is cheap but still finite. Alert on error-rate spikes that might indicate you need to escalate tier.
Document escalation rules in your agent orchestrator: which tool failures trigger a retry on gpt-5.6-terra or claude-sonnet-4-6 versus a user-facing error.
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.
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.
GPT, Claude, and Gemini catalog ids with published per-token or per-media rates — not obscure small models marketed as discounts.
Official reference vs LumeAPI columns on every commercial page. Your request model id matches Usage logs and billing.
One base URL for Chat Completions, image generations, and async video. Swap key, base URL, and model id — keep your SDK.
Top up with USDT, create keys in Console, and track per-call cost in Usage — no sales calls required.
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.4-mini",
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.4-mini",
messages=[{"role": "user", "content": "Hello"}],
)Full step-by-step rollout, streaming checks, and FAQ: OpenAI migration guide →
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.
Streaming, tool calling, JSON mode, and error handling on your heaviest models. Shadow 5–10% of traffic before full cutover.
Provider-native features (Anthropic Batch, Google Grounding, OpenAI Assistants) may require the official API. Test your exact payload.
Keep environment variables for base URL and model id. Switch back instantly if staging tests fail.
Exact id in request and billing.
Test on your prompts. Often used for pre-processing only.
Escalate to Terra or Sonnet when errors rise.
Per-token at published mini rates.
Short outputs at high request volume.
JSON extraction before expensive analysis.
Mini picks the next flagship model.
Background tasks without flagship reasoning.
This page focuses on gpt-5.4-mini.
See /high-volume-llm-api.
Yes. Swap model id.
Yes on LumeAPI base URL.
See /low-cost-llm-api.
See /gpt-api.
Low-cost GPT calls through https://api.lumeapi.site/v1. Need help choosing a model? Browse the developer docs or contact support.