Skip to main content
For your own agent, follow the quickstart. For an organization, use the team rollout. For application code, create a Gateway API key.
Launch a supported agent through the CLI, for example edgee launch claude. For an existing API client, configure its Gateway base URL and key using the relevant integration guide. Verify a model request in Logs before assuming traffic is routed through Edgee.
Yes. Edgee works with your existing Claude, Codex, and Cursor subscriptions. Follow your coding assistant’s integration guide to launch it through Edgee.
Usage cost describes the value of model traffic. It is not necessarily a deduction from Edgee credits. Inspect the request’s billing indicators and your provider account. Seats and the Edgee subscription are separate from request billing.
Only when the strategy is configured to block. Stay on last continues using the final stage, subject to other applicable limits and billing conditions. A strategy and hard usage limit cannot coexist on the same scope. See Strategies.
Edgee retries eligible transient errors and can use configured fallback routes. Continuity depends on eligible models, available credentials, provider availability, and spending controls. Review both the normal route and its backups; see Retry and fallback.
The published production aggregate is 15–20% lower token bills from compression across active customers. The 50% SWE-bench Lite result is a controlled benchmark, not a forecast. Measure representative tasks and keep routing savings separate. See Compression measurements.
Yes. Register and assign them through BYOK, then verify a new request. Check that every fallback and strategy destination has eligible credentials before enabling BYOK-only.
Your organization or squad may enforce it, or your role may not allow editing. Organization Off is an enforced value, while Inherit delegates the choice. See Gateway settings.
Check organization, profile, date range, filters, and whether the agent actually made a model request through Edgee. Opening an editor alone does not create usage. See Troubleshooting.
Usage metadata and Debug payload capture are separate. Enable Debug for specific investigations; it captures future request/response content and may include code or personal data. Review Debug logs before exporting or publishing information.
Yes, through a licensed deployment of the proprietary gateway. Connected and headless modes differ in configuration synchronization and usage enforcement. See Self-hosting.
Check Models in your organization for the current catalog and allowed provider routes. Organization restrictions, key restrictions, and credentials can narrow the choices. See Model access.
Read the Privacy Policy and DPA, and contact Edgee for deployment-specific requirements and audit documentation.