# TIMI UA/NSTEMI Status: LIVE Price: $0.005 USDC `GET /api/calc/timi_ua_nstemi` HTML: https://magentlab.com/docs/timi-ua-nstemi Markdown: https://magentlab.com/docs/timi-ua-nstemi.md Not a medical device. Not a diagnosis, dose, or listing recommendation. ## What it computes Compute the TIMI risk score for unstable angina / NSTEMI from age and six caller-assigned flags. ## When to use When an agent needs the published TIMI UA/NSTEMI total and must not invent points from a chart narrative. ## When not to use - Not an invasive-strategy protocol and not a diagnosis. - cad_risk_factors_ge_3 is a caller-assigned flag. magent does not expand smoking, hypertension, family history, diabetes, or cholesterol. - st_deviation is a caller-assigned flag. magent does not read ECGs. ## Formula ``` TIMI UA/NSTEMI = age_ge_65 + cad_risk_factors_ge_3 + known_cad + aspirin_last_7d + severe_angina + st_deviation + elevated_markers; each 1 if present; max 7 ``` ## Citation The TIMI risk score for unstable angina/non–ST elevation MI: A method for prognostication and therapeutic decision making Antman EM, Cohen M, Bernink PJLM, et al. JAMA. 2000;284(7):835-842 DOI: [10.1001/jama.284.7.835](https://doi.org/10.1001/jama.284.7.835) ## Worked example ### Age 50, all flags false Given: `age=50, aspirin_last_7d=false, cad_risk_factors_ge_3=false, elevated_markers=false, known_cad=false, severe_angina=false, st_deviation=false` 1. Age 50 < 65 → 0; six flags absent → 0 each 2. Score = 0 (max 7) ## Parameters - `age` (integer, required): Age in years (18-120). Age ≥65 scores 1. - `cad_risk_factors_ge_3` (boolean, required): ≥3 CAD risk factors as assigned by the caller. true or false. magent does not expand smoking, hypertension, family history, diabetes, or cholesterol. - `known_cad` (boolean, required): Known CAD (stenosis ≥50%). true or false. - `aspirin_last_7d` (boolean, required): Aspirin use in the last 7 days. true or false. - `severe_angina` (boolean, required): Severe angina (≥2 episodes in 24 hours). true or false. - `st_deviation` (boolean, required): ST deviation ≥0.5 mm as assigned by the caller. true or false. magent does not read ECGs. - `elevated_markers` (boolean, required): Elevated cardiac markers as assigned by the caller. true or false. ## Bulk (POST) POST the same path with a JSON items array. Price is n times the GET unit. Invalid items return HTTP 400 before settlement. Method: `POST /api/calc/timi_ua_nstemi` Max items: 25 Price: unit_amount * n (unit 5000 atomic) Status: PREVIEW - 1 to 25 items. Each item uses the same keys as the GET query parameters. - 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": [ { "age": "50", "aspirin_last_7d": "false", "cad_risk_factors_ge_3": "false", "elevated_markers": "false", "known_cad": "false", "severe_angina": "false", "st_deviation": "false" }, { "age": "50", "aspirin_last_7d": "false", "cad_risk_factors_ge_3": "false", "elevated_markers": "false", "known_cad": "false", "severe_angina": "false", "st_deviation": "false" } ] } ``` Human paywall (two-item fixture): https://api.magentlab.com/paywall/bulk/timi-ua-nstemi Example 200: ```json { "count": 2, "path": "/api/calc/timi_ua_nstemi", "items": [ { "components": [ { "value": 50, "factor": "age_ge_65", "points": 0, "present": false }, { "factor": "cad_risk_factors_ge_3", "points": 0, "present": false }, { "factor": "known_cad", "points": 0, "present": false }, { "factor": "aspirin_last_7d", "points": 0, "present": false }, { "factor": "severe_angina", "points": 0, "present": false }, { "factor": "st_deviation", "points": 0, "present": false }, { "factor": "elevated_markers", "points": 0, "present": false } ], "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": "Antman EM, Cohen M, Bernink PJLM, et al.", "doi": "10.1001/jama.284.7.835", "id": "antman-2000", "source": "JAMA. 2000;284(7):835-842", "title": "The TIMI risk score for unstable angina/non–ST elevation MI: A method for prognostication and therapeutic decision making" }, "formula": "timi_ua_nstemi", "formula_expression": "TIMI UA/NSTEMI = age_ge_65 + cad_risk_factors_ge_3 + known_cad + aspirin_last_7d + severe_angina + st_deviation + elevated_markers; each 1 if present; max 7", "age_years": 50, "max_score": 7, "score": 0 }, { "components": [ { "value": 50, "factor": "age_ge_65", "points": 0, "present": false }, { "factor": "cad_risk_factors_ge_3", "points": 0, "present": false }, { "factor": "known_cad", "points": 0, "present": false }, { "factor": "aspirin_last_7d", "points": 0, "present": false }, { "factor": "severe_angina", "points": 0, "present": false }, { "factor": "st_deviation", "points": 0, "present": false }, { "factor": "elevated_markers", "points": 0, "present": false } ], "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": "Antman EM, Cohen M, Bernink PJLM, et al.", "doi": "10.1001/jama.284.7.835", "id": "antman-2000", "source": "JAMA. 2000;284(7):835-842", "title": "The TIMI risk score for unstable angina/non–ST elevation MI: A method for prognostication and therapeutic decision making" }, "formula": "timi_ua_nstemi", "formula_expression": "TIMI UA/NSTEMI = age_ge_65 + cad_risk_factors_ge_3 + known_cad + aspirin_last_7d + severe_angina + st_deviation + elevated_markers; each 1 if present; max 7", "age_years": 50, "max_score": 7, "score": 0 } ] } ``` ## Response fields - `formula` (string): timi_ua_nstemi - `formula_expression` (string): Exact expression used - `score` (integer): Total points 0-7 - `max_score` (integer): Always 7 - `age_years` (integer): Age used for the ≥65 criterion - `components` (array): Per-factor points - `citation` (object): JAMA 2000 citation - `disclaimer` (string): Not-a-device notice ## Example JSON Frozen fixture. Not a live lookup. ```json { "components": [ { "value": 50, "factor": "age_ge_65", "points": 0, "present": false }, { "factor": "cad_risk_factors_ge_3", "points": 0, "present": false }, { "factor": "known_cad", "points": 0, "present": false }, { "factor": "aspirin_last_7d", "points": 0, "present": false }, { "factor": "severe_angina", "points": 0, "present": false }, { "factor": "st_deviation", "points": 0, "present": false }, { "factor": "elevated_markers", "points": 0, "present": false } ], "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": "Antman EM, Cohen M, Bernink PJLM, et al.", "doi": "10.1001/jama.284.7.835", "id": "antman-2000", "source": "JAMA. 2000;284(7):835-842", "title": "The TIMI risk score for unstable angina/non–ST elevation MI: A method for prognostication and therapeutic decision making" }, "formula": "timi_ua_nstemi", "formula_expression": "TIMI UA/NSTEMI = age_ge_65 + cad_risk_factors_ge_3 + known_cad + aspirin_last_7d + severe_angina + st_deviation + elevated_markers; each 1 if present; max 7", "age_years": 50, "max_score": 7, "score": 0 } ``` ## Errors - HTTP 400 `invalid_age`: age must be an integer from 18 to 120 Returned before settlement; you are not charged. - HTTP 400 `invalid_flag`: boolean clinical flags must be true or false 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. - HTTP 402 `payment_required`: Missing or invalid PAYMENT-SIGNATURE; decode the PAYMENT-REQUIRED header - HTTP 409 `payment_in_progress`: The same authorization nonce is already being settled; retry shortly - HTTP 429 `rate_limited`: Too many requests from this client - HTTP 503 `settlement_uncertain`: Settlement is unconfirmed; retry with the same PAYMENT-SIGNATURE - HTTP 503 `settle_failed`: Settlement failed; retry with the same PAYMENT-SIGNATURE shortly - HTTP 503 `facilitator_unavailable`: Payment facilitator unavailable - HTTP 503 `facilitator_misconfigured`: Payment facilitator is not configured - HTTP 503 `facilitator_unauthorized`: Payment facilitator rejected credentials - HTTP 503 `ledger_unavailable`: Payment ledger unavailable - HTTP 503 `payment_unavailable`: Payment processing unavailable ## 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. ## Also searched as - TIMI UA/NSTEMI - TIMI risk score unstable angina - Antman TIMI score - NSTEMI TIMI - TIMI risk score for UA ## Payment Required query parameters must be present and valid. 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 EIP-3009 (scheme exact, assetTransferMethod eip3009) with validBefore = now + accepts[0].maxTimeoutSeconds (600 seconds). That window starts when you sign and must cover wallet confirmation plus CDP verify and settle. Magent retries transient facilitator 429/5xx before answering. Do not send upto or batch-settlement payloads; magent does not offer those schemes. - Retry the same URL with PAYMENT-SIGNATURE (base64 JSON echoing accepted, payload, and extensions when present). - Success is HTTP 200 JSON plus PAYMENT-RESPONSE. Settlement happens before the tool runs. HTTP 503 settlement_uncertain or settle_failed: retry the same PAYMENT-SIGNATURE. Mint a new 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. - 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. - not offered `batch-settlement`: Not offered. Payment-channel vouchers claimed later in batches. Not the same as POST {items} bulk (that is still exact). Same-path POST {items} is still scheme exact: one EIP-3009 authorization for n times the GET unit. That is not x402 batch-settlement (payment channels / vouchers). ## Guarantees - Invalid query parameters return HTTP 400 before settlement. You are not charged. - Settlement finishes before the tool executes (paymentFlow upfront). 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.