Pi

Route the Pi coding agent through Edgee to cut token costs and gain full observability, with one command.

Pi is a terminal coding agent installed from npm. Route it through Edgee to reduce token costs with lossless compression and gain full observability over every session.

Edgee CLI setup (recommended)

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.

1. Install the Edgee CLI

   macOS / Linux

   curl -fsSL https://edgee.ai/install.sh | bash
   

   Homebrew (macOS)

   brew install edgee-ai/tap/edgee
   

   Windows (PowerShell)

   irm https://edgee.ai/install.ps1 | iex
   
2. Install Pi

   npm install -g @mariozechner/pi-coding-agent
   

   Pi 0.79.4 or newer is required. Earlier versions read the credential differently and the gateway answers 401.

3. Launch Pi through Edgee

   edgee launch pi
   

   Token compression is enabled automatically. Pick an Edgee model from Pi’s model picker, or pass one directly:

   edgee launch pi -- --model anthropic/claude-sonnet-5
   

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. Your API key is stored as a `$EDGEE_API_KEY` reference and supplied at launch, never written to disk.

Manual setup (advanced)

Prefer to configure Pi yourself? Add the provider to ~/.pi/agent/models.json and declare the models you want:

{
  "providers": {
    "edgee": {
      "name": "Edgee",
      "baseUrl": "https://edgee.io",
      "api": "anthropic-messages",
      "apiKey": "$EDGEE_API_KEY",
      "headers": {
        "x-edgee-api-key": "$EDGEE_API_KEY"
      },
      "models": [
        {
          "id": "anthropic/claude-sonnet-4-5",
          "name": "anthropic/claude-sonnet-4-5",
          "contextWindow": 1000000,
          "maxTokens": 64000,
          "cost": {
            "input": 3,
            "output": 15,
            "cacheRead": 0.3,
            "cacheWrite": 3.75
          }
        }
      ]
    }
  }
}

Then export your key from the Edgee Console before running pi:

export EDGEE_API_KEY="<YOUR_EDGEE_API_KEY>"

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.

Benefits

Cost reduction

Edgee’s token compression reduces the tokens sent to and from the model, with no change to output quality.

Observability

Every request is logged in the Edgee Console with token counts, latency, and cost breakdowns.

Reliability

Automatic retry and fallback across providers keeps your sessions running even when a provider has issues.

One command

No config to edit, the CLI wires everything up.

Next Steps

• Learn more about the Edgee CLI and its launch commands
• Set up observability to monitor usage and costs
• Explore retry and fallback for resilient routing