#diy

Caulk and sealant coverage maths as an API, computed locally and deterministically — the linear-feet-per-tube and how-many-tubes numbers a builder, glazier or DIYer buys sealant by. A bead of caulk is essentially a thin cylinder, so the coverage endpoint works out the feet a cartridge lays from the bead width: volume per foot ≈ (π/4 × width²) × 12 inches, and a standard 10.1 fl oz cartridge (18.2 in³) lays about 30 feet of a quarter-inch bead, 13 feet of a fat three-eighths or 55 of a fine three-sixteenths — pass cartridge_oz for sausage packs or 28-oz tubes, and a tube count to total it. The tubes endpoint runs it backwards: cartridges needed = (joint length × a waste factor) ÷ feet per cartridge, rounded up, so a 100-foot run of quarter-inch bead with 10 % waste takes four tubes. Everything is computed locally and deterministically, so it is instant and private. Ideal for construction, glazing, weatherproofing and home-improvement app developers, material-estimator and shopping-list tools, and contractor software. Pure local computation — no key, no third-party service, instant. Inches and feet; estimates — tooling and waste vary. Live, nothing stored. 2 compute endpoints.

api.oanor.com/caulk-api

Wallpaper-estimating maths as an API, computed locally and deterministically. The rolls endpoint uses the proper drop method: it works out how many full-height drops come from each roll, floor(roll length ÷ (wall height + pattern repeat)), how many drops the room perimeter needs, ceil(perimeter ÷ roll width), and from those the rolls required — so a larger pattern repeat correctly increases the count. The simple endpoint gives a quick area-based estimate, rolls = ceil(wall area·(1+waste) ÷ roll coverage), handy for plain papers. The cost endpoint totals the project from the rolls and price per roll plus the adhesive, with one tub of paste hanging about five rolls. The standard roll of 10.05 m × 0.53 m is assumed unless you override it. Everything is computed locally and deterministically, so it is instant and private. Ideal for home-decor, renovation and trade app developers, DIY and room-planning tools, and decorator and retailer calculators. Pure local computation — no key, no third-party service, instant. Live, nothing stored. 3 endpoints. This is wallpaper estimation; for wall paint use a paint API and for floor tiles use a flooring API.

api.oanor.com/wallpaper-api

Paint estimating and mixing maths as an API, computed locally and deterministically. The coverage endpoint works out how much paint an area needs — paint = area × coats ÷ spreading rate — from an area (in square metres or square feet), the number of coats and the paint's coverage (in m² per litre or square feet per US gallon, defaulting to a typical emulsion), and returns the volume in litres and US gallons and, given a tin size, the number of tins to buy. The room endpoint computes the paintable wall area of a room from its length, width and height — perimeter × height minus the door and window openings, optionally plus the ceiling — and then the paint needed, with sensible default door and window sizes you can override. The ratio endpoint splits a total volume by a mixing ratio such as 4:1 (base to hardener) or 4:1:10 (base, hardener, thinner) into each component's amount and percentage, or scales the whole mix up from one known component amount — for two-part epoxies, catalysed paints and thinning. Everything is computed locally and deterministically, so it is instant and private. Ideal for decorating, trade and DIY tools, hardware-store and paint-shop apps, estimating and quoting software, and home-improvement projects. Pure local computation — no key, no third-party service, instant. Live, nothing stored. 3 endpoints. This is paint coverage and mixing; for mulch, soil and gravel volumes use a landscaping API.

api.oanor.com/paint-api