# Ganzoni iron deficit Ganzoni iron deficit Status: LIVE Price: $0.005 USDC `GET /api/calc/ganzoni` HTML: https://magentlab.com/docs/ganzoni Markdown: https://magentlab.com/docs/ganzoni.md Not a medical device. Not a diagnosis, dose, or listing recommendation. ## What it computes Compute the Ganzoni 1970 iron deficit from weight, measured hemoglobin, a caller-supplied target hemoglobin, and depot iron stores. ## When to use When an agent needs the published Ganzoni milligram deficit and must not invent a target hemoglobin, depot iron, or an IV iron product order. ## When not to use - Not an IV iron product dose or order. magent does not pick target hemoglobin or depot iron. - Not a diagnosis of iron deficiency. ## Formula ``` iron_deficit_mg = weight_kg * (target_hemoglobin_g_dl - hemoglobin_g_dl) * 2.4 + iron_stores_mg ``` ## Citation [Intravenous iron-dextran: therapeutic and experimental possibilities](https://pubmed.ncbi.nlm.nih.gov/5417430) Ganzoni AM Schweiz Med Wochenschr. 1970;100(7):301-303 DOI: none ## Worked example ### 70 kg, Hb 8 to 15 g/dL, stores 500 mg Given: `hemoglobin_g_dl=8, iron_stores_mg=500, target_hemoglobin_g_dl=15, weight_kg=70` 1. iron_deficit = 70 * (15 - 8) * 2.4 + 500 = 1176 + 500 = 1676.0 mg ### 70 kg, Hb 8 to 15 g/dL, stores 0 mg Given: `hemoglobin_g_dl=8, iron_stores_mg=0, target_hemoglobin_g_dl=15, weight_kg=70` 1. iron_deficit = 70 * (15 - 8) * 2.4 + 0 = 1176.0 mg ## Also searched as - Ganzoni - iron deficit - iron deficit formula - Ganzoni formula - hemoglobin iron stores - depot iron ## Parameters - `weight_kg` (number, optional): Weight in kilograms. Provide weight_kg or weight_lb. - `weight_lb` (number, optional): Weight in pounds. Converted as kg = lb * 0.45359237. - `hemoglobin_g_dl` (number, required): Measured hemoglobin in g/dL (3-22). This tool does not accept g/L. - `target_hemoglobin_g_dl` (number, required): Target hemoglobin in g/dL (7-18). Must be strictly greater than hemoglobin_g_dl. magent does not pick a target. - `iron_stores_mg` (number, required): Depot iron stores in mg (0-2000). Required; magent does not default a depot. ## 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/ganzoni` 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": [ { "hemoglobin_g_dl": "8", "iron_stores_mg": "500", "target_hemoglobin_g_dl": "15", "weight_kg": "70" }, { "hemoglobin_g_dl": "8", "iron_stores_mg": "500", "target_hemoglobin_g_dl": "15", "weight_kg": "70" } ] } ``` Human paywall (two-item fixture): https://api.magentlab.com/paywall/bulk/ganzoni Example 200: ```json { "count": 2, "path": "/api/calc/ganzoni", "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": "Ganzoni AM", "id": "ganzoni-1970", "pmid": "5417430", "source": "Schweiz Med Wochenschr. 1970;100(7):301-303", "title": "Intravenous iron-dextran: therapeutic and experimental possibilities" }, "formula": "ganzoni", "formula_expression": "iron_deficit_mg = weight_kg * (target_hemoglobin_g_dl - hemoglobin_g_dl) * 2.4 + iron_stores_mg", "weight_kg": 70.0, "hemoglobin_g_dl": 8.0, "iron_deficit_mg": 1676.0, "iron_stores_mg": 500.0, "target_hemoglobin_g_dl": 15.0 }, { "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": "Ganzoni AM", "id": "ganzoni-1970", "pmid": "5417430", "source": "Schweiz Med Wochenschr. 1970;100(7):301-303", "title": "Intravenous iron-dextran: therapeutic and experimental possibilities" }, "formula": "ganzoni", "formula_expression": "iron_deficit_mg = weight_kg * (target_hemoglobin_g_dl - hemoglobin_g_dl) * 2.4 + iron_stores_mg", "weight_kg": 70.0, "hemoglobin_g_dl": 8.0, "iron_deficit_mg": 1676.0, "iron_stores_mg": 500.0, "target_hemoglobin_g_dl": 15.0 } ] } ``` ## Response fields - `formula` (string): ganzoni - `formula_expression` (string): Exact expression used - `weight_kg` (number): Normalized weight in kg - `hemoglobin_g_dl` (number): Measured hemoglobin in g/dL - `target_hemoglobin_g_dl` (number): Target hemoglobin in g/dL used - `iron_stores_mg` (number): Depot iron stores in mg used - `iron_deficit_mg` (number): Iron deficit in mg, 1 decimal - `citation` (object): Ganzoni 1970 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": "Ganzoni AM", "id": "ganzoni-1970", "pmid": "5417430", "source": "Schweiz Med Wochenschr. 1970;100(7):301-303", "title": "Intravenous iron-dextran: therapeutic and experimental possibilities" }, "formula": "ganzoni", "formula_expression": "iron_deficit_mg = weight_kg * (target_hemoglobin_g_dl - hemoglobin_g_dl) * 2.4 + iron_stores_mg", "weight_kg": 70.0, "hemoglobin_g_dl": 8.0, "iron_deficit_mg": 1676.0, "iron_stores_mg": 500.0, "target_hemoglobin_g_dl": 15.0 } ``` ## Errors - HTTP 400 `invalid_weight`: weight_kg (1-500) or weight_lb (2-1100) is required Returned before settlement; you are not charged. - HTTP 400 `invalid_hemoglobin`: hemoglobin_g_l (30-220) or hemoglobin_g_dl (3-22) is required, not both. Returned before settlement; you are not charged. - HTTP 400 `invalid_target_hemoglobin`: target_hemoglobin_g_dl must be 7-18 and strictly greater than hemoglobin_g_dl. Returned before settlement; you are not charged. - HTTP 400 `invalid_iron_stores`: iron_stores_mg must be a number from 0 to 2000. 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. - [Devine IBW](https://magentlab.com/docs/ibw) — Compute Devine ideal body weight and 0.4 adjusted body weight from height, sex, and actual weight. ## 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.