ForHosting KIT · Developer Utilities

Stillbirth risk calculator

Stillbirth is the death of a fetus at or after twenty weeks of gestation, and families, midwives, educators, and product teams often need a transparent percentage that combines how far the pregnancy has already come, the mother's age, and a short list of well-studied clinical flags.

● BetaFree · in your browser

Run — free How it works & API

Use it from WebAPIEmailTelegramApp soon

This stillbirth risk calculator estimates remaining stillbirth probability from gestational age between twenty and forty-two weeks, maternal age, and selected optional risk factors—previous stillbirth, pre-existing diabetes, hypertension, smoking, obesity, fetal growth restriction, and multiple pregnancy—using a remaining-risk table, age relative risks, and odds-adjusted factor multipliers. Gestational age outside twenty to forty-two weeks fails with invalid_input and is not billed. The same deterministic module powers the free browser widget and the API path, so teaching keys, research coding, and prototypes never disagree on a given vignette. Treat the JSON percentage as an educational arithmetic aid, not a diagnosis or a substitute for licensed obstetric judgment about monitoring, timing of birth, or whether to continue a pregnancy.

How to use it

Enter your values in the form above. The tool checks them before calculating and shows the result on the same page.

Check your inputs

Use the labels and units shown next to each field. If something is missing or outside the allowed range, the page points to the field to fix.

Use it again or automate it

Use the browser tool for individual checks and the API when you need the same capability in an automated workflow.

What you can do with it

Get an answer now

Enter one set of values and see the result without building a spreadsheet or script.

Compare scenarios

Change one value at a time and rerun the calculation to understand what affects the result.

Automate repeated work

Use the API when the same calculation needs to run inside your product or workflow.

FAQ

What does this stillbirth risk calculator estimate?

It returns a remaining stillbirth probability as risk_pct (and the equivalent risk_per_1000) from gestational age between 20 and 42 weeks, maternal age, and optional flags for previous stillbirth, diabetes, hypertension, smoking, obesity, fetal growth restriction, and multiple pregnancy.

Why must gestational age be between 20 and 42 weeks?

Stillbirth is defined here from 20 completed weeks, and the remaining-risk table is tabulated through 42 weeks. Values outside that window fail with invalid_input naming gestational_age and are not billed.

Which risk factors does the calculator accept?

Seven optional flags, each a boolean or 0/1 value defaulting to false: previous_stillbirth, diabetes, hypertension, smoking, obesity, fetal_growth_restriction, and multiple_pregnancy. Relative risks follow Flenady 2011-style published multipliers.

How should I interpret low, moderate, high, and very high remaining risk?

Bands are remaining stillbirths per thousand ongoing pregnancies: low under 2, moderate 2–5, high 5–10, and very high 10 or more. They are educational strata, not a personal prognosis or a delivery-timing rule.

Can I use this percentage to time birth or stop monitoring?

No. This is an educational arithmetic aid, not medical advice. Surveillance, induction, and whether to continue a pregnancy need a licensed clinician and the rest of the clinical picture this calculator does not collect.

What does the stillbirth risk calculator cost?

The browser widget runs free and locally. The same computation via the API is billed at $0.002 per successful request from prepaid KIT balance; invalid_input failures are not charged.

For developers — API access

Everything on this page is available programmatically. This section is for teams who want to wire it into their own systems; everyone else can just use the tool above.

API endpoint

POSThttps://api.kit.forhosting.com/health/stillbirth-risk

Prefer to automate it? One authenticated POST creates the task; the result comes back by webhook or a signed link. The same capability also runs here on the web, by email and from Telegram — and soon from our app too.

Call it from your stack

curl -X POST https://api.kit.forhosting.com/health/stillbirth-risk \
  -H "Authorization: Bearer $KIT_KEY" \
  -H "Content-Type: application/json" \
  -d '{"items":["valor-1","valor-2"]}'

const res = await fetch("https://api.kit.forhosting.com/health/stillbirth-risk", {
  method: "POST",
  headers: {
    "Authorization": `Bearer ${process.env.KIT_KEY}`,
    "Content-Type": "application/json"
  },
  body: JSON.stringify({
    "items": [
      "valor-1",
      "valor-2"
    ]
  })
});
const { task_id } = await res.json();

import os, requests

res = requests.post(
    "https://api.kit.forhosting.com/health/stillbirth-risk",
    headers={"Authorization": f"Bearer {os.environ['KIT_KEY']}"},
    json={
    "items": [
        "valor-1",
        "valor-2"
    ]
},
)
task_id = res.json()["task_id"]

<?php
$res = file_get_contents("https://api.kit.forhosting.com/health/stillbirth-risk", false, stream_context_create([
  "http" => [
    "method"  => "POST",
    "header"  => "Authorization: Bearer " . getenv("KIT_KEY") . "\r\nContent-Type: application/json",
    "content" => '{"items":["valor-1","valor-2"]}',
  ],
]));
$task = json_decode($res, true);

body := bytes.NewBufferString(`{"items":["valor-1","valor-2"]}`)
req, _ := http.NewRequest("POST", "https://api.kit.forhosting.com/health/stillbirth-risk", body)
req.Header.Set("Authorization", "Bearer "+os.Getenv("KIT_KEY"))
req.Header.Set("Content-Type", "application/json")
res, _ := http.DefaultClient.Do(req)

Example request

{
  "items": [
    "valor-1",
    "valor-2"
  ]
}

Example response

{
  "task_id": "tsk_a1b2c3d4e5f6a1b2c3d4e5f6",
  "type": "health.stillbirth_risk",
  "status": "queued",
  "_links": {
    "result": "/tasks/tsk_…/result"
  }
}

The API is asynchronous: the call returns a task_id immediately and the result arrives by webhook. Polling is capped at 1 req/s per task.

Pricing

Per request$0.002

Published price — no tokens, no invented credits. A failed task is never charged.

Errors

HTTP	Code	Meaning
`401`	`unauthorized`	Missing or invalid API key.
`402`	`insufficient_balance`	Your balance doesn't cover the task price.
`404`	`unknown_type`	That task type doesn't exist.
`429`	`rate_limited`	Too many requests. Use the webhook instead of polling.

Read the full KIT documentation →