LumeAPI
Get started

GPT API

GPT API — Models, Pricing & Integration

Call GPT-5.6, GPT-5.5, GPT-5.4, and GPT-5.4 mini through LumeAPI at roughly 50% below common official reference rates.

Hub page for all GPT models. Jump to GPT-5.6 or GPT-5.4 mini for model-specific guidance.

  • OpenAI-compatible
  • Pay as you go
  • One API key
  • GPT, Claude & Gemini
Create API keyView pricingRead docs

GPT model catalog & pricing

Official reference vs LumeAPI catalog rates. Pricing unit: per 1M input / output tokens. Last updated: July 2026. Source: provider list price.

ModelOfficial (in / out)LumeAPI (in / out)Savings
GPT-5.6 Solgpt-5.6-sol$5.00 / $30.00$2.50 / $15.0050% offDetails →
GPT-5.6 Terragpt-5.6-terra$2.50 / $15.00$1.25 / $7.5050% offDetails →
GPT-5.5gpt-5.5$5.00 / $30.00$2.50 / $15.0050% offDetails →
GPT-5.4gpt-5.4$2.50 / $15.00$1.25 / $7.5050% offDetails →
GPT-5.4 minigpt-5.4-mini$0.75 / $4.50$0.375 / $2.2550% offDetails →

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.

Flagship GPT app

20M input + 6M output tokens / month

GPT-5.6 Terra or Sol

Official (GPT-5.6 Terra)
$140.00/mo
LumeAPI
$70.00/mo
Monthly savings
$70.0050% off

Rates last updated July 2026

High-volume routing

80M input + 15M output tokens / month

GPT-5.4 mini for pre-processing

Official (GPT-5.6 Terra)
$425.00/mo
LumeAPI
$212.50/mo
Monthly savings
$212.5050% off

Rates last updated July 2026

GPT hub: pick the right tier

GPT-5.6 Sol targets complex reasoning, hard coding, and agent steps where quality dominates. GPT-5.6 Terra balances cost and capability for user-facing chat. GPT-5.4 mini is the workhorse for classification, extraction, and router layers at high volume.

Every GPT id in our catalog is documented under /models with official reference pricing, LumeAPI pricing, and curl samples. Your integration uses the same OpenAI-compatible client for all tiers.

Drill into /gpt-5-6-api or /gpt-5-4-mini-api when search intent is model-specific rather than brand-level.

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

  1. Create an API key — register and open Console.
  2. Set the LumeAPI base URL — https://api.lumeapi.site/v1
  3. 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 (official OpenAI)

python
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"}],
)

After (LumeAPI)

python
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? guide →

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

Exact GPT model ids?

gpt-5.6-terra, gpt-5.6-sol, gpt-5.4-mini — on each model page.

Official OpenAI?

LumeAPI is not affiliated with OpenAI.

Billing?

Per-token at published rates.

Streaming & tools?

Supported — test in staging.

Built for these workloads

Chat & copilots

GPT-5.6 tiers for user-facing quality. Mini for internal tools.

Agents

Sol and Terra for reasoning. Mini for tool routing.

Content generation

Compare output $/1M across GPT tiers.

IDE integrations

Point Cursor at LumeAPI with catalog GPT ids.

Related guides

FAQ

Which GPT to start with?

Terra for balanced quality. Mini for volume. Sol for hard reasoning.

Sol vs Terra?

See /gpt-5-6-api.

How much can I save?

~50% below reference on supported GPT models.

OpenAI SDK compatible?

Yes. base_url https://api.lumeapi.site/v1

GPT-5.4 mini?

See /gpt-5-4-mini-api.

Compare providers?

See /ai-api-pricing.

Start building with GPT on LumeAPI

Create a key and call any GPT model through https://api.lumeapi.site/v1. Need help choosing a model? Browse the developer docs or contact support.

Create API keyOpen consoleModel catalog