LumeAPICustomer support bot
12M input + 3M output tokens / month
Multi-turn with moderate history
- Official (Gemini 3.5 Flash)
- $45.00/mo
- LumeAPI
- $27.00/mo
- Monthly savings
- $18.0040% off
Chatbot API
Chatbot API — Streaming, Multi-Turn & Lower Token Costs
Power chatbots and AI SaaS with GPT, Claude, and Gemini at lower list rates — streaming, conversation history, and predictable per-token billing.
Conversation history resends every turn — lower input rates matter as sessions grow.
- OpenAI-compatible
- Pay as you go
- One API key
- GPT, Claude & Gemini
Chatbot model pricing
Official reference vs LumeAPI catalog rates. Pricing unit: per 1M input / output tokens. Last updated: July 2026. Source: provider list price.
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.
High-traffic SaaS chat
80M input + 20M output tokens / month
Flash or mini for scale
- Official (Gemini 3.5 Flash)
- $300.00/mo
- LumeAPI
- $180.00/mo
- Monthly savings
- $120.0040% off
Chat bills grow with history
Multi-turn chat APIs resend conversation history as input tokens every turn. A session that reaches 30k tokens of context makes input pricing as important as output pricing.
Streaming improves perceived latency for user-facing bots. Test stream reconnection in your web client before launch.
Tier support bots with mini or Flash for triage and Sonnet or Terra for escalations—same integration, different model ids.
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 (official provider chat)
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)
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: LLM pricing comparison →
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
Streaming latency?
Test on your region and model tier in staging.
History cost?
Every prior message counts as input tokens — model monthly cost.
Low latency models?
Flash and mini tiers for high concurrency.
Billing?
Per-call Usage logs with input/output breakdown.
Built for these workloads
Multi-turn dialogue
Lower input rates reduce history cost each turn.
Streaming UX
stream: true on supported models for responsive UI.
AI SaaS chat
Predictable margin with published catalog rates.
Support chatbots
Mini or Flash for tier-1, Sonnet for escalation.
Related guides
FAQ
Cheap chatbot API?
Compare Flash and GPT mini for your output ratio.
Streaming support?
Yes on catalog text models with stream: true.
GPT vs Claude vs Gemini for chat?
Test quality on your prompts. Compare input $/1M for long sessions.
Conversation memory?
You manage history in messages array — tokens bill each request.
Production?
See /production-llm-api.
Pricing hub?
See /ai-api-pricing.
Launch your chatbot on LumeAPI
Stream chat completions through https://api.lumeapi.site/v1. Need help choosing a model? Browse the developer docs or contact support.