> ## Documentation Index
> Fetch the complete documentation index at: https://www.edgee.ai/docs/llms.txt
> Use this file to discover all available pages before exploring further.

# FAQ

> Answers about setup, billing, routing, data, and troubleshooting.

> [accordion] Where should I start?
>
> For your own agent, follow the [quickstart](https://www.edgee.ai/docs/quickstart/index.md). For an organization, use the [team rollout](https://www.edgee.ai/docs/quickstart/team.md). For application code, create a [Gateway API key](https://www.edgee.ai/docs/llm-router/quickstart/api-key.md).

> [accordion] Do I need to change my agent or application code?
>
> 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.

> [accordion] Can I keep my provider subscription?
>
> Yes. Edgee works with your existing Claude, Codex, and Cursor subscriptions. Follow your [coding assistant’s integration guide](https://www.edgee.ai/docs/quickstart/index.md) to launch it through Edgee.

> [accordion] Why is there a cost if I use a subscription or BYOK?
>
> 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.

> [accordion] Does a routing budget stop requests at 100%?
>
> 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](https://www.edgee.ai/docs/features/routing-strategies.md).

> [accordion] What happens when a provider fails?
>
> 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](https://www.edgee.ai/docs/features/retry-and-fallback.md).

> [accordion] How much does compression save?
>
> 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](https://www.edgee.ai/docs/features/token-compression.md#what-youll-actually-save).

> [accordion] Can I use my own provider credentials?
>
> Yes. Register and assign them through [BYOK](https://www.edgee.ai/docs/features/byok.md), then verify a new request. Check that every fallback and strategy destination has eligible credentials before enabling BYOK-only.

> [accordion] Why is a setting locked?
>
> 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](https://www.edgee.ai/docs/features/organization.md).

> [accordion] Why is my session missing?
>
> 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](https://www.edgee.ai/docs/troubleshooting.md).

> [accordion] Does normal usage reporting capture my prompts?
>
> Usage metadata and Debug payload capture are separate. Enable [Debug](https://www.edgee.ai/docs/features/debug.md) for specific investigations; it captures future request/response content and may include code or personal data. Review [Debug logs](https://www.edgee.ai/docs/features/debug.md) before exporting or publishing information.

> [accordion] What does a public session link reveal?
>
> Public summaries show identity and usage information. Open the public page and inspect it before sharing the URL. Do not assume that organization authentication protects a public link. See [Sessions](https://www.edgee.ai/docs/features/observability/sessions.md#sharing).

> [accordion] Can we run Edgee on our own infrastructure?
>
> Yes, through a licensed deployment of the proprietary gateway. Connected and headless modes differ in configuration synchronization and usage enforcement. See [Self-hosting](https://www.edgee.ai/docs/self-hosting/overview.md).

> [accordion] Which models and providers can we use?
>
> 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](https://www.edgee.ai/docs/features/model-access.md).

> [accordion] Where do we review security and compliance requirements?
>
> Read the [Privacy Policy](https://www.edgee.ai/privacy) and [DPA](https://www.edgee.ai/dpa), and [contact Edgee](https://www.edgee.ai/contact) for deployment-specific requirements and audit documentation.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.