Hendecagon area from apothem
Get the area of a regular 11-sided polygon from its apothem, the distance from the centre to a side: apothem 1 gives 11·tan(π/11). Handy when you measured to a side rather than along an edge. Free in your browser.
- Free
- Runs in your browser
- No sign-up
- Your data stays on your device
Run — free
Worked example
- Apothem
- 1
- Area
- 3.2298914223
- Side length
- 0.5872529859
- Perimeter
- 6.4597828446
A regular hendecagon is the eleven-sided polygon with equal sides and equal interior angles. When you already know the apothem (the perpendicular distance from the center to any side, equal to the inradius of the inscribed circle) and need the enclosed area, the standard regular-polygon identity multiplies eleven times the square of that apothem by the tangent of pi over eleven. You do not need eleven vertex coordinates, a full side-length survey, or a general computer-algebra session.
What regular-hendecagon area from the apothem means and how the numbers work
A regular hendecagon has eleven equal sides and eleven equal interior angles. Each interior angle measures one thousand four hundred forty over eleven degrees, about one hundred thirty point nine degrees. Once the figure is known to be regular, a single positive apothem a fixes the entire shape up to similarity scaling.
The standard area identity for any regular n-gon is one-half times perimeter times apothem. For n equals eleven that becomes area equals eleven times a squared times tan of pi over eleven. The central half-angle is one hundred eighty over eleven degrees, so the solver evaluates tan of pi over eleven once and multiplies—no angle-mode ambiguity, no iterative approximation, and no need to place eleven vertices in the plane.
Side length follows as two times a times that same tangent; perimeter is eleven times the side. For a unit apothem the area is eleven times tan of pi over eleven; scale by a squared for any other positive apothem. Every step is elementary arithmetic on one scalar: no iteration, no sampling, no wall-clock dependence, and no dependence on floating Date or network state.
Compared with a side-length-only landing, this path matches surveys and drafting notes where the inradius or flat-to-flat half-distance is the measured quantity rather than an edge length. Compared with a general n-gon calculator, this landing is dedicated to the hendecagon search intent and the familiar eleven-times-a-squared-times-tan form textbooks quote for the apothem path when n is eleven.
What you can do with it
Decorative layouts and planters measured by inradius
Turn a measured center-to-side distance of a regular hendecagon into floor, paint, planting, or fabric area without reconstructing every edge by hand.
Game, CAD, and mesh area stored by apothem
Validate a regular hendecagon pad or compute surface area when the scene graph stores the inradius rather than side length.
FAQ
Why must the apothem be positive?
A non-positive apothem does not define a positive finite regular hendecagon.
How is this different from a side-length hendecagon area tool?
A side-length tool takes edge length s. This one takes the apothem (inradius). Same regular hendecagon geometry, different measured input and different search intent.
Is the hendecagon area from apothem calculator free?
The browser tool is free and runs locally.
What is the area formula from the apothem?
Eleven times the apothem squared times the tangent of π/11. It is the regular-polygon rule of half the perimeter times the apothem, written out for eleven equal sides.
What else do I get besides the area?
The side length, which is twice the apothem times tan(π/11), and the perimeter, eleven times that side. They let you check edge cuts against your drawing without measuring every side.
Related tools
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/geom/hendecagon-area-apothem \
-H "Authorization: Bearer $KIT_KEY" \
-H "Content-Type: application/json" \
-d '{"apothem":1}'const res = await fetch("https://api.kit.forhosting.com/geom/hendecagon-area-apothem", {
method: "POST",
headers: {
"Authorization": `Bearer ${process.env.KIT_KEY}`,
"Content-Type": "application/json"
},
body: JSON.stringify({
"apothem": 1
})
});
const { task_id } = await res.json();import os, requests
res = requests.post(
"https://api.kit.forhosting.com/geom/hendecagon-area-apothem",
headers={"Authorization": f"Bearer {os.environ['KIT_KEY']}"},
json={
"apothem": 1
},
)
task_id = res.json()["task_id"]<?php
$res = file_get_contents("https://api.kit.forhosting.com/geom/hendecagon-area-apothem", false, stream_context_create([
"http" => [
"method" => "POST",
"header" => "Authorization: Bearer " . getenv("KIT_KEY") . "\r\nContent-Type: application/json",
"content" => '{"apothem":1}',
],
]));
$task = json_decode($res, true);body := bytes.NewBufferString(`{"apothem":1}`)
req, _ := http.NewRequest("POST", "https://api.kit.forhosting.com/geom/hendecagon-area-apothem", body)
req.Header.Set("Authorization", "Bearer "+os.Getenv("KIT_KEY"))
req.Header.Set("Content-Type", "application/json")
res, _ := http.DefaultClient.Do(req)Example request
{
"apothem": 1
}Example response
{
"task_id": "tsk_a1b2c3d4e5f6a1b2c3d4e5f6",
"type": "geom.hendecagon_area_apothem",
"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. |
Technical notes
This hendecagon area from apothem calculator accepts a single positive apothem, returns the area together with side length and perimeter for cross-checks, and rejects zero or negative apothems with invalid_input instead of inventing a meaningless number. The same pure solve function powers the free browser tool and the prepaid API path, so homework checks, grading scripts, landscaping takeoffs, decorative-layout estimators, and production pipelines all see the same deterministic JSON every time.
What regular-hendecagon area from the apothem means and how the numbers work
Its apothem is the inradius: the radius of the inscribed circle, equal to the perpendicular distance from the geometric center to the midpoint of any side. Degenerate inputs—zero, negative, missing, or non-finite apothem—do not form a positive finite regular hendecagon, so this tool returns invalid_input rather than zero or NaN.
How to call the API and what comes back
Use it from geometry homework pipelines, decorative eleven-sided layout or planter takeoff scripts when only the inradius is known, game-level tooling for hendecagon pads stored by apothem, interview-prep sandboxes, or any workflow that needs a reproducible regular hendecagon area without installing a computer-algebra package on every machine. Send a JSON body with one required field. Field apothem is the positive finite distance from the center of the regular hendecagon to any side; aliases a, r, and inradius are accepted so form UIs and scripts can keep their preferred names. On success the response echoes apothem, returns area as the enclosed region, side_length derived from two times apothem times tan of pi over eleven, perimeter as eleven times that side, method set to regular_hendecagon_from_apothem, and a short formula block documenting the closed forms including the general n-gon pattern and the specialized eleven-side expressions. Failed validation—missing the field, a non-finite value, a non-positive apothem, or an apothem outside published limits—returns invalid_input and is never charged. Pricing is a flat $0.002 per successful request with unit item. Pair success cases such as apothem one and apothem two with a deliberate zero or negative apothem to verify clients handle invalid_input cleanly. Round-trip checks are easy: after solving, confirm area equals one-half times perimeter times apothem within floating tolerance, that side_length equals two times apothem times tan of pi over eleven, and that area also matches eleven times that same factor times apothem squared after the same rounding policy.
Practical tips, limits, and related searches
When teaching, prefer paired examples: apothem one for the pure eleven-tan constant; apothem two so students can verify that area scales with a squared (four times the unit-apothem area); and apothem zero or negative to demonstrate the hard rejection path that protects callers from non-positive geometry. If you already know the side length instead, use a companion side-based regular-polygon area path so each search intent stays on its own SEO landing without cannibalizing the other. For flat-to-flat decorative tiles, hardware blanks, or playground figures, remember that the full width across flats is twice the apothem, so half of that measured distance is the number you pass here. Keep the apothem inside the published positive range up to one trillion so intermediate products stay finite in IEEE double precision on the Worker and in the browser. Units are whatever you pass—metres, feet, or game units—as long as you interpret area in the square of that unit; the API does not convert units for you. Because the formula only needs the apothem, students can recompute eleven times tan of pi over eleven times a squared by hand for small integers and match the API line by line after rounding. This landing targets people searching for a hendecagon area from apothem calculator, eleven-sided polygon inradius area tool, or regular hendecagon area from apothem; it is not the side-length-only hendecagon area calculator, not a general n-gon solver with a variable side count—use the regular polygon calculator when n is not eleven—and it is not a hendecagonal prism volume or hendecagonal pyramid tool. Prefer this endpoint when the figure is known regular and only the apothem or inradius is measured. Failed tasks that return invalid_input do not consume prepaid balance, which keeps exploratory scripts cheap when users type impossible apothems while learning the contract.
Integration use cases
Homework and exam checks from a measured apothem
Give students a positive apothem; compare their hand-computed hendecagon area, side length, and perimeter against a deterministic API or free browser result.
Technical questions
What is the area of a regular hendecagon with apothem a?
A = 11·a²·tan(π/11). This calculator evaluates that closed form and also returns side length 2·a·tan(π/11) and perimeter 11s.
What inputs does the hendecagon area from apothem calculator need?
Only one positive finite number: apothem (aliases a, r, inradius). Zero, negative, missing, or non-finite values return invalid_input.