Body size · LIVE

Edmonton Obesity Staging System (EOSS)

EOSS

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.

LIVE $0.005 USDC GET /api/calc/eoss

Markdown: /docs/eoss.md · Canonical: https://magentlab.com/docs/eoss

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

Title

A proposed clinical staging system for obesity

Authors

Sharma AM, Kushner RF

Source

Int J Obes (Lond). 2009;33(3):289-295

DOI

10.1038/ijo.2009.2

Worked example

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

Try

Opens the live endpoint. Unpaid browser requests show the paywall; agents should send Accept: application/json.

/api/calc/eoss?eoss_stage=0

Full URL: https://api.magentlab.com/api/calc/eoss?eoss_stage=0

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/eoss?eoss_stage=0"

Parameters

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.

POST /api/calc/eoss Max 25 unit_amount + extra_item_amount * (n - 1) extra $0.002 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 (fixture)

{
  "items": [
    {
      "eoss_stage": "0"
    },
    {
      "eoss_stage": "0"
    }
  ]
}

Open bulk paywall →

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/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

Example JSON

Machine form of the same example. Frozen fixture. Not a live lookup.

{
  "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
}

Client errors (HTTP 400)

Invalid params return 400 without charge. Shared HTTP 402 and 503 meanings: Payments.

Related tools

• BMI — Compute Keys/Quetelet body-mass index from height and weight, plus a WHO adult band.
• 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 — 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. 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.