Polar coordinate plane distance
Points in the plane are often written in polar form as a radius from the origin paired with an angle from a fixed reference ray.
Run — free
Robotics paths, antenna patterns, radar plots, and classroom trigonometry all need the straight-line distance between two such points without first converting every coordinate to Cartesian by hand. This polar coordinate plane distance calculator accepts two radii and two angles, applies the planar law of cosines d equals the square root of r1 squared plus r2 squared minus twice r1 r2 times the cosine of the angle between them, and returns a deterministic distance together with the signed angular separation. Angles may be supplied in degrees by default or in radians when you set the unit field. Negative radii are rejected because a polar radius is a non-negative distance from the origin. The same pure module powers the free browser widget and the prepaid API path so homework checks, notebooks, and edge workers never disagree on a floating-point edge case.
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/geo/polar-distance \
-H "Authorization: Bearer $KIT_KEY" \
-H "Content-Type: application/json" \
-d '{"r1":3,"theta1":0,"r2":4,"theta2":90}'const res = await fetch("https://api.kit.forhosting.com/geo/polar-distance", {
method: "POST",
headers: {
"Authorization": `Bearer ${process.env.KIT_KEY}`,
"Content-Type": "application/json"
},
body: JSON.stringify({
"r1": 3,
"theta1": 0,
"r2": 4,
"theta2": 90
})
});
const { task_id } = await res.json();import os, requests
res = requests.post(
"https://api.kit.forhosting.com/geo/polar-distance",
headers={"Authorization": f"Bearer {os.environ['KIT_KEY']}"},
json={
"r1": 3,
"theta1": 0,
"r2": 4,
"theta2": 90
},
)
task_id = res.json()["task_id"]<?php
$res = file_get_contents("https://api.kit.forhosting.com/geo/polar-distance", false, stream_context_create([
"http" => [
"method" => "POST",
"header" => "Authorization: Bearer " . getenv("KIT_KEY") . "\r\nContent-Type: application/json",
"content" => '{"r1":3,"theta1":0,"r2":4,"theta2":90}',
],
]));
$task = json_decode($res, true);body := bytes.NewBufferString(`{"r1":3,"theta1":0,"r2":4,"theta2":90}`)
req, _ := http.NewRequest("POST", "https://api.kit.forhosting.com/geo/polar-distance", body)
req.Header.Set("Authorization", "Bearer "+os.Getenv("KIT_KEY"))
req.Header.Set("Content-Type", "application/json")
res, _ := http.DefaultClient.Do(req)Example request
{
"r1": 3,
"theta1": 0,
"r2": 4,
"theta2": 90
}Example response
{
"task_id": "tsk_a1b2c3d4e5f6a1b2c3d4e5f6",
"type": "geo.polar_distance",
"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. |