Absolute neutrophil count calculator
Absolute neutrophil count is the clinical number clinicians watch when chemotherapy, infection risk, or febrile neutropenia is on the table.
Run — free
Laboratories report a white blood cell count and a differential that lists segmented neutrophils and often band forms as percentages; the absolute count is not always printed next to every line. This capability multiplies the white cell count by the combined neutrophil and band percentages and returns both the conventional ×10³/µL figure and the cells-per-microlitre absolute. There is no fitness-tracker guesswork, no third-party lab API and no hidden activity multipliers—only the standard ANC formula on three scalars. The same deterministic math runs free in the browser widget and on the paid API path, so interactive checks match production responses byte for byte.
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 it cost?
$0.002 per successful API request. The same calculation runs free in your browser on this page.
Which inputs does the formula expect?
WBC in ×10³/µL (positive), neutrophil_percent from 0 to 100, and optional band_percent from 0 to 100 (defaults to 0). Their sum must not exceed 100.
Is this a diagnosis of neutropenia?
No. This returns the absolute neutrophil count arithmetic only. Clinical interpretation and thresholds remain with the care team.
Why was my request rejected?
WBC must be a positive number. Neutrophil and band percentages must be finite and between 0 and 100. Missing required fields return invalid_input and are not charged.
What if my lab already reports absolute neutrophils?
You can still recompute from WBC and percentages to verify the printed absolute, or skip this tool when the lab already provides ANC in cells/µL.
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
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/absolute-neutrophil \
-H "Authorization: Bearer $KIT_KEY" \
-H "Content-Type: application/json" \
-d '{"wbc":7.5,"neutrophil_percent":55}'const res = await fetch("https://api.kit.forhosting.com/health/absolute-neutrophil", {
method: "POST",
headers: {
"Authorization": `Bearer ${process.env.KIT_KEY}`,
"Content-Type": "application/json"
},
body: JSON.stringify({
"wbc": 7.5,
"neutrophil_percent": 55
})
});
const { task_id } = await res.json();import os, requests
res = requests.post(
"https://api.kit.forhosting.com/health/absolute-neutrophil",
headers={"Authorization": f"Bearer {os.environ['KIT_KEY']}"},
json={
"wbc": 7.5,
"neutrophil_percent": 55
},
)
task_id = res.json()["task_id"]<?php
$res = file_get_contents("https://api.kit.forhosting.com/health/absolute-neutrophil", false, stream_context_create([
"http" => [
"method" => "POST",
"header" => "Authorization: Bearer " . getenv("KIT_KEY") . "\r\nContent-Type: application/json",
"content" => '{"wbc":7.5,"neutrophil_percent":55}',
],
]));
$task = json_decode($res, true);body := bytes.NewBufferString(`{"wbc":7.5,"neutrophil_percent":55}`)
req, _ := http.NewRequest("POST", "https://api.kit.forhosting.com/health/absolute-neutrophil", body)
req.Header.Set("Authorization", "Bearer "+os.Getenv("KIT_KEY"))
req.Header.Set("Content-Type", "application/json")
res, _ := http.DefaultClient.Do(req)Example request
{
"wbc": 7.5,
"neutrophil_percent": 55
}Example response
{
"task_id": "tsk_a1b2c3d4e5f6a1b2c3d4e5f6",
"type": "health.absolute_neutrophil",
"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
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. |