Introduction
The main concepts behind the Cura API, in five minutes.
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 model
Cura 1T (API id actava/cura-soar) is actAVA's healthcare-specialized model — a one-trillion-parameter fine-tune of Kimi-K2.6 trained through recursive self-improvement. It handles patient communication, clinical reasoning over text and images, and agentic EHR workflows. It accepts text and images and generates text, with a 256K context window.
Endpoints
| Endpoint | Purpose |
|---|---|
| GET /v1/models | List the models your key can access |
| POST /v1/chat/completions | Generate responses — including streaming, vision, and tool calls |
Authentication
Every request carries Authorization: Bearer $ACTAVA_API_KEY. Keys are issued by actAVA — join the waitlist for access. Keep keys in environment variables or a secret manager; never commit them.
Tokens
Usage is metered per token: input and output are counted separately, and every response reports exact counts in usage — including how many prompt tokens were served from cache. Repeated prompt prefixes are cached automatically — Prompt caching explains how to benefit from it.
Sampling
Cura 1T is evaluated at temperature 1.0 — the setting all published benchmark numbers use. We recommend it as your default; lower it only if your application requires highly deterministic phrasing.
Research preview
Cura 1T is a research model. Build with clinician oversight for anything patient-facing, and design workflows so a human validates clinical decisions. Rate limits are set per key at issue time — contact us if you need more throughput.