Fireworks Inference
Run inference on Fireworks AI, direct, through the Leanmcp AI Gateway proxy...
Install
npx skills add Leanmcp/gateway-skills --skill fireworks-inference -g -a claude-code -y- Repository
- Leanmcp/gateway-skills2.1k
- Category
- Testing
- Updated
- 28d ago
- License
- MIT
- Context cost
- Mediumabout 1,639 tokens
- Runs scripts
- Yes, review before use
What it does
Run inference on Fireworks AI, direct, through the Leanmcp AI Gateway proxy (aigateway.leanmcp.com) for observability, or via LiteLLM / the OpenAI SDK / raw HTTP. Covers the endpoint-and-key matrix for each route, serverless vs dedicated deployments and their cold starts, browsing and filtering the model catalogue, reasoning models that return content:null with the answer in reasoning_content, function calling, concurrency and load testing, and runner scripts where many models share one protocol with a --use-proxy toggle. Use this skill whenever the user mentions Fireworks, FIREWORKS_API_KEY, api.fireworks.ai, fireworks_ai/ model ids, accounts/fireworks/models/..., a Fireworks deployment id, the Leanmcp gateway or LEANMCP_API_KEY, app.leanmcp.com observability, or gpt-oss / kimi / glm / qwen / deepseek served on Fireworks; wants to route LLM calls through a proxy for logging or cost tracking; is debugging empty responses, 404s, scope errors, cold starts, or "the gateway isn't working"; wants to pick a Fireworks model with tool calling; or wants to sweep several models over one benchmark. Reach for it even on vague asks like "why is this model returning nothing" or "set up inference for these models" when Fireworks is in play.
Fireworks inference
Inference on Fireworks is three independent choices, and nearly every confusing failure is one of them being wrong while you debug another:
TRANSPORT ROUTE MODEL
───────── ───── ─────
raw HTTP direct Fireworks serverless
openai SDK × api.fireworks.ai × accounts/fireworks/models/<slug>
litellm Leanmcp gateway dedicated deployment
aigateway.leanmcp.com accounts/<acct>/deployments/<id>
This skill's job is to let you isolate them one at a time instead of guessing.
The route matrix, memorize this
| base URL | key | |
|---|---|---|
| direct Fireworks | https://api.fireworks.ai/inference/v1 | FIREWORKS_API_KEY |
| Leanmcp gateway | https://aigateway.leanmcp.com/v1/fireworks | LEANMCP_API_KEY |
Same models, same request and response shape. Only the endpoint and the key change, which is why routing should be a flag, never a code path. Note the key swap: through the gateway you send your Leanmcp key; the gateway holds the Fireworks credential.
Gateway keys at https://app.leanmcp.com/api-keys (top up credits first at https://app.leanmcp.com/billing); every request then shows up at https://app.leanmcp.com/observability.
Start here
Something is broken. Climb the ladder in references/verification.md, each rung isolates one layer, so the first failure names the culprit.
python scripts/fw_smoke.py --model gpt-oss-20b # raw + sdk + litellm, gateway
python scripts/fw_smoke.py --model gpt-oss-20b --direct # same, direct
