Developers

Keep your SDK. Change the base URL.

The OevuAI API is OpenAI-compatible: same request shape, same streaming events, same client libraries. Point it at https://oevuai.com/v1 and use Caelim models.

Quickstart

1 · curl

curl https://oevuai.com/v1/chat/completions \
  -H "Authorization: Bearer $OEVAI_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "model": "Caelim-2.1-Pro",
    "messages": [
      {"role": "user", "content": "Hello, who are you?"}
    ],
    "stream": true
  }'

2 · Python (openai SDK)

from openai import OpenAI

client = OpenAI(
    base_url="https://oevuai.com/v1",
    api_key=os.environ["OEVAI_API_KEY"],
)

resp = client.chat.completions.create(
    model="Caelim-2.1-Pro",
    messages=[{"role": "user",
               "content": "Hello"}],
    stream=True,
)

3 · List models

curl https://oevuai.com/v1/models \
  -H "Authorization: Bearer $OEVAI_API_KEY"

4 · Check balance

curl https://oevuai.com/v1/user/balance \
  -H "Authorization: Bearer $OEVAI_API_KEY"

Models

Available over the API.

Model IDNotes
caelim-2.1-turboLightweight fast tier — everyday Q&A, high concurrency, low latency.
caelim-2.1-proDeep-reasoning tier — complex tasks, long-form writing, deep analysis.
caelim-2.1-betaExperimental — 3.8M-token context in early access; lower stability.

Served live from the model registry — the chat product's registry reports all three 2.1 tiers as online today. The platform console (/platform) shows per-model pricing. Latency figures will be published with our evaluation runs; we don't quote numbers we haven't measured.

Authentication

Send your key as a bearer token. Keys are created and revocable in the platform console. Never ship a key in client-side code — use the embeddable widget for browser-side chat.

Rate limits

Requests are rate-limited per account; when you exceed the limit the API responds with a standard rate-limit error — back off and retry. Limits are shown in the platform console alongside usage.

Pricing

Free during the open beta. Per-million-token input/output pricing is published per model in the console so there are no surprises when billing starts.

Errors

Responses follow the OpenAI error shape: a JSON object with error.message and error.type. HTTP status codes are conventional (401 auth, 429 rate limit, 5xx server).

Embed

Chat widget for your pages.

If you want OevuAI chat on a page without writing API code, the embeddable widget binds to a device key you manage from the platform console.

<!-- Point the widget host at your embed URL from the console -->
<iframe src="https://oevuai.com/embed/YOUR_EMBED_KEY"
        style="width:100%;height:600px;border:0;border-radius:12px"
        title="OevuAI chat"></iframe>

Embed keys are issued per deployment so you can revoke one site without touching the others. Ask in the console or contact us for setup.