#estimating

Geometría de techos como una API, calculada local y determinísticamente. El endpoint de pendiente convierte libremente entre las tres formas en que los oficios describen la inclinación de un techo: la pendiente como elevación por 12 de avance (notación X:12), el ángulo en grados y la pendiente como porcentaje, usando ángulo = atan(pendiente/12); un techo 6:12 es 26.57° y una pendiente del 50%, y también devuelve el multiplicador de pendiente √(1 + tan²) que escala una longitud plana a la longitud real a lo largo de la pendiente. El endpoint de viga calcula la longitud de la viga común a partir del avance horizontal y la pendiente, viga = √(avance² + elevación²) con elevación = avance·tan(ángulo), y agrega la longitud a lo largo de la pendiente de un voladizo horizontal opcional — un avance de 12 unidades a 6:12 necesita una viga de 13.42 unidades. El endpoint de área convierte una huella de edificio plana en el área de superficie real del techo inclinado, huella / cos(ángulo), la cifra que necesita para pedir tejas, membrana o subcapa; una huella de 100 m² bajo un techo 6:12 es aproximadamente 111.8 m². Las longitudes son independientes de la unidad — use una unidad consistente. Todo se calcula local y determinísticamente, por lo que es instantáneo y privado. Ideal para desarrolladores de aplicaciones de techado, construcción, estimación para contratistas, mejoras para el hogar, instalación solar y arquitectura, herramientas de medición y pedido de materiales, y software comercial. Cálculo local puro — sin clave, sin servicio de terceros, instantáneo. En vivo, nada almacenado. 3 endpoints. Esta es geometría específica de techos; para una pendiente o gradiente general, use una API de pendiente.

api.oanor.com/roofpitch-api

Drywall (plasterboard) material-estimation maths as an API, computed locally and deterministically. The sheets endpoint computes how many boards a wall or ceiling needs — the area (given directly, or as perimeter × height, or length × width) divided by the sheet area, with a waste allowance — and the number of screws (about 32 per standard sheet). The compound endpoint estimates the joint compound in kilograms and the joint tape in metres for taping and finishing the boarded area, with adjustable per-square-metre factors for your product and number of coats. The cost endpoint totals the project from the sheets and their price plus the compound and tape. The standard 2.4 × 1.2 m board is assumed unless you override it. Everything is computed locally and deterministically, so it is instant and private. Ideal for construction, renovation and trade app developers, drywall and plastering estimators, and builder and retailer tools. Pure local computation — no key, no third-party service, instant. Live, nothing stored. 3 endpoints. This is drywall material estimation; for insulation R-values use a U-value API and for wall paint use a paint API.

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

Fencing material estimating as an API, computed locally and deterministically. The posts endpoint works out the number of fence sections, line posts and rails for a run from its length and the post spacing, plus the total rail length. The pickets endpoint computes how many pickets or boards a length needs from the picket width and the gap between boards (set the gap to zero for a privacy fence). The materials endpoint produces a full bill of materials in one call — posts, rails, pickets and the concrete for the post holes, in cubic feet and metres and in 80 lb pre-mix bags — from the fence dimensions and the hole size and post depth. Everything is computed locally and deterministically, so it is instant and private. These are estimates: allow extra for waste, gates and corner posts, and follow your local building code for post depth and footing size. Picket width and gap are in inches; length can be feet, yards or metres. Ideal for fencing contractors and estimators, DIY and home-improvement tools, and landscaping and quoting software. Pure local computation — no key, no third-party service, instant. Live, nothing stored. 3 endpoints. This is fencing materials; for paint, tile and concrete use a construction-calculator API and for mulch and gravel use a landscaping API.

api.oanor.com/fence-api

Roofing geometry as an API, computed locally and deterministically. The pitch endpoint converts a roof pitch between every common form — rise-over-run (such as 6:12), the angle in degrees, the percent slope, and the slope multiplier (the factor that turns a flat footprint into the real sloped area). The rafter endpoint computes the rafter length from the horizontal run and the pitch — that is, the hypotenuse √(run² + rise²) — with an optional overhang projected along the slope. The area endpoint computes the true sloped roof area from the building footprint (entered directly or as length × width) and the pitch, adds a wastage allowance, and reports the number of US roofing squares and shingle bundles needed. Everything is computed locally and deterministically, so it is instant and private. Lengths are unit-agnostic — use consistent units — while the squares and bundles figures assume US roofing squares of 100 square feet, so pass the footprint in square feet for those. Ideal for roofing contractors and estimators, construction and DIY tools, solar-install planning, and quoting software. Pure local computation — no key, no third-party service, instant. Live, nothing stored. 3 endpoints. This is roof geometry; for paint, tile, concrete and brick quantities use a construction-calculator API.

api.oanor.com/roofing-api

Construction and material estimating as an API — the everyday "how much do I need to buy" maths for building and renovation jobs, computed locally and deterministically from standard geometry and trade rules of thumb. The paint endpoint works out the litres and number of cans for a surface, allowing for the number of coats and the paint's coverage and deducting doors and windows. The tile endpoint computes how many tiles (and full boxes) a floor or wall area needs from the tile dimensions and a wastage allowance. The concrete endpoint gives the concrete volume in cubic metres, cubic yards and litres — and the number of pre-mix bags — for a slab, footing, wall or round column, with an optional batch quantity. The bricks endpoint computes how many bricks a wall needs from the brick size and mortar joint (default 215×65 mm brick with a 10 mm joint ≈ 60 bricks per square metre). Everything is computed locally and deterministically, so it is instant and private. Ideal for builders' merchants and trade apps, DIY and home-improvement tools, quoting and estimating software, and project planners. Pure local computation — no key, no third-party service, instant. Live, nothing stored. Estimates are guidance — allow for site conditions and follow the manufacturer's stated figures. 4 endpoints. This is materials estimating; for plain unit conversion use a unit-conversion API and for tyre or drivetrain maths use a tyre API.

api.oanor.com/buildcalc-api