Edgee icon

Edgee

Edgee is an AI gateway for coding agents and LLM-powered apps. It compresses token traffic, routes requests across models, and provides observability and team controls to help reduce cost and keep sessions running.

Edgee

Overview

Edgee is an AI gateway for coding agents and LLM-powered apps. It sits between your clients and model providers, then compresses token traffic, routes requests across models, and records usage so teams can reduce cost and keep work moving when a provider fails or rate limits are reached.

The site positions Edgee around three core jobs: compress, route, and observe. For coding agents, it can be installed as a transparent proxy with no code changes; for applications, it offers an OpenAI-compatible API, SDK support, and bring-your-own-key options for direct billing control.

Core capabilities

Token compression

Reduces token usage at the edge with input and output compression. The source says this can trim tool-result payloads and reduce costs without changing application code.

Routing and automatic fallback

Sends requests across multiple models and retries when providers fail or rate-limit. Edgee can also force routing to specific models for cost control or standardization.

Observability and logging

Shows usage, cost, latency, errors, and compression savings in the console and logs. The observability docs also expose token usage fields in SDK responses.

Coding-agent integration

Works as a transparent proxy for coding agents with a CLI install flow. The site says it supports Claude Code, Codex, Copilot, OpenCode, Cursor, and similar tools.

API and SDK compatibility

Supports an OpenAI-compatible API and SDK usage for apps and agents. The pricing page also notes that you can bring your own provider keys for billing control.

Team and enterprise controls

Provides team controls such as seat management, GitHub attribution, spending caps, and squad-level visibility on the Team plan. Enterprise adds SSO/SAML, private gateway options, and privacy controls.

Common use cases

  • Reduce token spend in coding agents

    Install the CLI and connect a coding assistant so requests pass through Edgee without changing application code. This is the main workflow for developers who want immediate token savings in existing agent sessions.

  • Keep work moving during provider failures

    Set a priority-ordered model chain so Edgee can retry a request automatically when a provider returns a 429 or 5xx, or when a usage cap is reached. This keeps a Claude Code session running instead of stopping mid-task.

  • Run LLM apps with shared gateway controls

    Use the gateway for an app or internal tool that calls models through an OpenAI-compatible API. Edgee can compress traffic, track usage, and let teams separate environments such as dev, staging, and production.

  • Measure usage across teams and projects

    Track cost and usage by repo, PR, developer, squad, model, or environment in the console and logs. This helps teams attribute spend and review how compression or routing affects bills over time.

  • Add governance for larger teams

    Use Team or Enterprise features to manage seats, spending caps, GitHub attribution, private gateways, or SSO/SAML. These controls are aimed at organizations that want more governance over how agents and models are used.

Pros and Cons

Pros

  • Can reduce token usage and costs through edge compression for both input and output.
  • Supports transparent routing and automatic fallback when providers fail or hit limits.
  • Provides usage and cost observability at request, session, team, repo, and PR level.
  • Works with major coding agents and also supports apps through an OpenAI-compatible API.
  • Offers team and enterprise controls for billing, attribution, and access management.

Cons

  • Some capabilities are plan-gated, such as Team-level fallback and rerouting, with Enterprise required for features like SSO/SAML and private gateways.
  • The source highlights broad compatibility, but detailed setup and behavior may vary by agent, model, or provider.

FAQ

How does Edgee fit into an existing setup?

Edgee sits between your agent or app and the LLM provider. For coding agents, the source says you can install the CLI and connect it without changing application code; for apps and agents, it offers an OpenAI-compatible API and SDK support.

What does Edgee do beyond token compression?

The source says Edgee compresses token traffic at the edge, routes requests across models, and can fall back automatically when a provider fails or a rate limit is reached. It also supports observability so you can track usage, latency, errors, and cost.

Is there a free plan or paid plan?

The pricing page states that coding-agent compression is free, with paid Team and Enterprise plans for added routing, observability, team controls, and enterprise features. It also shows a free tier for solo developers and a Team plan for developers who need shared controls.

Who is Edgee mainly for?

The source says Edgee supports Claude Code, Codex, Copilot, OpenCode, and Cursor, and it also mentions apps and agents that call LLMs through its API. Fallback models are included on the Team plan, while some enterprise capabilities such as private gateways and SSO/SAML require Enterprise.

What kind of reporting does Edgee provide?

The observability docs say Edgee tracks requests, token usage, compression savings, latency, errors, and cost at session level and in the managed console. It also supports tags and dashboards for grouping by model, project, environment, user, or tenant.

Quick Facts

Category
AI Gateway / Developer Tool
Primary users
Coding-agent users, app teams, and platform teams
Core workflow
Compress, route, and observe LLM requests
Supported agents
Claude Code, Codex, Copilot, OpenCode, Cursor
API style
OpenAI-compatible API plus SDK support
Source domain
edgee.ai