# Killip class after myocardial infarction (1967)

Killip

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

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

## What it computes

Return the Killip and Kimball 1967 myocardial-infarction heart-failure class 1-4 from a caller-assigned integer, with the published class description and 1967 CCU hospital mortality.

## When to use

When an agent needs the 1967 Killip class and must not invent GRACE scores, modified Killip, or contemporary-registry mortality.

## When not to use

- Not a medical device and not a diagnosis of heart failure or shock. magent does not examine the patient.
- The caller assigns Killip class 1-4. magent does not auscultate, measure blood pressure, or inspect the chart.
- Hospital mortality percentages are the 1967 CCU series (250 patients) only. They are not GRACE, GUSTO, or contemporary registry rates.

## Formula

```
Killip class 1-4 as assigned by the caller; 1967 CCU hospital mortality 6/17/38/81 percent (Killip and Kimball 1967)
```

## Citation

[Treatment of myocardial infarction in a coronary care unit. A two year experience with 250 patients](https://doi.org/10.1016/0002-9149(67)90023-9)
Killip T 3rd, Kimball JT
Am J Cardiol. 1967;20(4):457-464
DOI: [10.1016/0002-9149(67)90023-9](https://doi.org/10.1016/0002-9149(67)90023-9)

## Worked example

### Class 1 no heart failure

Given: `killip_class=1`

1. killip_class 1 → no heart failure; score 1; max 4; 1967 CCU mortality 6%


## Also searched as

- Killip class
- Killip classification
- Killip-Kimball
- Killip Kimball class
- MI heart failure class
- Killip 1967
- coronary care unit class
- Killip class AMI

## Parameters

- `killip_class` (integer, required): Killip and Kimball 1967 class 1-4 as assigned by the caller (1 no heart failure; 2 heart failure with S3 and basilar rales; 3 pulmonary edema; 4 cardiogenic shock). magent does not examine the patient.

## 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/killip`
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": [
    {
      "killip_class": "1"
    },
    {
      "killip_class": "1"
    }
  ]
}
```

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

Example 200:

```json
{
  "count": 2,
  "path": "/api/calc/killip",
  "items": [
    {
      "description": "No heart failure",
      "components": [
        {
          "factor": "killip_class",
          "points": 1,
          "present": true
        }
      ],
      "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": "Killip T 3rd, Kimball JT",
        "doi": "10.1016/0002-9149(67)90023-9",
        "id": "killip-1967",
        "pmid": "6059183",
        "source": "Am J Cardiol. 1967;20(4):457-464",
        "title": "Treatment of myocardial infarction in a coronary care unit. A two year experience with 250 patients"
      },
      "formula": "killip",
      "formula_expression": "Killip class 1-4 as assigned by the caller; 1967 CCU hospital mortality 6/17/38/81 percent (Killip and Kimball 1967)",
      "max_score": 4,
      "score": 1,
      "hospital_mortality_percent": 6,
      "killip_class": 1
    },
    {
      "description": "No heart failure",
      "components": [
        {
          "factor": "killip_class",
          "points": 1,
          "present": true
        }
      ],
      "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": "Killip T 3rd, Kimball JT",
        "doi": "10.1016/0002-9149(67)90023-9",
        "id": "killip-1967",
        "pmid": "6059183",
        "source": "Am J Cardiol. 1967;20(4):457-464",
        "title": "Treatment of myocardial infarction in a coronary care unit. A two year experience with 250 patients"
      },
      "formula": "killip",
      "formula_expression": "Killip class 1-4 as assigned by the caller; 1967 CCU hospital mortality 6/17/38/81 percent (Killip and Kimball 1967)",
      "max_score": 4,
      "score": 1,
      "hospital_mortality_percent": 6,
      "killip_class": 1
    }
  ]
}
```

## Response fields

- `formula` (string): killip
- `formula_expression` (string): Published class rule
- `killip_class` (integer): Caller-assigned class 1-4
- `score` (integer): Same as killip_class
- `max_score` (integer): 4
- `description` (string): 1967 wording for that class
- `hospital_mortality_percent` (integer): 1967 CCU hospital mortality for that class (6, 17, 38, or 81)
- `components` (array): Killip-class component
- `citation` (object): Killip and Kimball 1967
- `disclaimer` (string): Not a medical device

## Example JSON

Frozen fixture. Not a live lookup.

```json
{
  "description": "No heart failure",
  "components": [
    {
      "factor": "killip_class",
      "points": 1,
      "present": true
    }
  ],
  "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": "Killip T 3rd, Kimball JT",
    "doi": "10.1016/0002-9149(67)90023-9",
    "id": "killip-1967",
    "pmid": "6059183",
    "source": "Am J Cardiol. 1967;20(4):457-464",
    "title": "Treatment of myocardial infarction in a coronary care unit. A two year experience with 250 patients"
  },
  "formula": "killip",
  "formula_expression": "Killip class 1-4 as assigned by the caller; 1967 CCU hospital mortality 6/17/38/81 percent (Killip and Kimball 1967)",
  "max_score": 4,
  "score": 1,
  "hospital_mortality_percent": 6,
  "killip_class": 1
}
```

## Errors

- HTTP 400 `invalid_killip_class`: killip_class must be 1, 2, 3, or 4. 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

- [TIMI risk score for STEMI](https://magentlab.com/docs/timi-stemi) — Compute the TIMI risk score for ST-elevation myocardial infarction from published bedside factors at presentation.
- [HEART score](https://magentlab.com/docs/heart) — Compute the HEART score as age points plus caller-assigned history, ECG, risk factors, and troponin (each 0-2).

## 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.