Connect your Fireworks account
Use a gateway-managed model catalog
These gateways expose their own model catalogs. Fireworks may serve a request, but you are not connecting an arbitrary Fireworks model ID.Gateway catalogs do not necessarily expose
firerouter/... IDs. Verify that
the gateway preserves the exact Fireworks model ID and forwards any provider
headers you require.LiteLLM Proxy
Use LiteLLM as a shared gateway for Fireworks serverless models, model routers, and deployments. Developers call one OpenAI-compatible chat completions API. You manage provider credentials and access control on the LiteLLM server.Prerequisites
- A Fireworks API key (
fw_...) - LiteLLM Proxy installed:
Configure Fireworks models
Add each model you want to expose toconfig.yaml. In litellm_params.model, prefix the Fireworks model ID with fireworks_ai/. For example, firerouter/opus becomes fireworks_ai/firerouter/opus.
Start the proxy
Call a model
If LiteLLM virtual keys are configured, clients authenticate with a virtual key:API key layout
Model routers
Account-level Provider Keys determine whether closed models are eligible. An Anthropic key covers barefirerouter and routes containing a Claude family alias or Anthropic model ID. An OpenAI key covers routes containing Astra or another OpenAI model. For credentials on direct API calls, see APIs and SDKs.