Atrial fibrillation · LIVE
HAS-BLED calculator
HAS-BLED
Compute the HAS-BLED bleeding-risk score from discrete clinical flags.
Markdown: /docs/has-bled.md · Canonical: https://magentlab.com/docs/has-bled
Not a medical device. Not a diagnosis, dose, or listing recommendation.
What it computes
Compute the HAS-BLED bleeding-risk score from discrete clinical flags.
When to use
When an agent needs AF bleeding-risk arithmetic and must not invent the point total from prose.
When not to use
- Not a diagnosis and not a treatment or anticoagulation recommendation.
- Labile INR and other flags are caller-supplied. magent does not read an INR time-in-range.
Formula
HAS-BLED = hypertension + abnormal_renal + abnormal_liver + stroke + bleeding + labile_inr + elderly(age>65) + drugs + alcohol; max 9
Citation
- Authors
- Pisters R, Lane DA, Nieuwlaat R, de Vos CB, Crijns HJ, Lip GYH
- Source
- Chest. 2010;138(5):1093-1100
Worked example
Age 78, hypertension only
Given:
abnormal_liver=falseabnormal_renal=falseage=78alcohol=falsebleeding=falsedrugs=falsehypertension=truelabile_inr=falsestroke=false
- Hypertension → 1; age >65 → 1
- Score = 2
Also searched as
- HASBLED
- HAS BLED score
- Pisters bleeding score
- AF bleed risk
Try
Opens the live endpoint. Unpaid browser requests show the paywall; agents should send Accept: application/json.
Full URL: https://api.magentlab.com/api/calc/has_bled?age=78&hypertension=true&abnormal_renal=false&abnormal_liver=false&stroke=false&bleeding=false&labile_inr=false&drugs=false&alcohol=false
Call
Expect HTTP 402 until you retry with PAYMENT-SIGNATURE. Incomplete query params
return HTTP 400 before any quote or charge.
curl -i -H "Accept: application/json" "https://api.magentlab.com/api/calc/has_bled?age=78&hypertension=true&abnormal_renal=false&abnormal_liver=false&stroke=false&bleeding=false&labile_inr=false&drugs=false&alcohol=false"
Parameters
| Name | Type | Required | Description |
|---|---|---|---|
age |
integer | required | Age in years (18-120). Age >65 scores 1 (E). |
hypertension |
boolean | required | Uncontrolled hypertension (H). true or false. |
abnormal_renal |
boolean | required | Abnormal renal function (A). true or false. |
abnormal_liver |
boolean | required | Abnormal liver function (A). true or false. Renal and liver each score 1. |
stroke |
boolean | required | Prior stroke (S). true or false. |
bleeding |
boolean | required | Bleeding history or predisposition (B). true or false. |
labile_inr |
boolean | required | Labile INR (L). true or false. |
drugs |
boolean | required | Concomitant antiplatelet or NSAID (D). true or false. |
alcohol |
boolean | required | Alcohol excess (D). true or false. Drugs and alcohol each score 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.
- 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 (fixture)
{
"items": [
{
"abnormal_liver": "false",
"abnormal_renal": "false",
"age": "78",
"alcohol": "false",
"bleeding": "false",
"drugs": "false",
"hypertension": "true",
"labile_inr": "false",
"stroke": "false"
},
{
"abnormal_liver": "false",
"abnormal_renal": "false",
"age": "78",
"alcohol": "false",
"bleeding": "false",
"drugs": "false",
"hypertension": "true",
"labile_inr": "false",
"stroke": "false"
}
]
}
Opens a two-item fixture on the API host. Unpaid browsers get the same MetaMask paywall as GET; Pay retries POST with those items.
Example 200 (fixture)
{
"count": 2,
"path": "/api/calc/has_bled",
"items": [
{
"components": [
{
"factor": "hypertension",
"points": 1,
"present": true
},
{
"factor": "abnormal_renal",
"points": 0,
"present": false
},
{
"factor": "abnormal_liver",
"points": 0,
"present": false
},
{
"factor": "stroke",
"points": 0,
"present": false
},
{
"factor": "bleeding",
"points": 0,
"present": false
},
{
"factor": "labile_inr",
"points": 0,
"present": false
},
{
"value": 78,
"factor": "elderly_age_gt_65",
"points": 1,
"present": true
},
{
"factor": "drugs",
"points": 0,
"present": false
},
{
"factor": "alcohol",
"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": "Pisters R, Lane DA, Nieuwlaat R, de Vos CB, Crijns HJ, Lip GYH",
"doi": "10.1378/chest.10-0134",
"id": "pisters-2010",
"source": "Chest. 2010;138(5):1093-1100",
"title": "A novel user-friendly score (HAS-BLED) to assess 1-year risk of major bleeding in patients with atrial fibrillation: the Euro Heart Survey"
},
"formula": "has_bled",
"formula_expression": "HAS-BLED = hypertension + abnormal_renal + abnormal_liver + stroke + bleeding + labile_inr + elderly(age>65) + drugs + alcohol; max 9",
"max_score": 9,
"score": 2,
"age_years": 78
},
{
"components": [
{
"factor": "hypertension",
"points": 1,
"present": true
},
{
"factor": "abnormal_renal",
"points": 0,
"present": false
},
{
"factor": "abnormal_liver",
"points": 0,
"present": false
},
{
"factor": "stroke",
"points": 0,
"present": false
},
{
"factor": "bleeding",
"points": 0,
"present": false
},
{
"factor": "labile_inr",
"points": 0,
"present": false
},
{
"value": 78,
"factor": "elderly_age_gt_65",
"points": 1,
"present": true
},
{
"factor": "drugs",
"points": 0,
"present": false
},
{
"factor": "alcohol",
"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": "Pisters R, Lane DA, Nieuwlaat R, de Vos CB, Crijns HJ, Lip GYH",
"doi": "10.1378/chest.10-0134",
"id": "pisters-2010",
"source": "Chest. 2010;138(5):1093-1100",
"title": "A novel user-friendly score (HAS-BLED) to assess 1-year risk of major bleeding in patients with atrial fibrillation: the Euro Heart Survey"
},
"formula": "has_bled",
"formula_expression": "HAS-BLED = hypertension + abnormal_renal + abnormal_liver + stroke + bleeding + labile_inr + elderly(age>65) + drugs + alcohol; max 9",
"max_score": 9,
"score": 2,
"age_years": 78
}
]
}
Response
| Field | Type | Description |
|---|---|---|
formula |
string | has_bled |
formula_expression |
string | Exact expression used |
score |
integer | Total points 0-9 |
max_score |
integer | Always 9 |
age_years |
integer | Age used for the E criterion |
components |
array | Per-factor points |
citation |
object | Chest 2010 citation |
disclaimer |
string | Not-a-device notice |
Example JSON
Machine form of the same example. Frozen fixture. Not a live lookup.
{
"components": [
{
"factor": "hypertension",
"points": 1,
"present": true
},
{
"factor": "abnormal_renal",
"points": 0,
"present": false
},
{
"factor": "abnormal_liver",
"points": 0,
"present": false
},
{
"factor": "stroke",
"points": 0,
"present": false
},
{
"factor": "bleeding",
"points": 0,
"present": false
},
{
"factor": "labile_inr",
"points": 0,
"present": false
},
{
"value": 78,
"factor": "elderly_age_gt_65",
"points": 1,
"present": true
},
{
"factor": "drugs",
"points": 0,
"present": false
},
{
"factor": "alcohol",
"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": "Pisters R, Lane DA, Nieuwlaat R, de Vos CB, Crijns HJ, Lip GYH",
"doi": "10.1378/chest.10-0134",
"id": "pisters-2010",
"source": "Chest. 2010;138(5):1093-1100",
"title": "A novel user-friendly score (HAS-BLED) to assess 1-year risk of major bleeding in patients with atrial fibrillation: the Euro Heart Survey"
},
"formula": "has_bled",
"formula_expression": "HAS-BLED = hypertension + abnormal_renal + abnormal_liver + stroke + bleeding + labile_inr + elderly(age>65) + drugs + alcohol; max 9",
"max_score": 9,
"score": 2,
"age_years": 78
}
Client errors (HTTP 400)
Invalid params return 400 without charge. Shared HTTP 402 and 503 meanings: Payments.
| HTTP | Code | When |
|---|---|---|
| 400 | invalid_age |
age must be an integer from 18 to 120 Returned before settlement; you are not charged. |
| 400 | invalid_flag |
boolean clinical flags must be true or false Returned before settlement; you are not charged. |
| 400 | invalid_items |
POST body must be a JSON object with only an items array Returned before settlement; you are not charged. |
| 400 | invalid_item_count |
items must be an array of 1 to 25 objects Returned before settlement; you are not charged. |
| 400 | invalid_item |
each items entry must be a JSON object Returned before settlement; you are not charged. |
Related tools
- CHA2DS2-VASc — Agents must not invent CHA2DS2-VASc from model memory. This endpoint computes the published Lip 2010 CHA2DS2-VASc stroke-risk score from discrete clinical flags; pay per request with x402 USDC on Base.
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. Unpaid valid requests return HTTP 402 with a base64
PAYMENT-REQUIRED
header. HTTP 503 is not a new quote: retry the same PAYMENT-SIGNATURE. Full handshake
and shared payment errors: Payments.
Stdio MCP: /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.