Skip to main content

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.

The Edgee API uses API keys to authenticate requests. You can view and manage your API keys in the Edgee Console. Please refer to the Create an API Key guide to know more about how to create an API key.
Your API keys carry many privileges, so be sure to keep them secure!Do not share your API keys in publicly accessible areas such as GitHub, client-side code, and so forth.
Authentication to the API is performed via Bearer authentication (also called token authentication). It is an HTTP authentication scheme that involves security tokens called bearer tokens. The client must send this token in the Authorization header when making requests to protected resources: 
Authorization: Bearer <api_key>
If you need to authenticate via HTTP Basic Auth, use -u {{token}}: instead of -H "Authorization: Bearer {{token}}". All API requests must be made over HTTPS. Calls made over plain HTTP will fail. API requests without authentication will also fail. 
curl 'https://api.edgee.ai/v1/chat/completions' \
-H 'Authorization: Bearer <token>' \
-H 'Content-Type: application/json' \
-d '{
  "model": "openai/gpt-5.2",
  "messages": [{"role": "user", "content": "Hello"}]
}'