LumeAPI
Get started

High-volume LLM API

High-Volume LLM API — 100M+ Tokens at Lower Marginal Cost

At 100M or 1B tokens per month, marginal cost matters. LumeAPI catalog rates on GPT, Claude, and Gemini reduce spend on real-time high-throughput workloads.

Compare official Batch for async jobs vs LumeAPI for interactive high-volume apps.

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

High-volume model 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.4 minigpt-5.4-mini$0.75 / $4.50$0.375 / $2.2550% offDetails →
Gemini 3.5 Flashgemini-3.5-flash$1.50 / $9.00$0.90 / $5.4040% offDetails →
Gemini 3 Flashgemini-3-flash$0.50 / $3.00$0.30 / $1.8040% offDetails →
GPT-5.6 Terragpt-5.6-terra$2.50 / $15.00$1.25 / $7.5050% offDetails →

Monthly cost examples

Illustrative totals for gemini-3.5-flash using catalog list prices — your actual bill depends on retries, tool loops, and output length.

100M tokens / month

80M input + 20M output tokens / month

Flash-heavy routing workload

Official (Gemini 3.5 Flash)
$300.00/mo
LumeAPI
$180.00/mo
Monthly savings
$120.0040% off

Rates last updated July 2026

1B tokens / month

800M input + 200M output tokens / month

Enterprise-scale agent platform

Official (Gemini 3.5 Flash)
$3,000.00/mo
LumeAPI
$1,800.00/mo
Monthly savings
$1,200.0040% off

Rates last updated July 2026

Plan at 100M and 1B tokens

At hundreds of millions of tokens per month, small per-million differences become real budget lines. Use scenario cards as order-of-magnitude checks, then load-test staging and export Usage.

Official Batch APIs can reduce async workloads; LumeAPI targets interactive products that need real-time responses at lower catalog list rates.

Tier aggressively: Flash and mini for bulk, flagship only where quality metrics dip.

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 at scale)

python
from openai import OpenAI

client = OpenAI(api_key="YOUR_OPENAI_API_KEY")

response = client.chat.completions.create(
    model="gemini-3.5-flash",
    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="gemini-3.5-flash",
    messages=[{"role": "user", "content": "Hello"}],
)

Full step-by-step rollout, streaming checks, and FAQ: Batch API guide — 50% off async workloads →

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

Throughput limits?

Test concurrency in staging. Retry on 429/5xx with backoff.

Batch vs real-time?

Official Batch may win async. LumeAPI for interactive high volume.

Volume discounts?

Public catalog rates. Contact support for enterprise discussions.

Cost predictability?

Published rates and per-call Usage logs.

Built for these workloads

100M+ token apps

Scenario cards show monthly totals at catalog rates.

High concurrency

Standard real-time API for interactive products.

Cost forecasting

Export Usage logs after staging week at target volume.

Model tiering

Flash and mini for bulk, flagship for escalation only.

Related guides

FAQ

Cheapest at 100M tokens?

Usually Flash or mini tiers — validate quality.

1B token cost estimate?

Scale scenario card inputs or export Usage after load test.

Bulk LLM API?

Same gateway — tier models by task complexity.

High throughput?

Implement client retries and circuit breakers.

Low-cost models?

See /low-cost-llm-api.

Pricing hub?

See /ai-api-pricing.

Model your high-volume bill

Run production traffic through https://api.lumeapi.site/v1. Need help choosing a model? Browse the developer docs or contact support.

Create API keyOpen consoleModel catalog