#crafts

Cross-stitch and embroidery maths as an API, computed locally and deterministically — the design-size, fabric and floss numbers a cross-stitcher, embroidery designer or needlework-shop works a project out with. The design-size endpoint turns a stitch count and a fabric count (stitches per inch) into the finished size: size = stitch count ÷ fabric count, so a 140 × 98 design on 14-count Aida finishes at 10 × 7 inches (25.4 × 17.8 cm), smaller on 18-count and larger on 11-count because a higher count packs more stitches per inch — and it returns the total stitch count (width × height) that drives the floss and the hours. The fabric-needed endpoint adds a margin on every side to give the fabric to cut: design size + twice the margin per dimension, with the usual 3 inches per side for hooping, framing and finishing, so a 10 × 7 design wants a 16 × 13 inch cut. The thread-length endpoint estimates floss from the geometry of a full cross — the front two diagonals plus the back returns is about (2√2 + 2) ÷ fabric count inches per stitch — so 5,000 stitches on 14-count is roughly 1,724 inches, about 44 m, and it estimates the skeins given the number of strands (a 6-strand skein is ~8 m). Everything is computed locally and deterministically, so it is instant and private. Ideal for cross-stitch and embroidery pattern tools, needlework-shop and kit apps, and craft-project calculators. Pure local computation — no key, no third-party service, instant. Floss figures are planning estimates — buy a little extra and dye-lot match. 3 compute endpoints. For sewing yardage use a sewing API; for knitting gauge a knitting API.

api.oanor.com/embroidery-api

Textile-dyeing recipe maths as an API, computed locally and deterministically — the dye, water and auxiliary numbers a dyer weighs out to mix a repeatable dye-bath, whether for a swatch or a full bolt. The dye-weight endpoint gives the dye to weigh = the weight of fabric × the depth of shade, the percentage of dye on the weight of the goods: a 2 % shade on 100 g of fabric is 2 g of dye, pale shades run under half a percent, deep blacks 4 % or more — working on-weight-of-fabric is exactly what makes a recipe scale and repeat. The liquor-ratio endpoint gives the dye-bath volume = the weight of goods in kilos × the liquor ratio, the litres of bath per kilo (a 20:1 ratio is 20 L per kg); lower ratios save water, dye and energy and exhaust deeper, higher ratios level more evenly on delicate or pale work. The auxiliary endpoint gives the salt, soda ash or levelling agent to add = the bath volume × the dosing concentration in grams per litre — salt (50–80 g/L) drives reactive and direct dyes onto cotton, soda ash (10–20 g/L) raises the pH to fix them. Everything is on-weight or per-litre, so the same recipe gives the same colour and chemistry at any scale, and it is computed locally and deterministically, so it is instant and private. Ideal for craft and studio dyers, textile and yarn shops, and dye-recipe and batch-calculator tools. Pure local computation — no key, no third-party service, instant. 3 compute endpoints. For knitting yardage and gauge use a knitting API; for vegetable-ferment or meat-cure salt a fermentation or curing API.

api.oanor.com/dye-api

