Start a request
Buy prepaid credits, request trial tokens, or contact sales for reserved capacity.
Use the same three values in Cline, Hermes Agent, OpenClaw, Roo Code, and other OpenAI-compatible clients: base URL, model ID, and your LighterHub API key. LighterHub is currently a single-model setup.
Use this flow for direct LighterHub API access. RapidAPI is useful for marketplace testing, but coding agents usually need the direct OpenAI-compatible base URL and key.
Buy prepaid credits, request trial tokens, or contact sales for reserved capacity.
LighterHub checks payment, region, workload fit, and Qwen3.6 capacity before sending credentials.
Use the base URL, model ID, and API key in your OpenAI-compatible client.
Start with one file edit or repo question before launching a long autonomous loop.
Select the client you are setting up. The matching guide appears here, with the shared LighterHub fields repeated for less scrolling.
lighterhub-qwen.
hermes model.lighterhub-qwen.model:
provider: custom
model: lighterhub-qwen
base_url: https://api.lighterhub.app/v1
api_key: ${LIGHTERHUB_API_KEY}
api_mode: chat_completions
models.providers.openai-completions adapter for the LighterHub /v1 endpoint.lighterhub/lighterhub-qwen.{
"models": {
"mode": "merge",
"providers": {
"lighterhub": {
"baseUrl": "https://api.lighterhub.app/v1",
"apiKey": "${LIGHTERHUB_API_KEY}",
"api": "openai-completions",
"models": [
{
"id": "lighterhub-qwen",
"name": "LighterHub Qwen3.6 35B-A3B",
"reasoning": false,
"input": ["text"],
"contextWindow": 262000,
"maxTokens": 8192
}
]
}
}
},
"agents": {
"defaults": {
"model": { "primary": "lighterhub/lighterhub-qwen" }
}
}
}
Roo's official docs say Roo Code products shut down on May 15, 2026. Use this only for existing installs after confirming compatibility, or choose Cline, Hermes Agent, OpenClaw, or another OpenAI-compatible client.
If an app fails, first test the same key and model with a small OpenAI-compatible request.
curl https://api.lighterhub.app/v1/chat/completions \
-H "Authorization: Bearer $LIGHTERHUB_API_KEY" \
-H "Content-Type: application/json" \
-d '{
"model": "lighterhub-qwen",
"messages": [
{
"role": "user",
"content": "Reply with one sentence confirming the connection."
}
],
"max_tokens": 64
}'
Use the same API key to view your current balance, recent usage summary, and a CSV export for your own records.
Shows remaining prepaid credit, lifetime spend, free-trial status, and pass status when an API pass is active.
Returns request IDs, timestamps, model, status, latency, token counts, billable flag, balance metadata, and cost metadata.
Usage exports contain metadata only. Prompts and model responses are not stored in the customer export.
curl https://api.lighterhub.app/billing/balance \
-H "Authorization: Bearer $LIGHTERHUB_API_KEY"
curl "https://api.lighterhub.app/billing/usage?hours=24&limit=200" \
-H "Authorization: Bearer $LIGHTERHUB_API_KEY"
curl "https://api.lighterhub.app/billing/usage?hours=24&format=csv&limit=1000" \
-H "Authorization: Bearer $LIGHTERHUB_API_KEY" \
-o lighterhub-usage-24h.csv
hours can be 1-168, limit can be 1-1000, and format can be json or csv.
Most setup failures come from one of these field mismatches.
Use https://api.lighterhub.app/v1 as the base URL. Do not paste the full /chat/completions URL into app settings.
Model-not-found errors usually mean the app used a different ID or selected a default OpenAI model.
Do not commit API keys into repos, screenshots, issue reports, or shared config files.
Send the app name, the provider screen you are on, and the error text with the API key redacted. LighterHub can confirm the correct base URL, model ID, and access path.