The AlphaEdge API is a REST API you can call from any programming language. No SDK installation is required; you can use HTTP requests directly.
Prerequisites
To use the AlphaEdge API, you need:
- An API key (get one from your dashboard)
- An HTTP client (curl, Postman, or your preferred programming language)
- An internet connection
API base URL
All requests must be sent to the following base URL:
https://api-endpoints.alphaedge-ai.com
Request format
Responses are JSON. For endpoints whose body is a JSON object (chat, completions, etc.), send at least:
Content-Type: application/json
X-API-Key: TA_CLE
For OCR and transcription (multipart/form-data: file plus optional fields), do not set Content-Type yourself—especially not application/json. Use curl -F, requests with files=, or fetch(FormData): the client sets multipart/form-data and the boundary automatically.
Test your connection
You can test your API connection with this simple request:
curl https://api-endpoints.alphaedge-ai.com/models
This request returns the list of all available models.
Headers & transparent behaviours
The gateway automatically adds several headers to every response. You don't need to configure anything client-side, but it's useful to know them:
X-Request-ID— unique request identifier (useful for support). If you send this header yourself, its value is preserved and echoed back.X-Process-Time-Ms— gateway-side processing time, in milliseconds.Retry-After— present only on 429 / 502 / 503 / 504 responses; indicates the recommended wait before retrying.Content-Encoding: gzip+Vary: Accept-Encoding— compression enabled on sufficiently large responses when the client sendsAccept-Encoding: gzip. Modern HTTP clients (curl, requests, fetch) handle decompression automatically.- Default security headers:
X-Content-Type-Options: nosniff,X-Frame-Options: DENY,Referrer-Policy: no-referrer,Cross-Origin-Resource-Policy: same-origin.
On sensitive endpoints (/account/*, /transcript), a Cache-Control: no-store is also present.