> ## 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.

# API overview

> Choose the Gateway API for model requests or the Console API for organization management.

Edgee exposes two APIs with different credentials and responsibilities.

| API | Use it for | Credential |
| - | - | - |
| Gateway API, `https://edgee.io` | Model requests, streaming, and token operations | Gateway API key |
| Console API | Organizations, Gateway keys, provider keys, and usage exports | Personal API token |

Start with [your first Gateway request](https://www.edgee.ai/docs/llm-router/quickstart/api-key.md) or [Console API setup](https://www.edgee.ai/docs/api-reference/console-api-setup.md). A provider credential registered through BYOK does not replace either Edgee credential.

## Choose a request format

| Endpoint | Client or task |
| - | - |
| [`POST /v1/chat/completions`](https://www.edgee.ai/docs/llm-router/api-reference/chat-completion) | OpenAI Chat Completions clients |
| [`POST /v1/responses`](https://www.edgee.ai/docs/llm-router/api-reference/responses) | OpenAI Responses clients |
| [`POST /v1/messages`](https://www.edgee.ai/docs/llm-router/api-reference/messages) | Anthropic Messages clients |
| [Models](https://www.edgee.ai/docs/llm-router/api-reference/models.md) | Discover available models |
| [Count tokens](https://www.edgee.ai/docs/llm-router/api-reference/count-tokens.md) | Count input tokens |
| [Compress](https://www.edgee.ai/docs/llm-router/api-reference/compress.md) | Use the compression endpoint |

Choose the format expected by your existing client. Model capabilities and supported request fields vary; API compatibility does not mean every provider implements every feature. Use a canonical `author/model` identifier from the model catalog where required.

For OpenAI clients, the usual base URL includes `/v1`: `https://edgee.io/v1`. Anthropic clients append their own endpoint paths; follow the [Anthropic SDK guide](https://www.edgee.ai/docs/llm-router/integrations/anthropic.md).

## Verify and diagnose

After sending a request, find it in **Logs** for the same organization and API key. Inspect the served model/provider and cost. Routing settings can select a different model from the one requested.

For a failed request, inspect both the HTTP status and error body. A 429 caused by a spending limit needs a different response from a transient rate limit. See [Authentication](https://www.edgee.ai/docs/llm-router/api-reference/authentication.md), [Errors](https://www.edgee.ai/docs/llm-router/api-reference/errors.md), and [Usage limits](https://www.edgee.ai/docs/features/usage-limits.md).


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