Skip to main content

Documentation Index

Fetch the complete documentation index at: https://docs.inferoute.ai/docs/llms.txt

Use this file to discover all available pages before exploring further.

Inferoute authenticates every API request using Bearer token authentication. You include your API key in the Authorization header of each request — there are no cookies, sessions, or OAuth flows involved.

​
Header format

Authorization: Bearer YOUR_API_KEY
Replace YOUR_API_KEY with a key generated from your Inferoute dashboard. See API keys for instructions on creating and managing keys.

​
Code examples

curl https://api.inferoute.ai/v1/chat/completions \
  --request POST \
  --header "Authorization: Bearer YOUR_API_KEY" \
  --header "Content-Type: application/json" \
  --data '{
    "model": "openai/gpt-4o",
    "messages": [{"role": "user", "content": "Hello!"}]
  }'

​
Authentication errors

If your API key is missing, malformed, or invalid, the API returns a 401 Unauthorized response with the following JSON body: 
{
  "error": {
    "type": "authentication_error",
    "message": "Invalid API key provided. Check your key in the dashboard and ensure it is included as a Bearer token."
  }
}
Your API key grants full access to your Inferoute account. Never commit it to version control or expose it in client-side code. Use environment variables to inject keys at runtime.

​
Managing API keys

You can create, rotate, and revoke keys from the Inferoute dashboard under Settings → API keys. See API keys for a step-by-step walkthrough.