# FINDRISC Finnish diabetes risk score FINDRISC Status: LIVE Price: $0.005 USDC `GET /api/calc/findrisc` HTML: https://magentlab.com/docs/findrisc Markdown: https://magentlab.com/docs/findrisc.md Not a medical device. Not a diagnosis, dose, or listing recommendation. ## What it computes Sum the original Lindström 2003 seven-item Finnish diabetes risk score (FINDRISC, 0–20) and return at_risk when the total is ≥9. ## When to use When an agent needs the published 2003 FINDRISC point total and must not invent a type 2 diabetes diagnosis or a later family-history revision. ## When not to use - Not a medical device. magent does not diagnose type 2 diabetes or assay glucose. - Original Lindström 2003 seven-item score 0–20, cutoff ≥9. Not the later 0–26 / family-history / eight-item FINDRISC revision. No family-history field. - at_risk is score ≥9 from that paper, not a diabetes diagnosis and not a 10-year diabetes probability. - BMI 25.0 and 30.0 score in the middle band (1). Waist 94 and 102 cm (men) and 80 and 88 cm (women) score in the middle band (3). - BMI is caller-supplied kg/m^2. magent does not compute BMI from height and weight. ## Formula ``` FINDRISC = age + bmi + waist + bp_medication + history_high_glucose + inactivity + no_daily_vegetables; age <45 -> 0, 45-54 -> 2, 55-64 -> 3, >=65 -> 4; BMI <25 -> 0, 25-30 -> 1, >30 -> 3; waist men <94 -> 0, 94-102 -> 3, >102 -> 4; women <80 -> 0, 80-88 -> 3, >88 -> 4; bp_medication 2; history_high_glucose 5; activity_30min false -> 2; daily_vegetables false -> 1; max 20; at_risk iff score>=9 ``` ## Citation [The diabetes risk score: a practical tool to predict type 2 diabetes risk](https://doi.org/10.2337/diacare.26.3.725) Lindström J, Tuomilehto J Diabetes Care. 2003;26(3):725-731 DOI: [10.2337/diacare.26.3.725](https://doi.org/10.2337/diacare.26.3.725) ## Worked example ### All 0-point bands Given: `activity_30min=true, age=40, bmi_kg_m2=22, bp_medication=false, daily_vegetables=true, history_high_glucose=false, sex=male, waist_cm=80` 1. Age 40 <45 → 0; BMI 22 <25 → 0; male waist 80 <94 → 0 2. No BP medication → 0; no high-glucose history → 0; daily 30 min activity → 0; daily vegetables → 0 3. Score = 0 (published max 20); at_risk false ### Cutoff ≥9 (age ≥65 plus high-glucose history) Given: `activity_30min=true, age=65, bmi_kg_m2=22, bp_medication=false, daily_vegetables=true, history_high_glucose=true, sex=male, waist_cm=80` 1. Age 65 → 4; history_high_glucose true → 5; other items 0 2. Score = 9; at_risk true (cutoff ≥9). Not a diagnosis. ## Also searched as - FINDRISC - Finnish diabetes risk score - Lindström diabetes risk score - type 2 diabetes risk score - diabetes risk score 2003 - FINDRISC 2003 ## Parameters - `age` (integer, required): Age in years (18-120). Lindström 2003: <45 scores 0; 45-54 scores 2; 55-64 scores 3; ≥65 scores 4. Age 45 and 54 score 2; 55 and 64 score 3; 65 scores 4. - `bmi_kg_m2` (number, required): Body-mass index in kg/m^2 (10-80). Caller-supplied; magent does not compute BMI from height and weight. Lindström 2003: <25 scores 0; 25-30 scores 1; >30 scores 3. 25.0 and 30.0 score 1; 30.1 scores 3. - `sex` (string, required): female or male. Selects the Lindström 2003 waist bands. - `waist_cm` (number, required): Waist circumference in cm (40-200). Lindström 2003 men: <94 scores 0; 94-102 scores 3; >102 scores 4. Women: <80 scores 0; 80-88 scores 3; >88 scores 4. 94 and 102 (men) and 80 and 88 (women) score 3. - `bp_medication` (boolean, required): History of antihypertensive drug treatment (Lindström 2003). true scores 2; false scores 0. - `history_high_glucose` (boolean, required): History of high blood glucose (health examination, illness, or pregnancy) (Lindström 2003). Caller-assigned; magent does not assay glucose. true scores 5; false scores 0. - `activity_30min` (boolean, required): Usually at least 30 minutes of physical activity daily at work and/or leisure, including normal daily activity (Lindström 2003). true scores 0; false scores 2. - `daily_vegetables` (boolean, required): Daily consumption of vegetables, fruit, or berries (Lindström 2003). true scores 0; false scores 1. ## 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/findrisc` 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": [ { "activity_30min": "true", "age": "40", "bmi_kg_m2": "22", "bp_medication": "false", "daily_vegetables": "true", "history_high_glucose": "false", "sex": "male", "waist_cm": "80" }, { "activity_30min": "true", "age": "40", "bmi_kg_m2": "22", "bp_medication": "false", "daily_vegetables": "true", "history_high_glucose": "false", "sex": "male", "waist_cm": "80" } ] } ``` Human paywall (two-item fixture): https://api.magentlab.com/paywall/bulk/findrisc Example 200: ```json { "count": 2, "path": "/api/calc/findrisc", "items": [ { "components": [ { "value": 40, "factor": "age", "points": 0, "present": false }, { "value": 22.0, "factor": "bmi", "points": 0, "present": false }, { "value": 80.0, "factor": "waist", "points": 0, "present": false }, { "factor": "bp_medication", "points": 0, "present": false }, { "factor": "history_high_glucose", "points": 0, "present": false }, { "factor": "inactivity", "points": 0, "present": false }, { "factor": "no_daily_vegetables", "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": "Lindström J, Tuomilehto J", "doi": "10.2337/diacare.26.3.725", "id": "lindstrom-2003", "pmid": "12610029", "source": "Diabetes Care. 2003;26(3):725-731", "title": "The diabetes risk score: a practical tool to predict type 2 diabetes risk" }, "formula": "findrisc", "formula_expression": "FINDRISC = age + bmi + waist + bp_medication + history_high_glucose + inactivity + no_daily_vegetables; age <45 -> 0, 45-54 -> 2, 55-64 -> 3, >=65 -> 4; BMI <25 -> 0, 25-30 -> 1, >30 -> 3; waist men <94 -> 0, 94-102 -> 3, >102 -> 4; women <80 -> 0, 80-88 -> 3, >88 -> 4; bp_medication 2; history_high_glucose 5; activity_30min false -> 2; daily_vegetables false -> 1; max 20; at_risk iff score>=9", "age_years": 40, "max_score": 20, "score": 0, "sex": "male", "bmi_kg_m2": 22.0, "waist_cm": 80.0, "at_risk": false }, { "components": [ { "value": 40, "factor": "age", "points": 0, "present": false }, { "value": 22.0, "factor": "bmi", "points": 0, "present": false }, { "value": 80.0, "factor": "waist", "points": 0, "present": false }, { "factor": "bp_medication", "points": 0, "present": false }, { "factor": "history_high_glucose", "points": 0, "present": false }, { "factor": "inactivity", "points": 0, "present": false }, { "factor": "no_daily_vegetables", "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": "Lindström J, Tuomilehto J", "doi": "10.2337/diacare.26.3.725", "id": "lindstrom-2003", "pmid": "12610029", "source": "Diabetes Care. 2003;26(3):725-731", "title": "The diabetes risk score: a practical tool to predict type 2 diabetes risk" }, "formula": "findrisc", "formula_expression": "FINDRISC = age + bmi + waist + bp_medication + history_high_glucose + inactivity + no_daily_vegetables; age <45 -> 0, 45-54 -> 2, 55-64 -> 3, >=65 -> 4; BMI <25 -> 0, 25-30 -> 1, >30 -> 3; waist men <94 -> 0, 94-102 -> 3, >102 -> 4; women <80 -> 0, 80-88 -> 3, >88 -> 4; bp_medication 2; history_high_glucose 5; activity_30min false -> 2; daily_vegetables false -> 1; max 20; at_risk iff score>=9", "age_years": 40, "max_score": 20, "score": 0, "sex": "male", "bmi_kg_m2": 22.0, "waist_cm": 80.0, "at_risk": false } ] } ``` ## Response fields - `formula` (string): findrisc - `formula_expression` (string): Exact Lindström 2003 expression - `score` (integer): FINDRISC points; published range 0-20 - `max_score` (integer): 20 (Lindström 2003 published maximum) - `at_risk` (boolean): true iff score ≥9 (Lindström 2003 cutoff). Not a type 2 diabetes diagnosis and not a 10-year probability. - `age_years` (integer): Age in years used for the age band - `bmi_kg_m2` (number): Caller-supplied BMI in kg/m^2 used for the BMI band - `sex` (string): female or male, used for the waist bands - `waist_cm` (number): Waist circumference in cm used - `components` (array): Per-factor points - `citation` (object): Lindström 2003 Diabetes Care citation - `disclaimer` (string): Not-a-device notice ## Example JSON Frozen fixture. Not a live lookup. ```json { "components": [ { "value": 40, "factor": "age", "points": 0, "present": false }, { "value": 22.0, "factor": "bmi", "points": 0, "present": false }, { "value": 80.0, "factor": "waist", "points": 0, "present": false }, { "factor": "bp_medication", "points": 0, "present": false }, { "factor": "history_high_glucose", "points": 0, "present": false }, { "factor": "inactivity", "points": 0, "present": false }, { "factor": "no_daily_vegetables", "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": "Lindström J, Tuomilehto J", "doi": "10.2337/diacare.26.3.725", "id": "lindstrom-2003", "pmid": "12610029", "source": "Diabetes Care. 2003;26(3):725-731", "title": "The diabetes risk score: a practical tool to predict type 2 diabetes risk" }, "formula": "findrisc", "formula_expression": "FINDRISC = age + bmi + waist + bp_medication + history_high_glucose + inactivity + no_daily_vegetables; age <45 -> 0, 45-54 -> 2, 55-64 -> 3, >=65 -> 4; BMI <25 -> 0, 25-30 -> 1, >30 -> 3; waist men <94 -> 0, 94-102 -> 3, >102 -> 4; women <80 -> 0, 80-88 -> 3, >88 -> 4; bp_medication 2; history_high_glucose 5; activity_30min false -> 2; daily_vegetables false -> 1; max 20; at_risk iff score>=9", "age_years": 40, "max_score": 20, "score": 0, "sex": "male", "bmi_kg_m2": 22.0, "waist_cm": 80.0, "at_risk": false } ``` ## Errors - HTTP 400 `invalid_age`: age must be an integer from 18 to 120 Returned before settlement; you are not charged. - HTTP 400 `invalid_bmi_kg_m2`: bmi_kg_m2 must be a number from 10 to 80. Returned before settlement; you are not charged. - HTTP 400 `invalid_sex`: sex must be female or male Returned before settlement; you are not charged. - HTTP 400 `invalid_waist_range`: waist_cm must be a number from 40 to 200. 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. Shared HTTP 402 and 503: https://magentlab.com/docs/payments ## Related tools - [HOMA-IR](https://magentlab.com/docs/homa-ir) — Compute the Matthews 1985 HOMA-IR approximation from fasting plasma glucose and insulin. - [A1C ↔ eAG](https://magentlab.com/docs/a1c-eag) — Convert A1C percent to estimated average glucose, or the reverse, using Nathan/ADAG. ## 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 of accepted and payload). Magent attaches canonical extensions.bazaar on CDP verify/settle; echoing 402 bazaar is optional. - 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. HTTP 402 never includes the tool JSON. - 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.