Liver · LIVE

Fatty liver index

Compute the Bedogni 2006 fatty liver index from caller-supplied BMI, waist circumference, triglycerides, and GGT as a predictor of hepatic steatosis in the general population.

LIVE $0.005 USDC GET /api/calc/fli

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

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

What it computes

Compute the Bedogni 2006 fatty liver index from caller-supplied BMI, waist circumference, triglycerides, and GGT as a predictor of hepatic steatosis in the general population.

When to use

When an agent needs published Bedogni 2006 FLI arithmetic and must not invent an imaging diagnosis, hepatic steatosis index cutoffs, or NAFLD fibrosis score bands.

When not to use

• Not a medical device. Not a steatosis diagnosis and not a substitute for imaging.
• BMI is caller-supplied. magent does not compute BMI from height and weight in this tool.
• Bedogni 2006 FLI only. Not the hepatic steatosis index, not the NAFLD fibrosis score, not FIB-4, and not APRI.

Formula

L = 0.953 * loge(triglycerides_mg_dl) + 0.139 * bmi_kg_m2 + 0.718 * loge(ggt_u_l) + 0.053 * waist_cm - 15.745; FLI = (e^L / (1 + e^L)) * 100

Citation

Title

The Fatty Liver Index: a simple and accurate predictor of hepatic steatosis in the general population

Authors

Bedogni G, Bellentani S, Miglioli L, Masutti F, Passalacqua M, Castiglione A, Tiribelli C

Source

BMC Gastroenterol. 2006;6:33

DOI

10.1186/1471-230X-6-33

Worked example

Also searched as

• fatty liver index
• FLI Bedogni
• Bedogni 2006 FLI
• hepatic steatosis FLI
• fatty liver index BMI waist GGT
• FLI triglycerides GGT
• Bedogni fatty liver

Try

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

/api/calc/fli?bmi_kg_m2=22&waist_cm=70&triglycerides_mg_dl=80&ggt_u_l=20

Full URL: https://api.magentlab.com/api/calc/fli?bmi_kg_m2=22&waist_cm=70&triglycerides_mg_dl=80&ggt_u_l=20

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/fli?bmi_kg_m2=22&waist_cm=70&triglycerides_mg_dl=80&ggt_u_l=20"

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/fli 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": [
    {
      "bmi_kg_m2": "22",
      "ggt_u_l": "20",
      "triglycerides_mg_dl": "80",
      "waist_cm": "70"
    },
    {
      "bmi_kg_m2": "22",
      "ggt_u_l": "20",
      "triglycerides_mg_dl": "80",
      "waist_cm": "70"
    }
  ]
}

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/fli",
  "items": [
    {
      "l": -2.65,
      "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": "Bedogni G, Bellentani S, Miglioli L, Masutti F, Passalacqua M, Castiglione A, Tiribelli C",
        "doi": "10.1186/1471-230X-6-33",
        "id": "bedogni-2006",
        "pmid": "17081293",
        "source": "BMC Gastroenterol. 2006;6:33",
        "title": "The Fatty Liver Index: a simple and accurate predictor of hepatic steatosis in the general population"
      },
      "formula": "fli",
      "formula_expression": "L = 0.953 * loge(triglycerides_mg_dl) + 0.139 * bmi_kg_m2 + 0.718 * loge(ggt_u_l) + 0.053 * waist_cm - 15.745; FLI = (e^L / (1 + e^L)) * 100",
      "bmi_kg_m2": 22.0,
      "bedogni_band": "rule_out",
      "fli": 6.6,
      "ggt_u_l": 20.0,
      "triglycerides_mg_dl": 80.0,
      "waist_cm": 70.0
    },
    {
      "l": -2.65,
      "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": "Bedogni G, Bellentani S, Miglioli L, Masutti F, Passalacqua M, Castiglione A, Tiribelli C",
        "doi": "10.1186/1471-230X-6-33",
        "id": "bedogni-2006",
        "pmid": "17081293",
        "source": "BMC Gastroenterol. 2006;6:33",
        "title": "The Fatty Liver Index: a simple and accurate predictor of hepatic steatosis in the general population"
      },
      "formula": "fli",
      "formula_expression": "L = 0.953 * loge(triglycerides_mg_dl) + 0.139 * bmi_kg_m2 + 0.718 * loge(ggt_u_l) + 0.053 * waist_cm - 15.745; FLI = (e^L / (1 + e^L)) * 100",
      "bmi_kg_m2": 22.0,
      "bedogni_band": "rule_out",
      "fli": 6.6,
      "ggt_u_l": 20.0,
      "triglycerides_mg_dl": 80.0,
      "waist_cm": 70.0
    }
  ]
}

Response

Example JSON

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

{
  "l": -2.65,
  "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": "Bedogni G, Bellentani S, Miglioli L, Masutti F, Passalacqua M, Castiglione A, Tiribelli C",
    "doi": "10.1186/1471-230X-6-33",
    "id": "bedogni-2006",
    "pmid": "17081293",
    "source": "BMC Gastroenterol. 2006;6:33",
    "title": "The Fatty Liver Index: a simple and accurate predictor of hepatic steatosis in the general population"
  },
  "formula": "fli",
  "formula_expression": "L = 0.953 * loge(triglycerides_mg_dl) + 0.139 * bmi_kg_m2 + 0.718 * loge(ggt_u_l) + 0.053 * waist_cm - 15.745; FLI = (e^L / (1 + e^L)) * 100",
  "bmi_kg_m2": 22.0,
  "bedogni_band": "rule_out",
  "fli": 6.6,
  "ggt_u_l": 20.0,
  "triglycerides_mg_dl": 80.0,
  "waist_cm": 70.0
}

Client errors (HTTP 400)

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

Related tools

• NAFLD fibrosis score — Compute the Angulo 2007 NAFLD fibrosis score from age, BMI, IFG/diabetes, AST, ALT, platelets, and albumin.

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.
• 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.