API · /knitting-api

Knitting Gauge API

healthy 3,961 Subscribers

Knitting and crochet gauge maths as an API, computed locally and deterministically. The stitches endpoint turns a gauge — the standard stitches and rows per 10 cm measured from a tension swatch — into the number of stitches to cast on for a target width and the number of rows for a target length; at 22 stitches and 30 rows per 10 cm, a 50 cm wide by 60 cm long piece needs 110 stitches and 180 rows. The gauge endpoint works backwards from a measured swatch, converting a count over a measured distance into stitches (or rows) per 10 cm, per centimetre and per inch — 33 stitches over 15 cm is a gauge of 22 per 10 cm. The convert-pattern endpoint re-scales a pattern written for one gauge to your own gauge so the finished garment keeps its intended size: your count = pattern count · (your gauge / pattern gauge), so a 100-stitch cast-on at a 20-per-10 cm pattern becomes 110 at your 22-per-10 cm tension. Dimensions are in centimetres. Everything is computed locally and deterministically, so it is instant and private. Ideal for knitting, crochet, pattern-design, craft-marketplace and maker app developers, gauge and tension calculators, and yarn-shop tools. Pure local computation — no key, no third-party service, instant. Live, nothing stored. 3 endpoints. This is gauge and stitch maths; works for crochet too by using your stitch gauge.

#knitting #crochet #gauge #tension #crafts #developer-tools

api.oanor.com/knitting-api

Get an API key Try in playground → Contact provider

Machine-readable spec so AI agents can integrate this API.

/api/knitting-api/openapi.json

/api/knitting-api/llms.txt

Discovery: GET /api/index.json lists every API.

API health

healthy

Uptime: 100.00%; Server probes · 24h
Avg latency: 83 ms; Server probes · 24h
Subscribers: 3,961; active
Total calls: 16; last 7 days

Full status page → · 20 probes/24h

Pricing

Pick a tier — billed monthly, cancel anytime.

Free

7,300 calls / month
2 requests / second
Hard cap (429 above quota, no overage)
7,300 calls/month
2 req/sec
Stitches + gauge + pattern conversion
No credit card

Starter

€3.60 /month

73,000 calls / month
6 requests / second
Hard cap (429 above quota, no overage)
73,000 calls/month
6 req/sec
Per-inch gauge, crochet support
Email support

Pro

€10.00 /month

325,000 calls / month
15 requests / second
Hard cap (429 above quota, no overage)
325,000 calls/month
15 req/sec
Pattern-app & marketplace pipelines
Priority support

Mega

€32.00 /month

1,720,000 calls / month
40 requests / second
Hard cap (429 above quota, no overage)
1,720,000 calls/month
40 req/sec
Platform scale
Dedicated SLA

Built by

PremiumApi

Related APIs

Other APIs with overlapping tags.

Catenary Cable API

Catenary (hanging-cable) maths as an API, computed locally and deterministically. The sag endpoint solves the exact catenary for a cable hung between two level supports: from the span, the weight per unit length and either the horizontal tension or the sag, it returns the catenary parameter a = H/w, the sag a·(cosh(L/2a) − 1), the cable length 2a·sinh(L/2a), the minimum tension (the horizontal tension at the lowest point) and the maximum tension at the supports (H·cosh(L/2a)), plus the slack over the straight span. The parabolic endpoint gives the shallow-sag parabolic approximation — sag = w·L²/(8·H) — that is standard for overhead utility lines, and converts between sag and tension either way. The length endpoint returns the cable length for a given span and sag, with the parabolic value alongside for comparison. Forces and lengths are unit-agnostic but must be consistent (for example newtons, newtons per metre and metres). Everything is computed locally and deterministically, so it is instant and private. Ideal for power-line and transmission tools, zip-line and rigging apps, suspension and surveying calculators, and physics and engineering education. Pure local computation — no key, no third-party service, instant. Live, nothing stored. 3 endpoints. This is hanging-cable catenary maths; for rigging working load limits use a rigging API and for beam deflection use a beam API.

