Skip to main content
Pi is a terminal coding agent. Route it through Edgee to reduce token costs with lossless compression and gain full observability over every session. The fastest way to connect Pi to Edgee is the CLI. It authenticates, registers an Edgee provider in your Pi config (populated from the live Edgee model catalog), and starts Pi.
Pi 0.79.4 or newer is required. Earlier versions read the credential differently and the gateway answers 401.
1

Install the Edgee CLI

2

Launch Pi through Edgee

Choose how you want to launch. Both options route requests through Edgee.
With aliases installed in the previous step, use your usual command:
The alias runs edgee launch for you, so requests go through Edgee.
If you are not signed in, Edgee starts sign-in automatically at launch. Follow the prompts and select your organization when asked.Token compression is enabled automatically. Pick an Edgee model from Pi’s model picker, or pass one directly:
After the session ends, the CLI prints a link to view token usage, compression savings, and cost breakdown in the Edgee Console. The CLI adds a single edgee provider to ~/.pi/agent/models.json (or your PI_CODING_AGENT_DIR, if set). It is additive: every other provider, model, and login you already had keeps working. Each model carries its context window and per-million-token rates from the Edgee catalog, so Pi’s context gauge and session cost readout work instead of reporting every session as 0.YourAPIkeyisstoredasa‘0. Your API key is stored as a `EDGEE_API_KEY` reference and supplied at launch, never written to disk.

​
Manual setup (advanced)

​
Get your coding-agent key

Manual setup uses the key of your enrolled Pi agent, not a standard API key created for LLM Router applications.
  1. Open the Edgee Console and select your organization.
  2. In the header, click Set up coding agent or +, select Pi, and click Enroll. If your agent is already enrolled, use its existing icon.
  3. Click the agent’s icon, then Advanced settings → Advanced.
  4. Under Edgee API key (for manual setup), click Reveal key, then the copy icon.
Use this key wherever the configuration below shows <YOUR_CODING_AGENT_KEY>.

​
Configure Pi

Prefer to configure Pi yourself? Add the provider to ~/.pi/agent/models.json and declare the models you want:
Then export your key from the Edgee Console before running pi:
baseUrl carries no /v1 suffix: with api: "anthropic-messages", Pi appends /v1/messages itself. A custom provider in Pi is defined by its models, so the models list cannot be empty. edgee launch pi writes all of this for you from the live catalog.

​
Next Steps

​
Verify the connection

Send one request from the configured client, then open Logs in the same Edgee organization. Check the served model, provider, and key. For a CLI-launched coding agent, also inspect its session report. If the request is missing, check that you launched through Edgee or saved the client’s gateway URL and coding-agent key. If it appears with an error, inspect the error before changing settings. See Troubleshooting and Gateway errors.