Prerequisites
- Pi installed
- A Fireworks API key (
fw_...) or a Fire Pass key (fpk_...) - FireConnect v0.9.0+ (see Install)
Enable Fireworks routing
Using Fire Pass
Use yourfpk_... key during login or with --api-key:
glm-fast-latest.
Default model
Pi routes a single default model. The default isglm-fast-latest.
What gets written
FireConnect:- Sets
defaultProvider/defaultModelin~/.pi/agent/settings.json - Stores a baked plaintext literal in
fireworks.keyin~/.pi/agent/auth.json(mode0600) - Registers the preferred serverless catalog in
~/.pi/agent/models.jsonfor Pi’s/modelpicker
~/.fireconnect/pi/ before the first change. Running fireconnect pi off restores them byte-for-byte.
Browsing and picking models
fpk_...) show Fire Pass-supported routers only and cannot select firerouter.
FireRouter
CLI reference
fireconnect pi help for all options.
Switch models
Turn off Fireworks routing
settings.json and auth.json from the backup in ~/.fireconnect/pi/.
Use a non-default settings file
Fireworks on Microsoft Foundry
Pi supports Fireworks on Microsoft Foundry (CLI:--provider azure or on --azure). See the FireConnect overview and Microsoft Foundry integration guide for portal setup.
Configure and enable
What gets written
FireConnect registers afireworks-azure openai-completions provider in Pi’s models.json (labeled Fireworks on Microsoft Foundry) and sets defaultProvider / defaultModel in settings.json. The Azure API key is stored in auth.json as a literal when passed with --api-key, or as $AZURE_API_KEY when resolved from the environment.
Pass your Foundry model with --model (for example, FW-GLM-5.2). Use fireconnect model list only for browsing Fireworks serverless models on the direct gateway path.
Turn off Foundry routing
To switch back to the Fireworks gateway:settings.json, auth.json, and models.json:
off. See Turn off Foundry routing for details on global config behavior and uninstall.