Daily coding (Sonnet)
12M input + 4M output tokens / month
Sonnet 4.6 for IDE workflows
- Official (Claude Sonnet 4.6)
- $96.00/mo
- LumeAPI
- $57.60/mo
- Monthly savings
- $38.4040% off
Claude API
Claude Sonnet 4.6, Opus 4.8, and Opus 4.7 at ~40% below reference — OpenAI-compatible and exact model ids.
Hub for all Claude models. See Sonnet and Opus pages for specifics.
Official reference vs LumeAPI catalog rates. Pricing unit: per 1M input / output tokens. Last updated: July 2026. Source: provider list price.
Illustrative totals for claude-sonnet-4-6 using catalog list prices — your actual bill depends on retries, tool loops, and output length.
12M input + 4M output tokens / month
Sonnet 4.6 for IDE workflows
8M input + 6M output tokens / month
Opus 4.8 for max depth
Claude Sonnet 4.6 is the default for coding copilots, document workflows, and agents. Opus 4.8 is selective escalation—not every request needs maximum depth.
All Claude models on LumeAPI use catalog ids you can verify in Usage logs. Read /claude-sonnet-api and /claude-opus-api for role-specific pricing narratives and code samples.
For cost-focused migration stories, /cheap-claude-api links Research with step-by-step rollout guidance.
Standardize on catalog Claude ids in config files—not display names—so Usage reconciliation is trivial. Sonnet should be the default route; Opus routes should be explicit and auditable.
If you migrate from Anthropic SDK message formats, map roles and tool schemas to OpenAI-compatible Chat Completions and run parallel requests in staging until diffs are acceptable.
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="claude-sonnet-4-6",
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="claude-sonnet-4-6",
messages=[{"role": "user", "content": "Hello"}],
)Full step-by-step rollout, streaming checks, and FAQ: Claude cost 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.
Not affiliated.
claude-sonnet-4-6, claude-opus-4-8, claude-opus-4-7.
Yes for Chat Completions.
Supported — test in staging.
Sonnet default. Opus when quality justifies cost.
Long inputs at lower input rates.
Multi-hop Claude at 40% lower rates.
One key for Sonnet and Opus.
See /claude-sonnet-api and /claude-opus-api.
~40% below reference.
See /cheap-claude-api.
See /claude-api-alternative.
See /production-llm-api.
See /coding-ai-api.
Create a key and call any Claude model through https://api.lumeapi.site/v1. Need help choosing a model? Browse the developer docs or contact support.