Principal stress 2D calculator
Plane-stress analysis asks a deceptively simple question: given the three in-plane components σx, σy and τxy at a point, what extreme normal stresses and what largest in-plane shear appear when the inspection element is rotated?
Run — free
Those extrema are the principal stresses σ1 and σ2 and the Mohr-circle radius τmax. Students checking a transformation-of-stress homework set, structural and mechanical engineers reading a strain-gauge rosette, and machine designers comparing a 2D stress state to an allowable all reach for Mohr's circle or the closed-form square-root identities that encode the same geometry. This 2D principal stress calculator accepts the three finite plane-stress components, applies those identities, and returns both principals, the maximum in-plane shear, the circle centre and radius, and the angle from the x-axis to the algebraically larger principal direction. The same pure function powers the free browser widget and the prepaid API path, so a classroom check and a production notebook never disagree on a square root.
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 do I use this capability?
Complete the fields above and run it on this page. The form highlights anything that needs attention.
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/eng/principal-stress-2d \
-H "Authorization: Bearer $KIT_KEY" \
-H "Content-Type: application/json" \
-d '{"sigma_x":80,"sigma_y":20,"tau_xy":30}'const res = await fetch("https://api.kit.forhosting.com/eng/principal-stress-2d", {
method: "POST",
headers: {
"Authorization": `Bearer ${process.env.KIT_KEY}`,
"Content-Type": "application/json"
},
body: JSON.stringify({
"sigma_x": 80,
"sigma_y": 20,
"tau_xy": 30
})
});
const { task_id } = await res.json();import os, requests
res = requests.post(
"https://api.kit.forhosting.com/eng/principal-stress-2d",
headers={"Authorization": f"Bearer {os.environ['KIT_KEY']}"},
json={
"sigma_x": 80,
"sigma_y": 20,
"tau_xy": 30
},
)
task_id = res.json()["task_id"]<?php
$res = file_get_contents("https://api.kit.forhosting.com/eng/principal-stress-2d", false, stream_context_create([
"http" => [
"method" => "POST",
"header" => "Authorization: Bearer " . getenv("KIT_KEY") . "\r\nContent-Type: application/json",
"content" => '{"sigma_x":80,"sigma_y":20,"tau_xy":30}',
],
]));
$task = json_decode($res, true);body := bytes.NewBufferString(`{"sigma_x":80,"sigma_y":20,"tau_xy":30}`)
req, _ := http.NewRequest("POST", "https://api.kit.forhosting.com/eng/principal-stress-2d", body)
req.Header.Set("Authorization", "Bearer "+os.Getenv("KIT_KEY"))
req.Header.Set("Content-Type", "application/json")
res, _ := http.DefaultClient.Do(req)Example request
{
"sigma_x": 80,
"sigma_y": 20,
"tau_xy": 30
}Example response
{
"task_id": "tsk_a1b2c3d4e5f6a1b2c3d4e5f6",
"type": "eng.principal_stress_2d",
"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. |