#maker

Fretted-instrument lutherie maths as an API, computed locally and deterministically — the fret positions a guitar, bass, mandolin or ukulele builder slots a fingerboard to. This is instrument-building geometry, not music theory. The positions endpoint lays out a whole fingerboard from the scale length using the twelve-tone equal-temperament rule: the distance from the nut to fret n = scale length × (1 − 1 ÷ 2^(n/12)), so the 12th fret lands at exactly half the scale (the octave) and each gap shrinks by the constant ratio 2^(1/12) ≈ 1.0595 toward the bridge — a 25.5-inch Fender scale puts fret 1 at 1.431 inches and fret 12 at 12.75. The fret endpoint gives one fret’s distance from the nut, from the previous fret and to the bridge; the scalelength endpoint runs it backwards, recovering the scale length from a measured distance to a known fret (measure to the 12th and double it). It works in inches or millimetres — 25.5 Fender, 24.75 Gibson, 25.4 classical, 34 bass. Everything is computed locally and deterministically, so it is instant and private. Ideal for lutherie, guitar-building, instrument-design and maker app developers, fingerboard-slotting and fret-calculator tools, and CAD/CNC templates. Pure local computation — no key, no third-party service, instant. Live, nothing stored. 3 compute endpoints. For note names or frequencies use a music-theory API.

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

Screen-printing maths as an API, computed locally and deterministically — the ink-usage and cost numbers an apparel printer or print shop quotes a job by. It all turns on “ink mileage”, the printed area a unit of ink covers — in² per pound, with plastisol commonly 12,000–18,000 depending on mesh and deposit. The ink endpoint sizes a run: ink = (print area × prints) ÷ mileage, so a 100 in² design printed 150 times at 15,000 in²/lb takes exactly one pound (454 g, about 3 g a print); pass the design as area or as width × height. The prints endpoint runs it in reverse — how many shirts a tub of ink will do: prints = (ink weight × mileage) ÷ print area, so a pound of plastisol covers 15,000 in², roughly 150 prints of that design before waste, and it takes pounds, kilograms or grams. The cost endpoint puts a price on it: ink pounds × price per pound gives the run’s ink cost and the per-print figure, usually just a few cents — ink only, before screens, garments and labour. Everything is computed locally and deterministically, so it is instant and private. Ideal for screen-printing, apparel-decoration, print-shop and merch app developers, quoting and job-costing tools, and production-planning software. Pure local computation — no key, no third-party service, instant. Live, nothing stored. 3 compute endpoints. Ink only; add screens, garments and labour for a full quote.

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

3D-printing filament maths as an API, computed locally and deterministically. The length-weight endpoint converts between the length and the weight of a spool of filament from its diameter (1.75 mm or 2.85 mm) and material density, using weight = (π/4·d²·length)·density — so one metre of 1.75 mm PLA weighs about 2.98 g, a standard 1 kg PLA spool holds roughly 335 m, and the same weight of the lighter ABS gives about 400 m. The cost endpoint computes the filament cost of a print from the weight or length used and the price per kilogram, and the spool-remaining endpoint turns a remaining-weight measurement (weigh the spool, subtract the empty-spool weight) into the remaining length so you know whether a job will finish. Built-in densities cover PLA, ABS, PETG, TPU, nylon, ASA, PC, HIPS, PVA, wood-fill and carbon-fibre blends, or supply your own. Diameters are in millimetres, lengths in metres and weights in grams. Everything is computed locally and deterministically, so it is instant and private. Ideal for 3D-printing, maker, print-farm, slicer-plugin, prototyping and STEM-education app developers, filament-usage and print-cost tools, and workshop software. Pure local computation — no key, no third-party service, instant. Live, nothing stored. 3 endpoints. This is filament geometry and cost; for tank or material volume use a volume API.

api.oanor.com/filament-api

Capacitor maths as an API, computed locally and deterministically. The energy endpoint computes the stored energy and charge of a capacitor from any two of the capacitance, the voltage and the charge — E = ½CV² = ½QV and Q = CV — in joules, millijoules and coulombs. The charging endpoint models the RC charging and discharging transient: the time constant τ = RC, the voltage at a given time, V(t) = Vs(1 − e^(−t/RC)) when charging or V(t) = V₀·e^(−t/RC) when discharging, and the percent charged, or — given a target voltage — the time to reach it; a capacitor reaches about 63 % of the way in one time constant and over 99 % in five. The combination endpoint computes the total capacitance of capacitors in series (1/C = Σ1/Cᵢ) or parallel (C = ΣCᵢ). Capacitance accepts farads or the handy µF/nF/pF units. Everything is computed locally and deterministically, so it is instant and private. Ideal for electronics, maker, embedded and circuit-design app developers, power-supply and timing tools, and electronics education. Pure local computation — no key, no third-party service, instant. Live, nothing stored. 3 endpoints. This is capacitor maths; for AC reactance and resonance use a resonance API and for LED resistor sizing an LED-resistor API.

api.oanor.com/capacitor-api

LED current-limiting-resistor maths as an API, computed locally and deterministically. The resistor endpoint sizes the series resistor for a single LED, R = (V_supply − V_forward) / I, and returns the resistor power dissipation (I²·R), the LED power, a recommended resistor wattage rating and the nearest E12 standard value (rounded up so the LED current stays at or below the target). The series endpoint sizes the one shared resistor for several LEDs wired in series, where the forward voltages add, R = (V_supply − n·V_f) / I, and flags when the supply is too low for the string. The parallel endpoint gives the per-LED resistor for LEDs in parallel (each needs its own) and the total current the supply must deliver. Currents are entered in milliamps. Everything is computed locally and deterministically, so it is instant and private. Ideal for electronics, maker, Arduino and hardware app developers, LED and lighting-circuit design tools, and electronics education. Pure local computation — no key, no third-party service, instant. Live, nothing stored. 3 endpoints. This is LED resistor sizing; for general Ohm's law and reactance use an Ohm's-law API and for AWG wire properties use a wire-gauge API.

api.oanor.com/ledresistor-api