api.oanor.com/catenary-api

Leathercraft API

Leathercraft maths as an API, computed locally and deterministically — the weight, area and strap numbers a leatherworker, saddler or maker cuts a project by. The thickness endpoint handles the quirk that leather “weight” is really a thickness: one ounce equals one sixty-fourth of an inch, or 0.397 mm, so 8 oz leather is 3.18 mm — and it converts in either direction between ounces, millimetres and inches and suggests typical uses, from 2–3 oz linings and wallets up to 9 oz-plus belts and saddlery. The area endpoint converts hide area between the US square foot, the European square decimetre (1 ft² = 9.29 dm²) and square metres, and sizes a project: given the leather a project needs and a waste allowance — 25–40 % is normal because hides have irregular edges and flaws — it returns the usable area and how many hides to buy. The strap endpoint counts straps cut from a rectangular piece (count = ⌊width ÷ strap width⌋, each as long as the piece) or the continuous lace length a spiral cut yields from an area (length = area ÷ width). Everything is computed locally and deterministically, so it is instant and private. Ideal for leatherwork, saddlery, crafting, bag-making and maker app developers, project-estimator and material-cost tools, and workshop software. Pure local computation — no key, no third-party service, instant. Live, nothing stored. 3 compute endpoints.

api.oanor.com/leather-api

Resin & Epoxy API

Casting and epoxy-resin maths as an API, computed locally and deterministically — the mix, coverage and mould-volume numbers a resin artist, crafter or maker pours a project by. The mix endpoint splits a two-part resin by its label ratio: resin = total × A/(A+B), hardener = total × B/(A+B), from whichever quantity you know — the total, the resin or the hardener — so a 2:1 epoxy for 300 ml is 200 + 100, and a 100:45 by-weight system for 100 g of resin needs 45 g of hardener; it keeps your unit (ml, grams, fl oz) and reminds you that some resins mix by volume and others by weight. The coverage endpoint sizes a flood or seal coat: volume = area × thickness, in metric or US units, returned in millilitres, fluid ounces and gallons plus the mass — matching the familiar art-resin rule of about a gallon per 12 ft² at an eighth of an inch. The moldfill endpoint computes the volume of a box, cylinder, sphere or cone mould (a 10×10×5 cm box is 500 ml, 550 g at epoxy’s ~1.1 g/cm³) and subtracts the displacement of anything you embed, so you never over- or under-pour. Everything is computed locally and deterministically, so it is instant and private. Ideal for resin-art, craft, jewelry, model-making, river-table and maker app developers, project-estimator and material-cost tools, and studio software. Pure local computation — no key, no third-party service, instant. Live, nothing stored. 3 compute endpoints. For pot life and cure follow the product data sheet.

api.oanor.com/resin-api

Pottery & Ceramics API

Pottery and ceramics maths as an API, computed locally and deterministically — the shrinkage, glaze-batch and firing numbers a potter works out at the wheel and the kiln. The shrinkage endpoint handles the fact that clay shrinks from wet to bone-dry to fired: with a typical 12 % linear shrinkage a 100 mm rim fires down to 88 mm, and run in reverse it tells you to throw a piece larger to land on a target size — make it 100 mm wet to finish at 88 mm — and reports the volume shrinkage, which is the cube of the linear factor (about 32 %). The glaze endpoint scales a percentage recipe to a real batch: pass the ingredients as a name:percent list and a dry batch weight and it returns the grams of each, dividing by the recipe’s own percent sum so recipes that total over 100 % (a base 100 plus colorant and opacifier additions) still scale correctly, plus the water to add for dipping. The cone endpoint gives the approximate firing temperature for an Orton self-supporting cone at the standard 108 °F/hour ramp — cone 06 is about 1828 °F (998 °C) for bisque, cone 6 about 2232 °F (1222 °C) and cone 10 about 2345 °F (1285 °C) for stoneware — and reminds you that a cone measures heat-work, not just temperature. Everything is computed locally and deterministically, so it is instant and private. Ideal for ceramics, pottery-studio, maker and craft app developers, kiln-log and glaze-calculator tools, and studio-management software. Pure local computation — no key, no third-party service, instant. Live, nothing stored. 3 compute endpoints. For kiln-element power use a different API.

