OpenAI compatibility

The Cura API speaks the OpenAI chat-completions dialect. Existing SDK code, agent frameworks, and gateways that accept a custom base_url work by pointing them at inference.actava.ai.

Cura 1T is a research model, not a medical service, and not a substitute for a clinician. Benchmark scores do not establish safety for unsupervised clinical use.

The two-line migration

Diff
  from openai import OpenAI   client = OpenAI(-     api_key=os.environ["OPENAI_API_KEY"],+     api_key=os.environ["ACTAVA_API_KEY"],+     base_url="https://inference.actava.ai/v1",  )   response = client.chat.completions.create(-     model="gpt-4o",+     model="actava/cura-soar",      messages=[...],  )

What's supported

  • /v1/chat/completions — messages (text + image parts), temperature, max_tokens, stream, tools / tool_choice, response_format
  • /v1/models — model listing
  • Standard usage accounting, including prompt_tokens_details.cached_tokens

Differences to know

  • Two endpoints only. Files, batches, embeddings, images, and assistants routes are not served — requests to them return 404.
  • One model id. actava/cura-soar; any other value 404s. See model list.
  • Temperature default is 1.0 — also the setting used for all published benchmark results; there is no reason to lower it for clinical reasoning.
  • Legacy functions/function_call still works, but answers in the modern shape — requests using the deprecated fields are accepted, and the response carries tool_calls (not function_call). Write new code against tools / tool_calls (the OpenAI SDK has defaulted to it since v1).

Framework configuration

Any framework with OpenAI-compatible provider settings works the same way: set the base URL to https://inference.actava.ai/v1, the API key to your actAVA key, and the model to actava/cura-soar.

← BenchmarkingCodex →