#heating

Heating and cooling degree-day maths as an API, computed locally and deterministically. The daily endpoint computes the heating degree days, HDD = max(0, base − mean), and the cooling degree days, CDD = max(0, mean − base), for a single day from a base temperature and the daily mean — or the minimum and maximum, since the mean is taken as their average. The period endpoint sums the degree days over a list of daily temperatures (means or min/max pairs), returning the total HDD and CDD, the count of heating and cooling days and the average temperature — the standard way to characterise a heating or cooling season. The energy endpoint turns degree days into an energy estimate: the heat delivered is UA·DD·24/1000 kWh from the building heat-loss coefficient, the fuel or electricity input is that divided by the boiler efficiency (or a heat-pump COP), and — with an energy price — the cost. Everything is computed locally and deterministically, so it is instant and private. Ideal for building-energy, HVAC and facilities tools, heating-bill and fuel-budget estimation, weather-normalisation and energy-benchmarking apps, and engineering education. Pure local computation — no key, no third-party service, instant. Live, nothing stored. 3 endpoints. This is degree-day demand estimation; for U-value and heat-loss fabric calculations use a U-value API.

api.oanor.com/degreeday-api

HVAC sizing maths as an API, computed locally and deterministically from standard rule-of-thumb factors. The cooling endpoint estimates the air-conditioner load for a room — in BTU per hour, tons of cooling and kilowatts — from the floor area (in square feet or metres, or length × width) using a baseline of about 20 BTU/h per square foot, with adjustments for the number of occupants, a kitchen, sun exposure and ceiling height. The heating endpoint estimates the heating load from the area and a climate zone (mild through very cold) or a custom BTU per square foot. The convert endpoint converts between BTU per hour, tons of cooling, kilowatts and watts (one ton = 12,000 BTU/h ≈ 3.517 kW). Everything is computed locally and deterministically, so it is instant and private. These are rule-of-thumb estimates in the EnergyStar style — a proper Manual J load calculation accounting for insulation, windows and local climate is recommended for a real installation. Ideal for HVAC and home-improvement tools, air-conditioner and heater sizing guides, smart-home and energy apps, and contractor quoting. Pure local computation — no key, no third-party service, instant. Live, nothing stored. 3 endpoints. This is HVAC sizing; for appliance running cost use an energy-cost API.

api.oanor.com/hvac-api

Firewood maths as an API, computed locally and deterministically. The volume endpoint turns a wood-stack's length, height and depth (in feet or metres) into its volume in cubic feet and cubic metres, full cords, face cords and steres — a full cord being 128 cubic feet (a 4×4×8 ft stack) and a face cord being an 8×4 ft stack by the piece (log) length. The convert endpoint converts a quantity between cords, face cords, steres, cubic metres and cubic feet, using the piece length for the face-cord relationship. The heat endpoint estimates the heating value of a number of cords by wood species — returning the millions of BTU and the equivalent gallons of heating oil, therms of natural gas and kilowatt-hours — from a built-in table of typical seasoned-wood values (oak, hickory, maple, ash, birch, pine and more) or a custom figure. Everything is computed locally and deterministically, so it is instant and private. Heat values are typical seasoned figures (around 20% moisture) and vary with species, dryness and stove efficiency. Ideal for firewood sellers and delivery tools, heating and homestead apps, and forestry and woodlot calculators. Pure local computation — no key, no third-party service, instant. Live, nothing stored. 3 endpoints. This is firewood volume and energy; for general volume or unit conversion use a unit-conversion API.

api.oanor.com/firewood-api