01
Generate
A familiar chat API
Use OpenAI SDKs, streaming responses, and the chat completion shape your team already knows.
Council API
Build clinical AI that can show its work.
An OpenAI-compatible API for grounded clinical answers, retrieval, and knowledge workflows—backed by 211 million curated medical vectors.
v1OpenAI compatible
211Mmedical vectors
$10starting credit
from openai import OpenAI
client = OpenAI(
base_url="https://developer.council.health/v1",
api_key="YOUR_API_KEY",
)
response = client.chat.completions.create(
model="google/gemma-4-26B-A4B-it",
messages=[{
"role": "user",
"content": "Summarize first-line hypertension treatment."
}],
extra_body={
"citations": {
"enabled": True,
"required": True,
"sources": ["public_kb"],
"top_k": 3,
}
},
)
print(response.choices[0].message.content)Example response200 OK · citations attached
{
"object": "chat.completion",
"choices": [{
"message": {
"role": "assistant",
"content": "Initial treatment commonly begins with ... [1][2]"
}
}],
"citations": [
{ "id": 1, "title": "Clinical guideline", "source_type": "public_kb" },
{ "id": 2, "title": "Evidence review", "source_type": "public_kb" }
]
}From prototype to production with the tools you already use.
OpenAI SDKsREST / JSONServer-sent eventsScoped API keys
The clinical API stack
One integration. More trustworthy clinical experiences.
Start with a familiar completion API, then add evidence retrieval and organization-specific knowledge without stitching together a separate stack.
02
Ground
Answers with traceable evidence
Request public, customer, or personal knowledge scopes and receive structured citation metadata with the answer.
03
Extend
Bring your own knowledge
Upload text, track ingestion, and search an account-scoped knowledge base through dedicated endpoints.
Core endpoints
GET /v1/modelsPOST /v1/chat/completionsPOST /v1/kb/searchPOST /v1/kb/documentsBuilt for healthcare
Put grounded intelligence inside the workflow.
Council gives product and engineering teams a practical foundation for clinical experiences where evidence and provenance matter.
Clinical copilots
Add evidence-aware assistance to clinician-facing workflows without rebuilding your application stack.
Patient education
Generate clear, contextual explanations grounded in sources your organization can inspect.
Medical knowledge search
Retrieve relevant passages from Council’s public knowledge base or from content you manage.
Research synthesis
Turn a question and a set of sources into a concise starting point with citations attached.
Operate with confidence
Developer velocity, with healthcare-grade boundaries.
The public API is separated from the private model runtime, and authorization follows the API key—not caller-provided identity fields.
Scoped, revocable keys
Control chat, search, document, and billing access independently for each API key.
Private model runtime
The underlying model host remains on private infrastructure and is never exposed directly.
Measured operations
Per-key rate limits, usage records, spend visibility, and request-level operational metadata.
Content-minimal logging
Raw prompts, completions, uploaded text, and retrieved chunks are not stored by the API service by default.
Simple API pricing
Pay for the intelligence your product uses.
Start with $10 in API credits. Use core chat when generation is enough, or add Council’s knowledge layer for evidence-backed responses.
Core chat
OpenAI-compatible completions
For clinical generation workflows that do not require retrieval.
$2input / 1M tokens
$10output / 1M tokens
- Standard chat completion shape
- Streaming with server-sent events
- Usage and spend monitoring
Grounded chat
With Council knowledge
Retrieval + structured citations
For experiences where answers need source context and provenance.
$5input / 1M tokens
$25output / 1M tokens
- Public and account-scoped sources
- Configurable citation requirements
- Structured citation metadata
Credits are enforced at the account level.Purchases are managed securely through the developer console.
Questions, answered
The essentials before your first request.
Is the Council API compatible with OpenAI SDKs?
Yes. Point an OpenAI-compatible client at https://developer.council.health/v1 and authenticate with a Council API key. Chat completions support both standard and streaming responses.
How do grounded responses work?
Add a citations object to a chat request and choose the knowledge scopes your key is allowed to use. Council retrieves relevant context and returns citation metadata alongside the completion. Set citations.required to true when retrieval must succeed.
Can I add my organization’s own knowledge?
Yes. Keys with document permissions can upload text, follow the ingestion job, and query customer-scoped or personal knowledge. The authenticated key determines the account boundary.
Where do I create keys and monitor usage?
The developer console at developer.council.health lets you create and revoke keys, review request volume and spend, purchase credits, and copy integration examples.
Start with one request
Build a clinical product that can point back to the evidence.
Create an account, generate a key, and make your first Council API call.
For clinical support workflows. Qualified professionals remain responsible for care decisions.