# Neutrophil-to-lymphocyte ratio

NLR

Status: LIVE
Price: $0.005 USDC
`GET /api/calc/nlr`
HTML: https://magentlab.com/docs/nlr
Markdown: https://magentlab.com/docs/nlr.md

Not a medical device. Not a diagnosis, dose, or listing recommendation.

## What it computes

Compute the Zahorec 2001 neutrophil-to-lymphocyte ratio from relative neutrophil and lymphocyte percents.

## When to use

When an agent needs the published ratio of relative neutrophil to lymphocyte counts and must not invent a sepsis cutoff or an oncology threshold.

## When not to use

- Not a diagnosis of sepsis. Zahorec 2001 is the ratio of relative neutrophil and lymphocyte counts (%).
- magent does not apply later oncology cutoffs that are not in that paper.

## Formula

```
nlr = neutrophil_percent / lymphocyte_percent
```

## Citation

[Ratio of neutrophil to lymphocyte counts--rapid and simple parameter of systemic inflammation and stress in critically ill](https://pubmed.ncbi.nlm.nih.gov/11723675)
Zahorec R
Bratisl Lek Listy. 2001;102(1):5-14
DOI: none

## Worked example

### Neutrophils 70%, lymphocytes 20%

Given: `lymphocyte_percent=20, neutrophil_percent=70`

1. nlr = 70 / 20 = 3.50 → 3.5


### Neutrophils 99%, lymphocytes 0.1%

Given: `lymphocyte_percent=0.1, neutrophil_percent=99`

1. nlr = 99 / 0.1 = 990.0


## Also searched as

- neutrophil lymphocyte ratio
- NLR
- neutrophil to lymphocyte
- Zahorec NLR
- relative neutrophil lymphocyte
- NL ratio

## Parameters

- `neutrophil_percent` (number, required): Relative neutrophil count as a percent of leukocytes (0.1-99).
- `lymphocyte_percent` (number, required): Relative lymphocyte count as a percent of leukocytes (0.1-99). Must be greater than 0.

## Bulk (POST)

POST the same path with a JSON items array. The first item is the GET unit; each additional item is $0.002. Invalid items return HTTP 400 before settlement.

Method: `POST /api/calc/nlr`
Max items: 25
Price: unit_amount + extra_item_amount * (n - 1) (unit 5000 atomic, extra 2000 atomic)
Status: PREVIEW

- 1 to 25 items. Each item uses the same keys as the GET query parameters.
- POST of 1 item costs the same as GET. Lists longer than 25: chunk into multiple POSTs. Extra items still execute; do not pad dummy rows.
- The first invalid item fails the whole request (index in the 400 JSON). You are not charged.
- HTTP 200 is {count, path, items}. Each items[i] is the GET 200 body for that row.
- Catalog misses (empty matches, found=false) stay paid 200s inside that slot.
- x402 resource URL is this path plus n and body_sha256. Browsers that prefer text/html get the same paywall as GET; Pay retries POST with the same items.

Example request:

```json
{
  "items": [
    {
      "lymphocyte_percent": "20",
      "neutrophil_percent": "70"
    },
    {
      "lymphocyte_percent": "20",
      "neutrophil_percent": "70"
    }
  ]
}
```

Human paywall (two-item fixture): https://api.magentlab.com/paywall/bulk/nlr

Example 200:

```json
{
  "count": 2,
  "path": "/api/calc/nlr",
  "items": [
    {
      "disclaimer": "Not a medical device. Deterministic published-formula or published-code output for autonomous agents. A licensed clinician remains responsible for patient care and billing submissions.",
      "citation": {
        "authors": "Zahorec R",
        "id": "zahorec-2001",
        "pmid": "11723675",
        "source": "Bratisl Lek Listy. 2001;102(1):5-14",
        "title": "Ratio of neutrophil to lymphocyte counts--rapid and simple parameter of systemic inflammation and stress in critically ill"
      },
      "formula": "nlr",
      "formula_expression": "nlr = neutrophil_percent / lymphocyte_percent",
      "neutrophil_percent": 70.0,
      "lymphocyte_percent": 20.0,
      "nlr": 3.5
    },
    {
      "disclaimer": "Not a medical device. Deterministic published-formula or published-code output for autonomous agents. A licensed clinician remains responsible for patient care and billing submissions.",
      "citation": {
        "authors": "Zahorec R",
        "id": "zahorec-2001",
        "pmid": "11723675",
        "source": "Bratisl Lek Listy. 2001;102(1):5-14",
        "title": "Ratio of neutrophil to lymphocyte counts--rapid and simple parameter of systemic inflammation and stress in critically ill"
      },
      "formula": "nlr",
      "formula_expression": "nlr = neutrophil_percent / lymphocyte_percent",
      "neutrophil_percent": 70.0,
      "lymphocyte_percent": 20.0,
      "nlr": 3.5
    }
  ]
}
```

## Response fields

- `formula` (string): nlr
- `formula_expression` (string): Exact expression used
- `neutrophil_percent` (number): Relative neutrophil percent used
- `lymphocyte_percent` (number): Relative lymphocyte percent used
- `nlr` (number): Neutrophil percent divided by lymphocyte percent, 2 decimals
- `citation` (object): Zahorec 2001 citation
- `disclaimer` (string): Not-a-device notice

## Example JSON

Frozen fixture. Not a live lookup.

```json
{
  "disclaimer": "Not a medical device. Deterministic published-formula or published-code output for autonomous agents. A licensed clinician remains responsible for patient care and billing submissions.",
  "citation": {
    "authors": "Zahorec R",
    "id": "zahorec-2001",
    "pmid": "11723675",
    "source": "Bratisl Lek Listy. 2001;102(1):5-14",
    "title": "Ratio of neutrophil to lymphocyte counts--rapid and simple parameter of systemic inflammation and stress in critically ill"
  },
  "formula": "nlr",
  "formula_expression": "nlr = neutrophil_percent / lymphocyte_percent",
  "neutrophil_percent": 70.0,
  "lymphocyte_percent": 20.0,
  "nlr": 3.5
}
```

## Errors

- HTTP 400 `invalid_neutrophil_percent`: neutrophil_percent must be a number from 0 to 100 Returned before settlement; you are not charged.
- HTTP 400 `invalid_lymphocyte_percent`: lymphocyte_percent must be a number from 0.1 to 99. Returned before settlement; you are not charged.
- HTTP 400 `invalid_nlr_inputs`: neutrophil_percent and lymphocyte_percent are required; lymphocyte_percent must be greater than 0. Returned before settlement; you are not charged.
- HTTP 400 `invalid_items`: POST body must be a JSON object with only an items array Returned before settlement; you are not charged.
- HTTP 400 `invalid_item_count`: items must be an array of 1 to 25 objects Returned before settlement; you are not charged.
- HTTP 400 `invalid_item`: each items entry must be a JSON object Returned before settlement; you are not charged.

Shared HTTP 402 and 503: https://magentlab.com/docs/payments

## Related tools

- [ANC](https://magentlab.com/docs/anc) — Compute absolute neutrophil count from WBC and neutrophil plus band percents, plus a Bodey 1966 granulocyte band.
- [SIRS](https://magentlab.com/docs/sirs) — Compute the Bone 1992 ACCP/SCCM SIRS criteria from temperature, heart rate, respiratory rate, and WBC, with optional PaCO2 and band percent.

## Payment

Unpaid requests return HTTP 402 even if query parameters or POST items are missing or invalid, so CDP and agents can index the path. After a PAYMENT-SIGNATURE, invalid params return HTTP 400 JSON before settlement. magent does not charge. Fix the params, then request a new 402 quote for that complete URL. Catalog misses (empty matches, found=false) are valid paid 200s.

- GET the tool with Accept: application/json (do not send Accept: text/html unless you want the human paywall).
- HTTP 402 means you have not paid. Decode the base64 PAYMENT-REQUIRED header. HTTP 503 is not a new quote.
- Sign accepts[0] (exact, EIP-3009) with validBefore = now + maxTimeoutSeconds (600 seconds), or accepts[1] (batch-settlement deposit/voucher) on product GET. Ping and POST {items} stay exact. Magent retries transient facilitator 429/5xx before answering.
- Retry the same URL with PAYMENT-SIGNATURE (base64 JSON echoing accepted, payload, and extensions when present).
- Success is HTTP 200 JSON plus PAYMENT-RESPONSE. exact settles before the tool. batch-settlement verifies (and deposit-settles) before the tool and commits the charge after HTTP 2xx. HTTP 503: retry the same PAYMENT-SIGNATURE. Mint a new exact nonce only after a new HTTP 402.

- offered `exact` on eip155:8453: Fixed-price USDC on Base. The buyer authorizes the advertised amount (EIP-3009). magent settles before the tool runs (paymentFlow upfront). extra.assetTransferMethod=eip3009 extra.paymentFlow=upfront.
- offered `batch-settlement` on eip155:8453: Payment-channel vouchers claimed later in batches. Exact stays accepts[0]. Same-path POST {items} is still exact. extra.assetTransferMethod=eip3009 extra.paymentFlow=authorization.

- not offered `upto`: Not offered. Usage-based: buyer authorizes a ceiling, seller settles the actual amount after work. Reserved for a future metered tool. Not for current calculators or code search.

Same-path POST {items} is still scheme exact: one EIP-3009 authorization for GET unit plus $0.002 per extra item. That is not x402 batch-settlement (payment channels / vouchers).

Shared HTTP 402 and 503 table: https://magentlab.com/docs/payments

Stdio MCP (one process per host): https://magentlab.com/docs/mcp

## Guarantees

- HTTP 402 is unpaid, including a missing query. After PAYMENT-SIGNATURE, invalid parameters return HTTP 400 before settlement. You are not charged.
- exact: settlement finishes before the tool (paymentFlow upfront). batch-settlement: verify/deposit before the tool; chargedCumulativeAmount commits after HTTP 2xx. Uncertain or failed settlement fails closed (HTTP 503). Retry the same PAYMENT-SIGNATURE.
- HTTP 402 is unpaid only. Do not sign a second authorization because of a 503.
- Execution is timeout-bounded and concurrency-capped.
- Calculator inputs are stored encrypted for allowlisted operators (Magent Console). They are not in public logs, SSH lookups, catalog, or rollups. Request logs store path without query.