Fuse-Bead-Mathematik als API, lokal und deterministisch berechnet – die Perlenanzahl, Stecktafel- und Farbzahlen, die ein Perler-, Hama- oder Schmelzperlen-Bastler bei der Planung eines Pixel-Designs benötigt. Der Grid-Endpunkt wandelt ein Pixel-Muster der Breite × Höhe in den tatsächlichen Bau um: Gesamtperlen = Breite × Höhe, Stecktafeln = ⌈Breite ÷ Tafel⌉ × ⌈Höhe ÷ Tafel⌉ (eine 29-Noppen-Quadrattafel für Midi-Perlen) und die fertige Größe = Perlen × Perlenabstand – ein 58 × 58 Midi-Design ergibt also 3.364 Perlen, vier Stecktafeln und etwa 29 × 29 cm, in Millimetern, Zentimetern und Zoll, mit Midi bei 5 mm, Mini bei 2,6 mm und Biggie bei 9–10 mm. Der Palette-Endpunkt teilt die Perlen nach Farbe auf: Gib die Gesamtzahl und eine Liste von Farbprozenten an, und er gibt die Anzahl pro Farbe zurück (normalisiert durch die Prozentsumme, funktioniert also auch, wenn sie nicht genau 100 ergeben) und die zu kaufenden Beutel mit etwa tausend Perlen pro Stück, oder übergib Rohzahlen, um sie direkt zu beuteln. Alles wird lokal und deterministisch berechnet, also ist es sofort und privat. Ideal für Entwickler von Fuse-Bead-, Pixel-Art-, Kinderbastel- und Maker-Apps, für Muster-zu-Einkaufsliste- und Projekt-Schätzer-Tools sowie für Bastelsoftware. Reine lokale Berechnung – kein Key, kein Drittanbieter-Service, sofort. Live, nichts wird gespeichert. 2 Compute-Endpunkte. Für Kreuzstich-Stoffzahlen verwende eine andere API.

api.oanor.com/fusebead-api

Paracord-craft maths as an API, computed locally and deterministically — the cord-length numbers a paracord crafter cuts a project to. The bracelet endpoint sizes the cord from the finished length and the weave using the well-known rule of thumb — about a foot of cord per inch of work for a cobra (Solomon) bar, double that for a king cobra, less for a fishtail — so an 8-inch cobra bracelet takes around 9 feet of cord including a foot of waste for the tails; give it a wrist measurement instead and it adds the fit ease and the buckle to get the finished length first, so a 7-inch wrist comes out near 10 feet. The weave endpoint generalises it to any project — lanyards, belts, dog leashes — as cord = finished length × cord-per-inch × the number of working strands, with the weave factors built in or your own cord-per-inch, and answers in inches, feet and metres. Everything is computed locally and deterministically, so it is instant and private. Ideal for paracord, survival-gear, scouting, craft and maker app developers, project-estimator and cut-list tools, and DIY software. Pure local computation — no key, no third-party service, instant. Rules of thumb — cut long and trim. Live, nothing stored. 2 compute endpoints.

api.oanor.com/paracord-api

Chainmaille-Mathematik als API, lokal und deterministisch berechnet – die Seitenverhältnis- und Ringzahlen, nach denen ein Maille-Künstler webt. Der Aspect-Endpunkt berechnet das alles entscheidende Seitenverhältnis = Innendurchmesser ÷ Drahtdurchmesser und löst nach dem fehlenden Wert auf, listet dann die Weaves auf, die dieser Ring ergibt: AR, nicht die absolute Größe, entscheidet alles – zu niedrig und die Ringe schließen nicht ineinander, zu hoch und das Weave wird labbrig, also ein 6,4 mm ID auf 1,6 mm Draht ergibt AR 4,0, gut für European 4-in-1, Byzantine, Box Chain und mehr. Der Ring-Endpunkt erledigt die Materialmathematik: Draht pro Ring ≈ π × (Innendurchmesser + Drahtdurchmesser) – der mittlere Durchmesserumfang – also benötigen diese AR-4-Ringe etwa 25 mm Draht pro Stück und wiegen in Stahl etwa 0,4 g; geben Sie eine Drahtlänge an, um die Anzahl der Ringe zu erhalten, oder eine Ringanzahl, um den gesamten Draht und das Gewicht zu erhalten, in jedem von neun Metallen von Aluminium bis Silber. Alles wird lokal und deterministisch berechnet, also sofort und privat. Ideal für Chainmaille-, Schmuck-, Cosplay-Rüstungs- und Maker-App-Entwickler, Ringkauf- und Projektkalkulator-Tools sowie Bastelsoftware. Reine lokale Berechnung – kein API-Key, kein Drittanbieter-Service, sofort. Maße in mm. Live, nichts wird gespeichert. 2 Compute-Endpunkte. Für Drahtstärke ↔ mm verwenden Sie eine Wire-Gauge-API.

api.oanor.com/chainmaille-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

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 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

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.

api.oanor.com/knitting-api