Body size · LIVE

Relative fat mass (RFM)

RFM

Compute Woolcott 2018 relative fat mass (RFM) from height, waist circumference, and sex as an estimator of whole-body fat percentage.

LIVE $0.005 USDC GET /api/calc/rfm

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

Not a medical device. Not a diagnosis, dose, or listing recommendation.

What it computes

Compute Woolcott 2018 relative fat mass (RFM) from height, waist circumference, and sex as an estimator of whole-body fat percentage.

When to use

When an agent needs published RFM from height, waist, and sex and must not invent a body-fat percentage or apply later obesity cutoffs that are not in Woolcott 2018.

When not to use

• Not a medical device and not a body-fat diagnosis. magent does not measure the patient.
• Woolcott 2018 is the RFM estimate only. magent does not apply later obesity cutoffs that are not in that paper.

Formula

RFM = 64 - (20 * (height_m / waist_m)) + (12 * sex); sex = 0 male, 1 female

Citation

Title

Relative fat mass (RFM) as a new estimator of whole-body fat percentage ─ A cross-sectional study in American adult individuals

Authors

Woolcott OO, Bergman RN

Source

Sci Rep. 2018;8:10980

DOI

10.1038/s41598-018-29362-1

Worked example

Also searched as

• relative fat mass
• RFM
• Woolcott RFM
• height-to-waist fat mass
• Woolcott Bergman RFM
• RFM body fat percentage
• whole-body fat percentage estimator

Try

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

/api/calc/rfm?height_cm=180&waist_cm=90&sex=male

Full URL: https://api.magentlab.com/api/calc/rfm?height_cm=180&waist_cm=90&sex=male

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/rfm?height_cm=180&waist_cm=90&sex=male"

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/rfm 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": [
    {
      "height_cm": "180",
      "sex": "male",
      "waist_cm": "90"
    },
    {
      "height_cm": "180",
      "sex": "male",
      "waist_cm": "90"
    }
  ]
}

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/rfm",
  "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": "Woolcott OO, Bergman RN",
        "doi": "10.1038/s41598-018-29362-1",
        "id": "woolcott-2018",
        "pmid": "30030479",
        "source": "Sci Rep. 2018;8:10980",
        "title": "Relative fat mass (RFM) as a new estimator of whole-body fat percentage ─ A cross-sectional study in American adult individuals"
      },
      "formula": "rfm",
      "formula_expression": "RFM = 64 - (20 * (height_m / waist_m)) + (12 * sex); sex = 0 male, 1 female",
      "sex": "male",
      "height_cm": 180.0,
      "waist_cm": 90.0,
      "rfm": 24.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": "Woolcott OO, Bergman RN",
        "doi": "10.1038/s41598-018-29362-1",
        "id": "woolcott-2018",
        "pmid": "30030479",
        "source": "Sci Rep. 2018;8:10980",
        "title": "Relative fat mass (RFM) as a new estimator of whole-body fat percentage ─ A cross-sectional study in American adult individuals"
      },
      "formula": "rfm",
      "formula_expression": "RFM = 64 - (20 * (height_m / waist_m)) + (12 * sex); sex = 0 male, 1 female",
      "sex": "male",
      "height_cm": 180.0,
      "waist_cm": 90.0,
      "rfm": 24.0
    }
  ]
}

Response

Example JSON

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

{
  "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": "Woolcott OO, Bergman RN",
    "doi": "10.1038/s41598-018-29362-1",
    "id": "woolcott-2018",
    "pmid": "30030479",
    "source": "Sci Rep. 2018;8:10980",
    "title": "Relative fat mass (RFM) as a new estimator of whole-body fat percentage ─ A cross-sectional study in American adult individuals"
  },
  "formula": "rfm",
  "formula_expression": "RFM = 64 - (20 * (height_m / waist_m)) + (12 * sex); sex = 0 male, 1 female",
  "sex": "male",
  "height_cm": 180.0,
  "waist_cm": 90.0,
  "rfm": 24.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.
• BRI — Compute Thomas 2013 body roundness index from height and waist by modeling the body as an ellipse.

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.