# Edmonton Obesity Staging System (EOSS) EOSS Status: LIVE Price: $0.005 USDC `GET /api/calc/eoss` HTML: https://magentlab.com/docs/eoss Markdown: https://magentlab.com/docs/eoss.md Not a medical device. Not a diagnosis, dose, or listing recommendation. ## What it computes Echo the caller-assigned Sharma 2009 Edmonton Obesity Staging System stage (0-4) with the published clinical-picture description. magent does not assign stage from BMI or from domain scores. magent does not examine the patient. ## When to use When an agent already has an EOSS stage 0-4 as assigned by the caller from the Sharma 2009 clinical pictures and needs the published stage description. magent does not examine the patient, assign stage from BMI, or combine separate medical, functional, or psychological domain scores. ## When not to use - Not a medical device. magent does not examine the patient. - The caller assigns Sharma 2009 EOSS stage 0-4. magent does not assign stage from BMI or from separate medical, functional, or psychological domain scores. - Not WHO BMI class. Not a diagnosis. Not a surgical-eligibility gate. ## Formula ``` eoss_stage in {0, 1, 2, 3, 4} as assigned by the caller (Sharma 2009 Edmonton Obesity Staging System five stages). magent does not assign stage from BMI or from separate medical/functional/psychological domain scores. Not WHO BMI class. Not a surgical-eligibility gate. magent does not examine the patient. ``` ## Citation [A proposed clinical staging system for obesity](https://doi.org/10.1038/ijo.2009.2) Sharma AM, Kushner RF Int J Obes (Lond). 2009;33(3):289-295 DOI: [10.1038/ijo.2009.2](https://doi.org/10.1038/ijo.2009.2) ## Worked example ### Stage 0 no apparent obesity-related risk factors Given: `eoss_stage=0` 1. eoss_stage 0 as assigned by the caller 2. no apparent obesity-related risk factors, no physical symptoms, no psychopathology, no functional limitations and/or impairment of well being ### Stage 4 severe disability from obesity-related disease Given: `eoss_stage=4` 1. eoss_stage 4 as assigned by the caller 2. severe (potentially end-stage) disability/ies from obesity-related chronic diseases ## Also searched as - Edmonton Obesity Staging System - EOSS - Sharma 2009 obesity staging - obesity staging system - EOSS stage - Edmonton obesity stage - obesity clinical staging - EOSS 0-4 ## Parameters - `eoss_stage` (integer, required): Sharma 2009 Edmonton Obesity Staging System stage 0-4 as assigned by the caller (0 no apparent obesity-related risk factors, no physical symptoms, no psychopathology, no functional limitations and/or impairment of well being; 1 obesity-related subclinical risk factor(s) OR mild physical symptoms OR mild psychopathology / mild functional limitations / mild impairment of well being; 2 established obesity-related chronic disease(s) OR moderate limitations in activities of daily living and/or well being; 3 established end-organ damage OR significant psychopathology OR significant functional limitation(s) and/or impairment of well being; 4 severe (potentially end-stage) disability/ies from obesity-related chronic diseases, severe disabling psychopathology, severe functional limitation(s) and/or severe impairment of well being). Integer 0-4 only; reject 5, -1, and non-integers. magent does not assign stage from BMI or from separate medical/functional/psychological domain scores. Not WHO BMI class. 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/eoss` 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": [ { "eoss_stage": "0" }, { "eoss_stage": "0" } ] } ``` Human paywall (two-item fixture): https://api.magentlab.com/paywall/bulk/eoss Example 200: ```json { "count": 2, "path": "/api/calc/eoss", "items": [ { "description": "no apparent obesity-related risk factors (e.g. BP, lipids, fasting glucose in normal range), no physical symptoms, no psychopathology, no functional limitations and/or impairment of well being", "components": [ { "factor": "stage_0", "met": true }, { "factor": "stage_1", "met": false }, { "factor": "stage_2", "met": false }, { "factor": "stage_3", "met": false }, { "factor": "stage_4", "met": 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": "Sharma AM, Kushner RF", "doi": "10.1038/ijo.2009.2", "id": "sharma-2009", "pmid": "19139700", "source": "Int J Obes (Lond). 2009;33(3):289-295", "title": "A proposed clinical staging system for obesity" }, "formula": "eoss", "formula_expression": "eoss_stage in {0, 1, 2, 3, 4} as assigned by the caller (Sharma 2009 Edmonton Obesity Staging System five stages). magent does not assign stage from BMI or from separate medical/functional/psychological domain scores. Not WHO BMI class. Not a surgical-eligibility gate. magent does not examine the patient.", "eoss_stage": 0 }, { "description": "no apparent obesity-related risk factors (e.g. BP, lipids, fasting glucose in normal range), no physical symptoms, no psychopathology, no functional limitations and/or impairment of well being", "components": [ { "factor": "stage_0", "met": true }, { "factor": "stage_1", "met": false }, { "factor": "stage_2", "met": false }, { "factor": "stage_3", "met": false }, { "factor": "stage_4", "met": 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": "Sharma AM, Kushner RF", "doi": "10.1038/ijo.2009.2", "id": "sharma-2009", "pmid": "19139700", "source": "Int J Obes (Lond). 2009;33(3):289-295", "title": "A proposed clinical staging system for obesity" }, "formula": "eoss", "formula_expression": "eoss_stage in {0, 1, 2, 3, 4} as assigned by the caller (Sharma 2009 Edmonton Obesity Staging System five stages). magent does not assign stage from BMI or from separate medical/functional/psychological domain scores. Not WHO BMI class. Not a surgical-eligibility gate. magent does not examine the patient.", "eoss_stage": 0 } ] } ``` ## Response fields - `formula` (string): eoss - `formula_expression` (string): Published Sharma 2009 EOSS five-stage rule - `eoss_stage` (integer): Caller-assigned Sharma 2009 EOSS stage 0-4 - `description` (string): Sharma 2009 clinical-picture wording for that stage - `components` (array): Per-stage Tree rows stage_0, stage_1, stage_2, stage_3, stage_4 with factor and met; exactly one is met - `citation` (object): Sharma 2009 Int J Obes citation - `disclaimer` (string): Not-a-device notice ## Example JSON Frozen fixture. Not a live lookup. ```json { "description": "no apparent obesity-related risk factors (e.g. BP, lipids, fasting glucose in normal range), no physical symptoms, no psychopathology, no functional limitations and/or impairment of well being", "components": [ { "factor": "stage_0", "met": true }, { "factor": "stage_1", "met": false }, { "factor": "stage_2", "met": false }, { "factor": "stage_3", "met": false }, { "factor": "stage_4", "met": 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": "Sharma AM, Kushner RF", "doi": "10.1038/ijo.2009.2", "id": "sharma-2009", "pmid": "19139700", "source": "Int J Obes (Lond). 2009;33(3):289-295", "title": "A proposed clinical staging system for obesity" }, "formula": "eoss", "formula_expression": "eoss_stage in {0, 1, 2, 3, 4} as assigned by the caller (Sharma 2009 Edmonton Obesity Staging System five stages). magent does not assign stage from BMI or from separate medical/functional/psychological domain scores. Not WHO BMI class. Not a surgical-eligibility gate. magent does not examine the patient.", "eoss_stage": 0 } ``` ## Errors - HTTP 400 `invalid_eoss`: eoss_stage must be 0, 1, 2, 3, or 4 (Sharma 2009 Edmonton Obesity Staging System). 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 - [BMI](https://magentlab.com/docs/bmi) — Compute Keys/Quetelet body-mass index from height and weight, plus a WHO adult band. - [WHR](https://magentlab.com/docs/whr) — Compute waist–hip ratio (WHR) as waist circumference divided by hip circumference after the same unit normalize, following the WHO 2011 expert consultation report. - [RFM](https://magentlab.com/docs/rfm) — Compute Woolcott 2018 relative fat mass (RFM) from height, waist circumference, and sex as an estimator of whole-body fat percentage. ## 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.