Beads per length calculator
Jewelry makers still need one honest integer before they cut cord or buy a hank: how many beads of a known diameter actually sit along the finished, strung length of a necklace, bracelet, or anklet.
Run — free
This beads per length calculator accepts the target strung length in millimetres, centimetres, or international inches, the bead diameter in millimetres, an optional knot or spacer gap in millimetres, and an optional clasp-and-findings length in millimetres. It converts the strand into millimetres, subtracts the clasp, then packs whole beads with gaps only between neighbouring beads so the count never overshoots the usable wire or cord. The path is pure finite arithmetic with no network calls, no random waste fudge, and no date-dependent shortcuts, so the same measurements always produce the same shopping count. Use it free in the browser when planning a commission, or call the API at $0.002 per successful request when shop tools and CI fixtures need a deterministic bead count.
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/hobby/craft-beads-per-length \
-H "Authorization: Bearer $KIT_KEY" \
-H "Content-Type: application/json" \
-d '{"length":180,"bead_diameter":6}'const res = await fetch("https://api.kit.forhosting.com/hobby/craft-beads-per-length", {
method: "POST",
headers: {
"Authorization": `Bearer ${process.env.KIT_KEY}`,
"Content-Type": "application/json"
},
body: JSON.stringify({
"length": 180,
"bead_diameter": 6
})
});
const { task_id } = await res.json();import os, requests
res = requests.post(
"https://api.kit.forhosting.com/hobby/craft-beads-per-length",
headers={"Authorization": f"Bearer {os.environ['KIT_KEY']}"},
json={
"length": 180,
"bead_diameter": 6
},
)
task_id = res.json()["task_id"]<?php
$res = file_get_contents("https://api.kit.forhosting.com/hobby/craft-beads-per-length", false, stream_context_create([
"http" => [
"method" => "POST",
"header" => "Authorization: Bearer " . getenv("KIT_KEY") . "\r\nContent-Type: application/json",
"content" => '{"length":180,"bead_diameter":6}',
],
]));
$task = json_decode($res, true);body := bytes.NewBufferString(`{"length":180,"bead_diameter":6}`)
req, _ := http.NewRequest("POST", "https://api.kit.forhosting.com/hobby/craft-beads-per-length", body)
req.Header.Set("Authorization", "Bearer "+os.Getenv("KIT_KEY"))
req.Header.Set("Content-Type", "application/json")
res, _ := http.DefaultClient.Do(req)Example request
{
"length": 180,
"bead_diameter": 6
}Example response
{
"task_id": "tsk_a1b2c3d4e5f6a1b2c3d4e5f6",
"type": "hobby.craft_beads_per_length",
"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. |