Openai Compatible Apps

--- title: "OpenAI-Compatible Apps" description: "Point OpenAI- and Anthropic-compatible SDKs and applications at Aurora's /v1 endpoints." icon: "plug" ---

Overview

Most applications that support an OpenAI- or Anthropic-compatible base URL can use Aurora by changing only the base URL, API key, and model name.

Aurora exposes:

• /v1/chat/completions
• /v1/responses
• /v1/embeddings
• /v1/rerank
• /v1/files for providers that support files
• /v1/batches for providers that support batches
• /v1/models

Base URL

Use your Aurora origin plus /v1 as the SDK base URL when the SDK expects a versioned OpenAI base path:

http://your-aurora-host/v1

Use a managed API key or master key as the OpenAI API key value.

Chat example

curl http://your-aurora-host/v1/chat/completions \
  -H "Authorization: Bearer $AURORA_API_KEY" \
  -H "Content-Type: application/json" \
  -H "X-Aurora-User-Path: /team/alpha" \
  -d '{
    "model": "regular",
    "messages": [{"role": "user", "content": "Reply with ok"}]
  }'

Embeddings example

curl http://your-aurora-host/v1/embeddings \
  -H "Authorization: Bearer $AURORA_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "model": "text-embedding-3-small",
    "input": ["Hello from Aurora"]
  }'

Rerank example

curl http://your-aurora-host/v1/rerank \
  -H "Authorization: Bearer $AURORA_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "model": "rerank-model",
    "query": "best gateway feature",
    "documents": ["model aliases", "unrelated text"],
    "top_n": 1,
    "return_documents": true
  }'

Use aliases

Prefer aliases such as regular, reasoning, or embedding-default in client configuration. Then operators can move aliases between providers without application redeploys.