api.oanor.com/pottery-api

Frequently asked questions

Quick answers about pricing, quotas, and integration.

How do I get an API key for Knitting Gauge API?

Sign up for free at oanor.com, generate an API key from the developer dashboard, and call Knitting Gauge API with the x-oanor-key header. No credit card needed for the free tier.

What's the rate limit for Knitting Gauge API?

Free tier allows 1 request per second. Paid plans scale up to 50 requests per second on the Mega tier. Hard limits return HTTP 429 above the quota — no surprise overage charges.

How much does Knitting Gauge API cost?

Knitting Gauge API has a free tier with 100 calls / month. Paid plans start at €3.60 / month with higher quotas and faster rate limits.

Can I cancel my subscription anytime?

Yes. Plans are billed monthly and you can cancel anytime from your billing dashboard. No long-term contracts and no cancellation fee.

Is Knitting Gauge API GDPR-compliant?

All requests to Knitting Gauge API go through our EU-based gateway. Your upstream API key never leaves our server and no personal data is shared with the upstream provider beyond the request you send.

Knitting 3

Meta 1

Pick an endpoint from the list on the left to see its details and try it.

GET /v1/convert-pattern

Convert pattern between gauges

Playground

Parameters

Custom headers

Language: Client:

GET /v1/gauge

Gauge from a swatch

Playground

Parameters

Custom headers

Language: Client:

GET /v1/stitches

Stitches/rows for dimensions

Playground

Parameters

Custom headers

Language: Client:

GET /v1/meta

Spec

Playground

Custom headers

Language: Client:

Code snippets

curl https://api.oanor.com/knitting-api/SOME_PATH \
  -H "x-oanor-key: oanor_test_..."

const res = await fetch("https://api.oanor.com/knitting-api/SOME_PATH", {
  headers: { "x-oanor-key": "oanor_test_..." }
});
const data = await res.json();

$ch = curl_init("https://api.oanor.com/knitting-api/SOME_PATH");
curl_setopt($ch, CURLOPT_RETURNTRANSFER, true);
curl_setopt($ch, CURLOPT_HTTPHEADER, ["x-oanor-key: oanor_test_..."]);
$response = curl_exec($ch);

import requests
r = requests.get(
    "https://api.oanor.com/knitting-api/SOME_PATH",
    headers={"x-oanor-key": "oanor_test_..."},
)
print(r.json())

Ratings

No reviews yet.

Discussion

Ask questions, share usage tips, get answers from the provider and other developers. Public — anyone can read.

New thread

📌 Pinned 🔒 Locked

· ·

🔒 This thread is locked — no new replies.

No threads yet — start the discussion.

Support

Private 1:1 support with the provider — billing questions, integration issues, account problems. Only you and the provider team can see these threads.

Open new ticket

Describe what you need help with. The provider team gets an email and replies on the ticket page.

No tickets yet for this API.

Subscription active — calls can start immediately.

Send your first request —

Subscription active — copy a snippet and fire off your first call.

Pick a key

Plaintext is shown once at creation — use the prefix as a reminder.

Knitting Gauge API

API health

Pricing

Built by

Related APIs

Catenary Cable API

Leathercraft API

Resin & Epoxy API

Pottery & Ceramics API

Frequently asked questions

Parameters

Parameters

Parameters

Code snippets

Ratings

Discussion

New thread

📌 🔒

Support

Open new ticket

Your cookie choices