About
The full read of the head CT study: the non-contrast brain series is analysed and the result contains all sections the study supports.
Endpoint ct/head/interpret · version 1.0.0 · $0.08 per request · the bare id ct/head is an alias.
1. Calling the API#
Set up your API key#
Create a key in Settings → API Keys and set it as MEDRUN_KEY in your runtime.
export MEDRUN_KEY="YOUR_API_KEY"Submit a request#
Every call is asynchronous: submitting returns a request with its id and status, and you follow it until the result is ready.
response=$(curl --request POST \
--url https://api.medrun.ai/v1/run/ct/head/interpret \
--header "Authorization: Bearer $MEDRUN_KEY" \
--header "Content-Type: application/json" \
--data '{
"input": {
"files": [
"file_01K7CTHEAD0000000000000000"
],
"options": {
"report": false
}
}
}')
REQUEST_ID=$(echo "$response" | jq -r .id)Request status
Stream progress#
Stages stream as server-sent events (received, queued, preprocessing, inference, report, completed). Critical findings are flagged first, before the full result.
curl --no-buffer \
--url https://api.medrun.ai/v1/requests/$REQUEST_ID/events \
--header "Authorization: Bearer $MEDRUN_KEY" \
--header "Accept: text/event-stream"2. Authentication#
The API uses API keys. Send Authorization: Bearer $MEDRUN_KEY with every call. Test keys (mr_test_…) run against the mock backend for free.
API key#
Protect your API key
3. Queue#
Long-running requests
Fetch request status#
Statuses run queued → preparing → running and end in succeeded, failed, canceled, rejected or expired.
curl --request GET \
--url https://api.medrun.ai/v1/requests/$REQUEST_ID \
--header "Authorization: Bearer $MEDRUN_KEY"Get the result#
When the request has succeeded, output holds the result envelope. See the result format.
curl --request GET \
--url https://api.medrun.ai/v1/requests/$REQUEST_ID \
--header "Authorization: Bearer $MEDRUN_KEY" | jq .output4. Files#
files is a flat list: DICOM files, folders, CD exports (DICOMDIR) and zip/tar archives. The platform groups them into series and runs.
Uploading files#
# 1. Create the upload (one PUT up to 100 MB; larger files get multipart part URLs)
upload=$(curl --request POST --url https://api.medrun.ai/v1/uploads \
--header "Authorization: Bearer $MEDRUN_KEY" --header "Content-Type: application/json" \
--data '{"filename": "study.zip", "bytes": 214000000, "media_type": "application/zip"}')
# 2. PUT the bytes to upload.url (with upload.headers)
curl --request PUT --upload-file study.zip "$(echo "$upload" | jq -r .upload.url)"
# 3. Complete it, then pass file.id in input.files
curl --request POST --url "$(echo "$upload" | jq -r .complete_url)" --header "Authorization: Bearer $MEDRUN_KEY"
FILE_ID=$(echo "$upload" | jq -r .file.id)Hosted files (URL)#
You can also pass https URLs, for example signed S3 or GCS links. MedRun fetches them when the request starts.
5. Webhooks#
Add a webhook to the submit body. MedRun POSTs the request object, signed with Standard Webhooks headers, when the request ends. Configure secrets and see deliveries in Settings → Webhooks.
{
"input": {
"files": [
"file_…"
]
},
"webhook": {
"url": "https://example.org/medrun/webhook",
"events": [
"request.succeeded",
"request.failed"
]
}
}6. Schema#
Input#
- fileslist<string>* required
The head CT study: DICOM files, a folder, a CD export or a zip (all series are fine). `file_…` ids from /v1/uploads or https URLs.
- clinical_contextobject
Optional. Used for guidance only; never names, IDs or dates.
- age_yearsinteger
Range:
0 … 130 - sexenum
Possible values:
female, male, other, unknown - indicationstring
For example "head trauma, on anticoagulation" or "sudden headache".
- optionsobject
- reportbooleanadd-on
Adds a draft head CT report written from the structured result (English). +$0.02 per run.
Default value:
false - report_languageenum
Default value:
"en"Possible values:
en - returnlist<enum>
JSON is always returned. DICOM objects reference your original UIDs.
Default value:
["json","dicom-sr","dicom-seg"]Possible values:
json, dicom-sr, dicom-seg
Example input:
{
"files": [
"file_01K7CTHEAD0000000000000000"
],
"options": {
"report": false
}
}Output#
The output is the MedRun result envelope: sections[] with a status per section, then findings, measurements, scores, classifications, guidance, the optional report and artifacts (DICOM SR/SEG, overlays, PDF, FHIR).
triageCritical-finding triage: Worklist priority from the hemorrhage read (critical when a hemorrhage is present, urgent when it cannot be excluded, routine otherwise).hemorrhageIntracranial hemorrhage: Acute intracranial hemorrhage present, not excluded or absent; each compartment (epidural, subdural, subarachnoid, intraparenchymal, intraventricular) stated; present bleeds outlined in 3D with side, volume, subdural thickness, the ABC/2 cross-check and the ICH score imaging inputs.midline-shiftMidline shift: Septum pellucidum deviation from the ideal midline in mm, with the > 5 mm flag and direction.ventriclesVentricles and hydrocephalus: Ventricle volumes, Evans index and temporal-horn dilatation.fracturesSkull and facial fractures: Vault, skull-base and facial fractures, depressed fracture and pneumocephalus on the bone reconstruction.aspectsASPECTS: Early ischaemic change per ASPECTS region and side in a stroke study without hemorrhage.lvoLarge-vessel occlusion: Occlusion site and side on a head and neck CTA.aneurysmIntracranial aneurysm: Aneurysm detection, location and maximal diameter on CTA.perfusionCT perfusion: CBF, CBV, MTT, Tmax maps with core and hypoperfusion volumes and the mismatch ratio.segment-vesselsCircle of Willis segmentation: Multiclass Circle of Willis segmentation with a centreline graph.compareComparison with prior: Hematoma expansion and new bleeds against a prior head CT.reportDraft report: Opt-in draft report (findings, impression, limitations) written from the structured result; every number is validated against it.
OpenAPI document: https://api.medrun.ai/v1/models/ct/head/interpret/openapi.json