Use Fireworks AI Models in Big-AGI.

Running Fireworks AI in Big-AGI

Add your Fireworks API key over its OpenAI-compatible endpoint and reach the open-model catalog at Fireworks' own rates. Big-AGI adds no markup and no intermediary: the billing relationship runs directly between you and Fireworks.

• Your key, your billing. Usage is billed by Fireworks AI to your account.
• Always current. Fireworks is a 100% live catalog: every model Fireworks adds, from DeepSeek to Llama to Kimi, appears the moment it's live on their API, with real release dates driving the "new" badges, no hand-maintained list to fall behind.
• Zero setup beyond the key. Big-AGI recognizes Fireworks endpoints by hostname and turns on the right vision and tool flags per model automatically.
• Speed as the product. Fireworks' custom inference stack pushes open models to interactive latencies, priced per token.

Why Big-AGI instead of the playground?

Fireworks' playground is built for one prompt at a time. Big-AGI turns the same key into a persistent workspace: chats that stick around, personas, and file and image attachments, all layered on top of the raw API. It's also the only place a Fireworks model runs next to Claude, GPT, and Gemini in Beam, with the parameters and the key still yours to control.

Your keys and your data

Turn on Direct Connection and the browser talks to Fireworks directly, skipping the Big-AGI server, when your key is client-side and Fireworks allows it. Your keys stay in your browser. Chats are stored locally first, and sync only if you turn it on. The AI Inspector shows the exact request, the token counts, and a cost estimate, so you always know what you're billed for.

Fireworks AI in Beam

Put a Fireworks model into a Beam alongside frontier labs, or run a few open models side by side at Fireworks' speed. Fusions then combine, cross-check, and synthesize the parallel answers instead of just picking the best one. Parallel runs use more tokens than a single chat.