Skip to content
LLM Router
Get started

LLM Router and SDKs

Connect an application to Edgee using an existing client, an Edgee SDK, or HTTP.

Use Edgee as an LLM router when your application sends model requests directly through an API client, an SDK, or HTTP. Configure a Gateway API key and a client, then inspect the resulting requests in the console.

If you want to run Claude Code, Codex, Cursor, or another coding assistant through Edgee, start with the coding assistant quickstart.

Choose your integration

Your starting pointGuide
Existing OpenAI clientOpenAI SDK
Existing Anthropic clientAnthropic SDK
LangChain applicationLangChain
OpenClaw configurationOpenClaw
New application using an Edgee SDKTypeScript, Python, Go, or Rust
Direct HTTP requestsFirst API request and Gateway API reference

Send your first request

  1. Sign in to the console, or accept your team’s invitation.
  2. Create a Gateway API key and store it in your application's secret environment.
  3. Choose a client above and configure the appropriate base URL. OpenAI clients usually use https://edgee.io/v1; follow the integration guide for your client.
  4. Send a model request, then open Logs in the same organization to verify the key, served model, provider, and usage.

For the complete sequence, follow the application quickstart.

Configure application usage

TaskGuide
Restrict or rotate application credentialsGateway API keys
Track tokens, costs, and request tags in codeApplication observability
Use your own provider accountBYOK
Allow models and provider routesModel access
Configure routing and backupsRouting strategies
Cap application spendingUsage limits

Organization settings also apply to application traffic. Review inherited settings before changing an individual key.

Gateway API versus Console API

The Gateway API serves model requests and uses Gateway API keys. The Console API manages organization resources and uses personal API tokens. To automate key management or export usage, use the separate Console API section.