ForHosting KIT · Developer Utilities

PEX tubing calculator

Planning a PEX repipe or a new manifold layout means knowing how much tubing to buy before you open coils on site.

● BetaFree · in your browser

Use it from WebAPIEmailTelegramApp soon

Guessing from floor area alone often underbuys long remote fixtures or overbuys a compact wet-wall design. This PEX tubing calculator multiplies the number of fixtures by the average one-way run from the manifold (or main supply point) to each outlet, then scales by how many lines each fixture needs—typically two for hot and cold—and adds a configurable waste percent for scrap, routing around framing, and fitting makeup. Optional coil length packs the purchase quantity into whole stock rolls so shopping lists match what suppliers sell. The same pure arithmetic powers the free browser widget and the API path, so material takeoffs, quote forms, and automation never disagree on the same inputs. Use it for early budgets; refine with a room-by-room measure when drawings are final.

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/pex-tubing

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/pex-tubing \
  -H "Authorization: Bearer $KIT_KEY" \
  -H "Content-Type: application/json" \
  -d '{"fixtures":8,"avg_run_per_fixture":25}'

const res = await fetch("https://api.kit.forhosting.com/home/pex-tubing", {
  method: "POST",
  headers: {
    "Authorization": `Bearer ${process.env.KIT_KEY}`,
    "Content-Type": "application/json"
  },
  body: JSON.stringify({
    "fixtures": 8,
    "avg_run_per_fixture": 25
  })
});
const { task_id } = await res.json();

import os, requests

res = requests.post(
    "https://api.kit.forhosting.com/home/pex-tubing",
    headers={"Authorization": f"Bearer {os.environ['KIT_KEY']}"},
    json={
    "fixtures": 8,
    "avg_run_per_fixture": 25
},
)
task_id = res.json()["task_id"]

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

body := bytes.NewBufferString(`{"fixtures":8,"avg_run_per_fixture":25}`)
req, _ := http.NewRequest("POST", "https://api.kit.forhosting.com/home/pex-tubing", body)
req.Header.Set("Authorization", "Bearer "+os.Getenv("KIT_KEY"))
req.Header.Set("Content-Type", "application/json")
res, _ := http.DefaultClient.Do(req)

Example request

{
  "fixtures": 8,
  "avg_run_per_fixture": 25
}

Example response

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