Omega-6 to omega-3 ratio calculator
Omega-6 to omega-3 ratio calculator: enter your values and see a clear result on this page. Free for individual checks; API from $0.002.
Run — free
How to use it
Enter your values in the form above. The tool checks them before calculating and shows the result on the same page.
Check your inputs
Use the labels and units shown next to each field. If something is missing or outside the allowed range, the page points to the field to fix.
Use it again or automate it
Use the browser tool for individual checks and the API when you need the same capability in an automated workflow.
What you can do with it
Get an answer now
Enter one set of values and see the result without building a spreadsheet or script.
Compare scenarios
Change one value at a time and rerun the calculation to understand what affects the result.
Automate repeated work
Use the API when the same calculation needs to run inside your product or workflow.
FAQ
How is the omega-6 to omega-3 ratio calculated?
Send positive gram intakes for omega6 and omega3. The API returns ratio = omega6 / omega3, a compact n:1 label, and a screening band (balanced ≤4, elevated ≤10, high >10).
What units should I use?
Grams for both fields over the same period (usually one day). Convert milligrams to grams consistently before calling; the ratio itself is unitless.
Why does zero or negative intake fail?
Division by zero is undefined, and non-positive grams are not a meaningful intake total. The tool returns invalid_input instead of inventing infinity.
Is the band a medical diagnosis?
No. balanced, elevated, and high are educational screening labels for common discussion ranges. They do not replace lab tests or clinical advice.
What does the omega-6 to omega-3 ratio calculator cost?
The browser tool is free. API requests use prepaid KIT balance at $0.002 per successful call; invalid input is not billed.
For developers — API access
Everything on this page is available programmatically. This section is for teams who want to wire it into their own systems; everyone else can just use the tool above.
API endpoint
Prefer to automate it? One authenticated POST creates the task; the result comes back by webhook or a signed link. The same capability also runs here on the web, by email and from Telegram — and soon from our app too.
Call it from your stack
curl -X POST https://api.kit.forhosting.com/health/omega-ratio \
-H "Authorization: Bearer $KIT_KEY" \
-H "Content-Type: application/json" \
-d '{"omega6":12,"omega3":2}'const res = await fetch("https://api.kit.forhosting.com/health/omega-ratio", {
method: "POST",
headers: {
"Authorization": `Bearer ${process.env.KIT_KEY}`,
"Content-Type": "application/json"
},
body: JSON.stringify({
"omega6": 12,
"omega3": 2
})
});
const { task_id } = await res.json();import os, requests
res = requests.post(
"https://api.kit.forhosting.com/health/omega-ratio",
headers={"Authorization": f"Bearer {os.environ['KIT_KEY']}"},
json={
"omega6": 12,
"omega3": 2
},
)
task_id = res.json()["task_id"]<?php
$res = file_get_contents("https://api.kit.forhosting.com/health/omega-ratio", false, stream_context_create([
"http" => [
"method" => "POST",
"header" => "Authorization: Bearer " . getenv("KIT_KEY") . "\r\nContent-Type: application/json",
"content" => '{"omega6":12,"omega3":2}',
],
]));
$task = json_decode($res, true);body := bytes.NewBufferString(`{"omega6":12,"omega3":2}`)
req, _ := http.NewRequest("POST", "https://api.kit.forhosting.com/health/omega-ratio", body)
req.Header.Set("Authorization", "Bearer "+os.Getenv("KIT_KEY"))
req.Header.Set("Content-Type", "application/json")
res, _ := http.DefaultClient.Do(req)Example request
{
"omega6": 12,
"omega3": 2
}Example response
{
"task_id": "tsk_a1b2c3d4e5f6a1b2c3d4e5f6",
"type": "health.omega_ratio",
"status": "queued",
"_links": {
"result": "/tasks/tsk_…/result"
}
}The API is asynchronous: the call returns a task_id immediately and the result arrives by webhook. Polling is capped at 1 req/s per task.
Pricing
Published price — no tokens, no invented credits. A failed task is never charged.
Errors
| HTTP | Code | Meaning |
|---|---|---|
401 | unauthorized | Missing or invalid API key. |
402 | insufficient_balance | Your balance doesn't cover the task price. |
404 | unknown_type | That task type doesn't exist. |
429 | rate_limited | Too many requests. Use the webhook instead of polling. |