ForHosting KIT · Developer Utilities

Corner stud count calculator

Framing takeoffs often under-order lumber at corners and partition intersections because linear wall-run formulas only place end studs on each plate.

● BetaFree · in your browser

Run — free How it works & API

Use it from WebAPIEmailTelegramApp soon

This corner stud count calculator answers a different question: given how many outside L-corners and how many interior tee intersections your plan has, how many studs belong in those assemblies? You enter corner and tee counts, optionally override the default three-stud corner and two-stud tee packs, and receive corner_studs, tee_studs, and total_studs with a stable formula string. Pair it with a wall-run stud calculator for on-center layout, then add these assembly members so the cut list matches field practice for traditional or California corners. The browser tool runs free on your device; prepaid API calls cost $0.002 per successful item when estimating apps need the same deterministic contract.

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

POSThttps://api.kit.forhosting.com/home/corner-studs

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/home/corner-studs \
  -H "Authorization: Bearer $KIT_KEY" \
  -H "Content-Type: application/json" \
  -d '{"corners":4,"tees":2}'

const res = await fetch("https://api.kit.forhosting.com/home/corner-studs", {
  method: "POST",
  headers: {
    "Authorization": `Bearer ${process.env.KIT_KEY}`,
    "Content-Type": "application/json"
  },
  body: JSON.stringify({
    "corners": 4,
    "tees": 2
  })
});
const { task_id } = await res.json();

import os, requests

res = requests.post(
    "https://api.kit.forhosting.com/home/corner-studs",
    headers={"Authorization": f"Bearer {os.environ['KIT_KEY']}"},
    json={
    "corners": 4,
    "tees": 2
},
)
task_id = res.json()["task_id"]

<?php
$res = file_get_contents("https://api.kit.forhosting.com/home/corner-studs", false, stream_context_create([
  "http" => [
    "method"  => "POST",
    "header"  => "Authorization: Bearer " . getenv("KIT_KEY") . "\r\nContent-Type: application/json",
    "content" => '{"corners":4,"tees":2}',
  ],
]));
$task = json_decode($res, true);

body := bytes.NewBufferString(`{"corners":4,"tees":2}`)
req, _ := http.NewRequest("POST", "https://api.kit.forhosting.com/home/corner-studs", body)
req.Header.Set("Authorization", "Bearer "+os.Getenv("KIT_KEY"))
req.Header.Set("Content-Type", "application/json")
res, _ := http.DefaultClient.Do(req)

Example request

{
  "corners": 4,
  "tees": 2
}

Example response

{
  "task_id": "tsk_a1b2c3d4e5f6a1b2c3d4e5f6",
  "type": "home.corner_studs",
  "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

Per request$0.002

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.

Read the full KIT documentation →